Set up Claude
Capture Claude on claude.ai with the browser extension, and Claude Code in your terminal.
Worsley captures Claude in two places. Set up either one, or both: everything lands in the same account.
- Claude on the web, at claude.ai, through the browser extension.
- Claude Code, Anthropic's coding agent in your terminal, through the Worsley CLI.
Set it up in your browser
- 1Get the Worsley extension from the Install Extension page. It's in the Chrome Web Store; for Firefox, join the waitlist there for early access. It works in Chrome, in Chromium browsers such as Edge, Brave, Arc, Opera, Opera GX and Vivaldi, and in Firefox.
- 2Pin it to your toolbar: open the extensions menu (the puzzle-piece icon) and pin Worsley, so its status is one click away.
- 3In the same browser, log in to Worsley, or create an account if you don't have one yet.
- 4Open Settings > Connection and select Connect. The extension is now tied to your account, and This Browser shows as Capturing.
- 5If the Worsley icon says No Site Access, select it and choose Allow Access. Worsley needs access to claude.ai to capture, and to nothing else you browse.
- 6Open Claude and sign in. If a Claude tab was already open before you installed the extension, reload it.
- 7Have a conversation as you normally would. Worsley captures each turn as it finishes.
Sign in to the Worsley CLI
Do this once on each computer where you run Claude Code.
- 1Install the Worsley CLI. It runs on macOS, Windows and Linux and needs Node.js 22.23.4 or later (on a Mac,
brew install nodeworks too). On macOS or Linux, run:
curl -fsSL https://www.worsley.ai/install.sh | shOn Windows, in PowerShell:
irm https://www.worsley.ai/install.ps1 | iexThe installer checks the download against its published checksum, puts the CLI in your home folder (~/.worsley, or %LOCALAPPDATA%\Worsley on Windows) and adds it to your PATH. Open a new terminal window afterward so the worsley command is found. Run the same command again any time to update.
- 1Sign in. The command below prints a link and a short code, then waits.
worsley login- 1Open the link. Log in to Worsley if asked, check that the code on the page matches the one in your terminal and that it names this computer, then select Connect. If you last logged in more than 10 minutes ago, Worsley asks you to log in again first. Opened the page without the code? Type it in.
- 2Back in the terminal, Worsley confirms Signed in as your email. The sign-in is kept in your system's credential store (macOS Keychain, Windows Credential Manager or Secret Service on Linux), never in a plain file. The code expires after 10 minutes; run
worsley loginagain if it does.
Turn on Claude Code capture
- 1Tell Worsley to capture Claude Code. It reads only Claude Code's session folder, ~/.claude/projects, and nothing else on your computer.
worsley enable claude-codeIf you moved Claude Code's folder with CLAUDE_CONFIG_DIR, Worsley follows it. Kept somewhere else entirely? Pass the folder yourself: worsley enable claude-code --dir <folder>.
- 1Start uploading. Leave this running in a terminal window while you work; it checks for new turns and uploads them as they happen. Press Ctrl+C to stop.
worsley watchPrefer to upload now and then? Run worsley sync instead: it reads what's new, uploads it once, and exits. Nothing is read or uploaded while neither is running.
- 1Use Claude Code as you normally do. Every new session appears in Worsley, usually within a minute.
Support for Claude Code is new: it's built from Claude Code's known session format and hasn't yet been checked against every setup. If a session doesn't appear, or looks wrong, contact support and tell us which version you use.
Check that it's working
- Open History in Worsley. Your session shows up there with the tool's name, usually within a minute of a finished turn.
- Select the Worsley icon on a Claude tab: it shows the conversation you're in and its suggestions once a prompt is analyzed.
- In the terminal, run
worsley status. It shows the account this computer is signed in to and anything still waiting to upload.
What's captured
- Your prompts and Claude's replies, turn by turn.
- The model and effort setting, when Claude shows them.
- Details of files you attach (name, type and size, not their contents).
- Incognito chats are captured and labeled temporary. See Temporary and incognito conversations.
- In Claude Code: what you typed, Claude's replies, the model and the session's title. Tool calls and their output, thinking, images, slash commands, shell commands run with !, and sub-agents are left out, and so are your project's files. If you rewind and edit a prompt, the edited version replaces the old one.
The Claude desktop and mobile apps aren't captured. Use claude.ai in a browser with the extension, or Claude Code in your terminal.
If a session doesn't appear
- Browser: check that the Worsley icon isn't showing Not Connected, Reconnect or No Site Access, and reload the tool's tab. More in Extension isn't capturing.
- Terminal: check that
worsley watchorworsley proxywas running while you worked, and runworsley status. If it says the sign-in was revoked or expired, runworsley loginagain. - Still missing after a few minutes? Contact support and tell us which tool and which browser or terminal you used.
Related articles
- Extension isn't capturingGet capture working again in a few steps.
- Temporary and incognito conversationsTemporary chats are captured and clearly labeled as temporary.
- AttachmentsWorsley records details about files in a conversation.
- Capturing sessions in your terminalWorsley captures the AI sessions you run in your terminal, as well as those in your browser.
- Session isn't appearingWhat to check when a conversation doesn't show up in Worsley.

