1. Home
2. Claude Code

Opuscule for Claude Code

Your Claude Code sessions, bound as a book.

Opuscule archives your Claude Code sessions on your Mac before they're deleted, and typesets them into a printed volume you proofread before it goes to the printer.

Claude Code keeps every conversation in ~/.claude/projects, then deletes it after 30 days by default. In between lies a whole quarter of work: features shipped, bugs hunted down at 2 a.m., generated images, three-word prompts and three-screen ones. Opuscule makes it a book.

What a session becomes

Each session becomes a two-page spread:

• Your promptQuoted exactly as you typed it. Your words are never rewritten.
• What happenedA short summary, written by your own claude from text that's already filtered.
• The numbersDuration, number of prompts, agent actions, model.
• The imagesThe ones the agent produced, as they were that day.

Every volume also includes an activity report (sessions per month, prompt length, actions per prompt, models, records), a closing letter and notes pages. Flip through this week's volume, a fictional sample typeset with the real template.

Before they're deleted

Opuscule archives your sessions as you go on your Mac, with their images. Your archive stays even when Claude Code cleans up. Until the app is out, keep yours with one line in ~/.claude/settings.json:

{ "cleanupPeriodDays": 3650 }

The details, plus a hook to archive every session: Claude Code deletes your sessions after 30 days.

Your sessions stay on your Mac

• Archiving, filtering, layout and proofreading happen on your Mac. The Opuscule server never sees the content of the book.
• Keys, passwords, tokens, card numbers and IBANs are always masked before layout. Masked text is removed from the PDF, not covered.
• You review risky pages one by one and approve the rest in one go. Nothing is printed without your approval.
• Only the approved PDF goes to the printer, through a single-use link, and it's deleted once retrieved.

Questions