Use in Terminal
The terminal workflow sends work to a coding tool, updates work, and runs local workers without switching back to the browser.
Before you start
Install the CLI, sign in, and choose a workspace from CLI. After that, use the terminal to send work, inspect records, or start local workers.
Configure the launch targets you want one send to use:
one settings tools add codexone settings folder add ~/Sites/project
Use one settings tools list and one settings folder list to inspect the active workspace settings.
Send one item
Run one send after an initiative, bug, or todo is ready to open in a coding tool:
one send tsk_123The CLI builds a prompt from the initiative, bug, or todo, including linked document-backed descriptions when present, then opens the tool you choose.
Enabled launch targets appear when you run one send. Some open an app; others run a shell command in a saved terminal folder.
Modes include Plan, Code, Review, and Fix. Pass --tool and --mode when you already know the target:
one send tsk_123 --tool codex --mode codeInspect and update work
The CLI gives you a fast terminal view of work before deciding what to send:
| Goal | Command |
|---|---|
| List work | one list, one ready, one blocked |
| Open details | one show <id> |
| Create work | one create |
| Move status | one start <id>, one close <id>, one block <id>, one status <id> <status> |
| Add context | one comment <id> |
In an interactive terminal, omitting an ID opens a picker for commands that can choose work.
Start a local worker from the CLI
Worker commands queue work for a Codex worker on your machine:
one worker createone worker doctorone worker run tsk_123
Run a foreground worker when you want logs in the current terminal:
one worker watchRun a background worker when you want the worker to keep polling after the terminal returns:
one worker startone worker statusone worker logsone worker stop
one worker status tracks background workers started with one worker start. Foreground one worker watch prints progress in its own terminal.
Use Desktop terminal launch
From a work detail page in Desktop, choose Send to and select Terminal. Desktop builds the prompt, copies it to the clipboard, opens Terminal.app in the selected project folder, and runs the configured command with the prompt ready.
If no default folder is saved, Desktop asks you to pick one and saves it for next time. This path uses the one:// deep link scheme and is macOS-only.
For the dashboard flow, start with Send to app. For full command coverage, open CLI. For queued Codex runs on your machine, use Local Workers.