Capturing sessions in your terminal

Worsley isn't limited to your browser. Connect Worsley to your terminal, and it monitors the AI sessions you run there and captures them, so your work in the terminal is scored and analyzed alongside your browser sessions.

What you get

• Your terminal sessions in your account, next to the sessions from your browser.
• The same ROIP scoring and feedback as every other session.
• One picture of how you work with AI, wherever you run it.

How it works

The Worsley CLI signs in to your account once per computer, then captures in one of two ways:

• Tools that keep session files (Claude Code, Codex CLI, Gemini CLI, Grok Build, Qwen Code, GitHub Copilot in VS Code): worsley enable <tool> reads only that tool's session folder, and worsley watch uploads new turns as they happen.
• Tools that call a model's API (DeepSeek, Mistral, Kimi, Muse and local models): worsley proxy runs a relay on your computer and you point the tool at it. Requests pass through unchanged; Worsley keeps a copy of each exchange, never your API key.

Get started

Install the CLI (macOS or Linux; on Windows, use irm https://www.worsley.ai/install.ps1 | iex in PowerShell):

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

Then sign in once on each computer, and approve the link it prints:

worsley login

Then follow the setup guide for your tool:

• Claude Code
• Codex CLI
• Gemini CLI
• Grok Build
• Qwen Code
• GitHub Copilot in VS Code
• DeepSeek
• Mistral Vibe
• Kimi Code CLI
• Muse
• Local models (Ollama, LM Studio, llama.cpp)