cc-in-codex
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CC_IN_CODEX_CLAUDE_PATH | No | Absolute path to the claude executable if not in PATH |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| companion_openB | Create or restore the persistent Claude Code companion for a project cwd. This does not send work to Claude. |
| companion_resumeA | Bind cc-in-codex to an existing Claude Code conversation. SDK needs sessionId; TUI can use sessionId or continueLatest:true. |
| companion_sendA | Send a short task or follow-up to the persistent Claude Code companion and wait for completion. For long coding work, prefer companion_start plus polling. |
| companion_tui_openC | Create or restore a native Claude Code CLI in tmux for this project. Returns the attach command for the side terminal. |
| companion_tui_resumeB | Launch the visible tmux-hosted Claude Code CLI with |
| companion_tui_sendA | Paste a prompt into the persistent native Claude Code TUI and press Enter. Returns immediately with the tmux attach command. |
| companion_tui_rawA | Send literal text and/or tmux key names to the existing Claude Code TUI pane without the cc-in-codex wrapper. Use for slash commands (e.g. /clear), control keys (C-c), or Escape. Requires an open tui session. |
| companion_tui_compact_checkA | Inspect the visible Claude Code TUI and cc-in-codex metadata to decide whether this is a good checkpoint to run /compact. This is a heuristic, not a true token-limit reading. |
| companion_tui_compactA | Ask the visible Claude Code TUI to run /compact with cc-in-codex-aware preservation instructions. Prefer companion_tui_compact_check first. |
| companion_tui_screenB | Capture recent text from the persistent tmux-hosted Claude Code TUI so Codex can monitor what the user sees. |
| companion_startA | Start a background Claude Code companion run for this cwd. Returns quickly with runId; use companion_status/recent/result to monitor. |
| companion_waitB | Wait until the companion emits events after sinceCursor, finishes, or timeoutMs elapses. Use after companion_start for smoother progress updates. |
| companion_recentA | Read recent events from the persistent companion, similar to scrolling the Claude Code window. |
| companion_resultB | Read the latest companion result, resume command, and session metadata for a cwd. |
| companion_statusC | Inspect the current companion session for a cwd. |
| companion_cancelA | Cancel the currently running companion turn for a cwd, if any. |
| companion_init_projectA | Create AGENTS.md and CLAUDE.md in the project cwd so Codex and Claude Code share the same project instructions. Existing files are skipped unless force=true. |
| companion_resetA | Forget the project-to-Claude-session binding for a cwd. Use only when the user wants a fresh Claude Code companion. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| companion_policy | Default tool policy and interaction rules for the Claude Code companion. |
TDQS
Scored across 18 tools
Most tools have clearly distinct purposes, but the SDK vs TUI variants (e.g., companion_open vs companion_tui_open, companion_send vs companion_start vs companion_tui_send) could be confused by an agent despite descriptions clarifying the differences. Overall, the boundaries are mostly clear.
All tools follow a consistent 'companion_<verb>[_noun]' pattern using snake_case, with optional 'tui' prefixes for TUI-specific actions. This makes the tool set highly predictable and easy to navigate.
With 18 tools, the set is in the 16-25 range that feels heavy. Many tools exist in both SDK and TUI variants, inflating the count, though each serves a genuine purpose for the dual interfaces.
The tool set covers the full lifecycle of a companion: create/restore, send/start tasks, monitor via status/recent/result, manage with cancel/reset/resume, and TUI-specific compact/raw operations. Minor gaps include no explicit listing of all companions for a cwd, but that's not essential.