AI Prompts: connecting Claude Code and Codex to Colabio
Your organization can record the prompts you send to AI coding agents, so your work shows up as what you were building rather than as screenshots to interpret. Here is exactly what runs, where, and when.
Capture follows your timer
Nothing is recorded while your timer is stopped. Work for the organization happens on the clock, so prompts you send with tracking off are your own time and are never collected — the check happens before anything is written to your disk, not after.
If the app crashes or you force-quit it, capture stops on its own rather than carrying on in the background.
Turning it on
Your organization decides. An organization manager turns it on once, under Activity → AI Prompts in the dashboard. Every signed-in desktop app picks it up within about five minutes — no restart, nothing for you to install.
You can also switch it on for yourself in the desktop app under Preferences → AI Coding Agents.
Claude Code — automatic
The desktop app adds one hook entry to your Claude Code settings. It backs the file up first, never touches a settings file it cannot read, and leaves everything else in it alone. Removing capture removes only that entry.
A restart usually is not needed. If nothing appears after a few minutes, quit and reopen Claude Code.
Codex — one paste
Codex is set up by hand, because its configuration file is one people also edit themselves. In the desktop app, open Preferences → AI Coding Agents and use Copy setup block — the block already contains the correct paths for your machine. Then:
- Use Open config.toml to reveal the file (it is created for you if Codex has never run).
- Paste the block at the end of the file and save.
- Trust it once. Codex runs a hook from your config only after you approve it: in a terminal run
codex, type/hooks, select the Colabio hook and trust it. Until then Codex skips it silently and nothing is recorded. The Codex desktop app has no screen for this step, so it needs the CLI (npm install -g @openai/codexif you do not have it).
The setting flips to “Codex is connected” once a prompt actually arrives — so you can confirm it worked rather than hope.
The hook runs through node, which is already present wherever these agents run.
Where your files are
| Operating system | Claude Code settings | Codex config | Colabio capture folder |
|---|---|---|---|
| macOS | ~/.claude/settings.json | ~/.codex/config.toml | ~/Library/Application Support/colabio/ai-prompts |
| Windows | %USERPROFILE%\.claude\settings.json | %USERPROFILE%\.codex\config.toml | %APPDATA%\colabio\ai-prompts |
| Linux | ~/.claude/settings.json | ~/.codex/config.toml | ~/.config/colabio/ai-prompts |
A backup of your original Claude Code settings is kept beside it as settings.json.colabio-backup.
What is and is not recorded
- The prompt you submitted, when you sent it, which agent, and the folder and branch you were working in.
- Passwords, API keys and connection strings are removed before anything leaves your machine, and again on arrival.
- Anything sent while your timer is stopped.
- The agent's replies, your files, or the changes it made.
- Chat in a browser, on your phone, or on a machine without the Colabio app.
- Background messages the tools send themselves, such as task notifications.
If nothing shows up
- Check the timer is running. This is the usual answer — capture follows the clock.
- Give it five minutes. Prompts upload on a cycle, not instantly.
- Restart Claude Code if it was already open when capture was switched on.
- Check Preferences → AI Coding Agents. It says whether anything has been captured yet, and how many prompts are waiting to upload.
Still stuck? Email support@colabio.org.