Drive Terminals From the Command Line
Run `onedevtool terminal` from any shell to list your in-app agent tabs, poll one for idle or busy, submit a prompt, and close a tab when it is done. Every submit returns a submission id and the agent's readiness, and the exit code separates “written to a ready composer” from “likely queued behind the current turn”.
Screenshot coming soon
Why You Need This
How this feature boosts your daily productivity
Scripting an agent is only useful if the script can tell what happened. `onedevtool terminal submit` now prints a submission id plus the readiness of the agent at the moment the prompt landed, and exits 3 rather than 0 when the composer looked busy — so a caller waits instead of assuming the work started. `status` polls one tab in a single shot, and `close` shuts a tab and its process down, refusing seats a live orchestration team is using and pointing at the proper stop command instead. A prompt 1DevTool is holding for your confirmation reports that it is awaiting approval rather than reading as delivered. Turn the CLI on under Settings → Terminal → “Enable local onedevtool terminal CLI”.
How It Works
Get started in 4 simple steps
Turn the CLI on
Settings → Terminal → "Enable local onedevtool terminal CLI" exposes the onedevtool terminal command to any shell on this machine.
Find the tab you want
`onedevtool terminal list --json` returns your in-app agent tabs, each row carrying a status of idle, busy, unknown or closed.
Send a prompt and read the receipt
`onedevtool terminal submit --id=<id> --prompt-stdin` prints a submission id and the agent readiness at the moment the prompt landed.
Branch on the exit code
Exit 0 means the prompt went into a ready composer; exit 3 means it was written while the agent looked busy and is likely queued behind the current turn.
Poll, then close
`onedevtool terminal status --id=<id>` is a one-shot readiness check; `close --id=<id>` ends the tab and its process, refusing seats a live team is using.
Without 1DevTool
The manual way vs. the 1DevTool way
The Hard Way
The 1DevTool Way
Key Capabilities
Everything included with Drive Terminals From the Command Line
Why It Matters
The productivity impact of having terminal & ai agents built into your workspace
Exit 0 Finally Means Something
A submit that lands in a busy composer exits 3 instead of 0, so a script can wait for the current turn rather than assuming its prompt is being worked on.
Proof, Not Hope
Every submit returns a submission id and the readiness at the moment it landed — a receipt you can log, rather than the absence of an error.
Teams Do Not Lose Members To A Script
Closing a tab that a live orchestration seat is using is refused and redirected to the proper stop command, so automation cannot quietly break a running team.
Held Is Not Delivered
A prompt waiting on your confirmation says so, instead of reporting success and leaving the caller waiting for a reply that cannot come.
More in Terminal & AI Agents
Other features in this category you might find useful
Multi-Agent Terminals
Run Claude Code, Codex, Gemini CLI, Amp, OpenCode, Qwen, and custom AI commands in dedicated terminal tabs with recognizable agent logos, custom colors, and status indicators.
Flexible Terminal Layouts
View terminals in 2×2 grid, side-by-side columns, or single fullscreen mode with resizable panes.
Terminal Dashboard
Kanban-style board view of all terminal statuses — Idle, Running, and Review — with real-time polling.
Session Persistence
Terminal sessions persist across app restarts with full scrollback history via tmux integration.
Ready to boost your workflow?
Download 1DevTool for free and experience Drive Terminals From the Command Line along with 170 other features — all in one app.