Command Code
Command Code (`command-code`) is now a built-in agent: pick it in Add Terminal next to Claude and Codex, and it gets its own command-key logo on desktop and on the phone. 1DevTool waits for its composer to be idle before Agent Input or Send to AI types a prompt, resumes its sessions with `command-code --resume <id>`, lists its models from `--list-models`, and offers full-permission, plan and accept-edits modes in one click.
Why You Need This
How this feature boosts your daily productivity
Running Command Code in a plain shell tab means 1DevTool cannot tell when it is ready, so a prompt sent from Agent Input can land in the middle of a turn or on top of a half-typed draft, and its sessions never show up anywhere else. As a built-in, Command Code is a peer of the other agents. Prompt delivery holds back while a turn is running, a draft is typed or a picker is open. Past sessions from `~/.commandcode/projects` appear in Resume, prompt history and the Conversation view, a restarted terminal reopens its own session, and a rename is written into Command Code's own session metadata so the title sticks in the CLI too. Other agents can delegate work to it with `--to=commandcode`, it can take a seat in a team, Draw, commit-message generation and Task AI, and Settings installs 1DevTool's MCP servers into `~/.commandcode/mcp.json` like any other agent. Install it with `npm install -g command-code` (Node 22 or newer).
How It Works
Get started in 4 simple steps
Install the CLI
Run npm install -g command-code (Node 22 or newer). 1DevTool finds command-code, commandcode or cmdc on your PATH; a bare cmd stays the Windows shell.
Pick Command Code in Add Terminal
It sits in the AI Agents grid with its own command-key logo. Choose a model from the picker, which lists what Command Code's --list-models reports.
Choose a permission mode
Full permission (--yolo), plan or accept-edits are one click away, and the startup command stays editable before you launch.
Send prompts safely
Agent Input, Send to AI and delegated prompts wait until the composer is idle, and hold back while a turn runs, a draft is typed or a picker is open.
Resume and rename
Past sessions appear in Resume, prompt history and the Conversation view. A restart reopens the terminal's own session with --resume, and a rename sticks in Command Code too.
Without 1DevTool
The manual way vs. the 1DevTool way
The Hard Way
The 1DevTool Way
Key Capabilities
Everything included with Command Code
Why It Matters
The productivity impact of having ai productivity built into your workspace
Prompts Never Land Mid-Turn
Delivery waits for an idle composer, so a prompt from another terminal or agent cannot interrupt a running turn or overwrite your draft.
Sessions You Can Find Again
Past Command Code sessions sit in the same Resume and Conversation views as Claude and Codex, instead of in a folder you have to remember.
One More Seat on the Team
Other agents can delegate to Command Code, and it can fill a role in a team, Draw, commit messages or Task AI.
More in AI Productivity
Other features in this category you might find useful
Prompt History
Search prompts and sticky notes from Remote Control while away from the desktop. Switch between This project and All projects, filter prompts by agent or notes by source, copy entries, delete with Operator access, and sync local prompt history.
Resume UI
Browse, search, and resume past AI sessions from Claude Code, Codex, and Gemini CLI — or combine multiple sessions into one.
Combine Sessions
Select sessions from Claude Code, Codex, and Gemini CLI and merge them into a single conversation — giving your next agent the full cross-agent context.
AI Diff Review Panel
Track every file modification any AI agent makes — Claude Code, Codex, Gemini, Amp, custom — and review, accept, or revert their work per file from a dedicated panel with inline diff overlays in the editor.
Ready to boost your workflow?
Download 1DevTool for free and experience Command Code along with 321 other features — all in one app.