Repository navigation
docs: document agentop configure claude-code — enable, disable, status #1236
Description
Feature Description
agentop configure claude-code ships in v0.8.1 and has no user-facing page. The laptop quickstart mentions Claude Code in one line (install.sh --claude-code) and otherwise sends readers to a short ## Other agents section. Nothing documents the subcommand, what it writes, or how to undo it.
The command exists at cmd/agentop/cmd_claudecode.go and supports:
agentop configure claude-code enable [--yes] [--settings PATH] [--config PATH]
agentop configure claude-code disable [--yes] [--settings PATH]
agentop configure claude-code status [--settings PATH]
It routes Claude Code through Cortex without shell environment variables, by writing an env block into Claude Code settings, reading the proxy address from ~/.cortex/config.yaml so it always matches the running proxy.
Proposed Solution
- A page covering
enable/disable/status, with real output - What the command writes, and where the settings file lives
- Why this is preferable to exporting proxy env vars in a shell
- How the proxy address is resolved from
~/.cortex/config.yaml, and what happens when Cortex is not running - The CA trust step, and how it relates to the install
- How to undo it, and how to confirm it is undone
- Verified against a release binary
Additional Context
Split out of #959, which covered the first-run spine and is closed. This is the per-agent configuration surface the spine links to but does not document.
Companion issue covers Bob and Bobshell.
Activity
mrsabath commentedon Oct 3, 2026
Scope grew —
agentop configurenow covers five agents, not one.Since this was filed, OpenCode support landed (#1243) and
codexappeared in the dispatcher.agentop configureonmainis now:claude-code~/.claude/settings.jsonbobhttp.proxyin IBM Bob'ssettings.jsonbobshellbobshell function in your rc fileopencodecodexagentop exec -- codexThere is also a new
agentop setup(#1245) that installs or repairs an install, plans every change before applying it, and rolls back on failure orCtrl-C.rossoctl/rossoctl#2618 adds the per-agent table to
laptop.md#other-agentsand routes the missing-CA case toagentop setup, so the commands are at least discoverable.Remaining for this issue — the full page for
claude-code:enable/disable/statuswith real captured output~/.claude/settings.json, and that it touches nothing else~/.cortex/config.yaml, and the behaviour when Cortex is not runningagentop setup --claude-coderelates to itWorth noting
opencodediffers in kind from the rest — it configures a background service rather than the binary you invoke — so it likely wants its own section rather than a row in a shared table. Flagging here rather than filing a third issue.docs: correct the latency reading, and cover the new agentop surfaces
docs: correct the latency reading, and cover the new agentop surfaces (…
huang195 commentedon Oct 11, 2026
docs/agents/claude-code.md covers enable, disable and status. closing