Agent CLI: Claude Code or Codex as Your Assistant

If you already use Claude Code or Codex, Chronoid’s chat can run through it. Answers come from the subscription that CLI is signed in to, so there is no API key to create, paste, or pay for separately — and the CLI can read your real tracked time to answer questions, the same way the built-in chat does.

Setting It Up

1. Open Settings → AI Providers, click +, and choose Agent CLI.
2. In the CLI picker, choose Claude Code, Codex CLI, OpenCode, Pi, Amp, or Custom command.
3. Chronoid finds the command automatically and shows a green Found at … check. If you installed it somewhere unusual, set the full path in the Path field.
4. Click Test Connection, then pick the new provider in chat.

The CLI must already be installed and signed in — run claude or codex once in Terminal first if you have not. Requests run on that tool’s subscription; no key is stored in Chronoid.

Chronoid looks for the command in the usual install folders, such as ~/.local/bin, /opt/homebrew/bin, /usr/local/bin, ~/.bun/bin, and ~/.npm-global/bin, and then in your shell’s PATH. If it shows Not installed, set the full path or use the folder button to choose it.

Choosing a Model

With Claude Code you can pin Opus, Sonnet, or Haiku, or leave CLI default to use whatever the CLI is already set to. Codex, OpenCode, and Pi list the models the CLI reports. Amp has modes instead of models (Low, Medium, High, Ultra). Custom commands use their own default unless you pass a model flag via Extra arguments (use {model} where the command expects the model name).

Extra arguments are added to every run. Useful examples: --effort high for Claude Code, --enable web_search for Codex, or --fast for Amp.

Access to Your Time Data

The “Let the CLI read your tracked time” toggle (on by default, Claude Code and Codex only) gives the CLI the same local tools the built-in chat uses, served from Chronoid’s authenticated local MCP server. Each lookup appears in the chat transcript as it happens — you see every tool call, its input, and its result. Turn the toggle off and the CLI only sees your question.

OpenCode, Pi, Amp, and custom commands do not get tool access, so they answer from your question alone.

The CLI runs in a temporary folder with its own file and shell tools turned off. It can reach your time data through Chronoid’s tools, but not your files.

Custom Commands

Custom command points Chronoid at any executable that reads a question on standard input and prints the answer on standard output. Chronoid appends nothing beyond the model and the extra arguments you set, and treats everything the command prints as the answer. Custom commands do not get tool access; relevant data is included in the prompt instead.

Limits

• Image attachments are not supported through an Agent CLI — attachments are described in text instead.
• Each request has a 5-minute ceiling; long-running commands are stopped after that.
• Temperature and other model settings in Chronoid do not apply; the CLI uses its own.

Related Guides

• Using AI in Chronoid
• AI Providers
• AI Assistant
• AI Connectors (claude.ai & ChatGPT)
• Chronoid MCP Server

For help, email support@chronoid.app