Set up ChatGPT

Worsley captures ChatGPT in two places. Set up either one, or both: everything lands in the same account.

• ChatGPT on the web, at chatgpt.com, through the browser extension.
• Codex CLI, OpenAI's coding agent in your terminal, through the Worsley CLI.

Set it up in your browser

1. 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.
2. 2Pin it to your toolbar: open the extensions menu (the puzzle-piece icon) and pin Worsley, so its status is one click away.
3. 3In the same browser, log in to Worsley, or create an account if you don't have one yet.
4. 4Open Settings > Connection and select Connect. The extension is now tied to your account, and This Browser shows as Capturing.
5. 5If the Worsley icon says No Site Access, select it and choose Allow Access. Worsley needs access to chatgpt.com to capture, and to nothing else you browse.
6. 6Open ChatGPT and sign in. If a ChatGPT tab was already open before you installed the extension, reload it.
7. 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 Codex CLI.

1. 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 node works too). On macOS or Linux, run:

curl -fsSL https://www.worsley.ai/install.sh | sh

On Windows, in PowerShell:

irm https://www.worsley.ai/install.ps1 | iex

The 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.

1. 1Sign in. The command below prints a link and a short code, then waits.

worsley login

1. 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.
2. 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 login again if it does.

Turn on Codex CLI capture

1. 1Tell Worsley to capture Codex CLI. It reads only Codex CLI's session folder, ~/.codex/sessions, and nothing else on your computer.

worsley enable codex-cli

If you moved Codex CLI's folder with CODEX_HOME, Worsley follows it. Kept somewhere else entirely? Pass the folder yourself: worsley enable codex-cli --dir <folder>.

1. 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 watch

Prefer 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.

1. 1Use Codex CLI as you normally do. Every new session appears in Worsley, usually within a minute.

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 ChatGPT 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 ChatGPT's replies, turn by turn.
• The model and thinking setting, when ChatGPT shows them.
• Details of files you attach (name, type and size, not their contents).
• Temporary chats are captured and labeled temporary. See Temporary and incognito conversations.
• In Codex CLI: what you typed and the agent's replies. Tool calls, command output, reasoning and your project's files are never read.

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 watch or worsley proxy was running while you worked, and run worsley status. If it says the sign-in was revoked or expired, run worsley login again.
• Still missing after a few minutes? Contact support and tell us which tool and which browser or terminal you used.