Run Miton from your terminal.
Miton CLI runs on its own and keeps its own projects and sessions. If you also use Miton Desktop on this computer, CLI can use the provider connections both apps support.
Commands run on the computer where you start them. Sessions do not sync to another machine.
See which connections are ready with miton provider list, then choose one with miton provider use <id>. Connections the CLI cannot use do not appear.
For example, ask Miton to check a project without changing its dependencies:
miton build "review the direct dependencies without updating them"The same checks apply in a terminal.
CLI checks the project, the tools available to the current mode and where the work will run. If it cannot ask whether you trust a project, it starts with restricted access.
- Piping in does not grant trust
- If CLI cannot ask, it keeps the project restricted unless you pass trust explicitly.
- The local control service stays on your machine
- Its control API stays on this computer. A separate phone connection opens only after you pair a device and allow local-network access.
- Tools still pass two checks
- Before a tool runs, CLI checks that it is available in the current mode and that you have permission to use it.
Choose how results come back.
Use the interactive view while you work, stream structured events to another tool, or keep the prompt plain for SSH and screen readers.
- Interactive
- A full terminal interface with activity, routing and spend visible while the turn runs.
--format json · ndjson- Every agent event as a record. NDJSON streams one event per line for anything reading incrementally.
--no-tui- A plain readline prompt with no cursor addressing, for terminals and readers that do better without it.
Find a command for the job.
An independent command surface for sessions, workflows, projects, routing, CLI-supported providers and the local control plane.
01 · Doing the work
miton run <prompt>- Run an agent against a prompt.
miton build <prompt>- Plan, approve, build and verify an app.
miton resume <id> [prompt]- Pick a session back up where it stopped.
miton fork <id>- Branch a session and keep both paths.
miton pr <number>- Check out a pull request and run the agent on it.
02 · Sessions and projects
miton sessions list | show | tree- See what you have been working on, and how it branched.
miton sessions export | import- Move a session between machines.
miton project open | create | clone | status- Work with projects and their git state.
miton init- Generate project instructions, scaffold and wiki pages.
03 · Automation
miton workflow run <file>- Run a workflow graph.
miton workflow replay <id>- Replay a previous run.
miton workflow cron- Manage schedules on your own machine.
miton skill run | list- Run a skill, or see what is installed.
miton agents list | show | create- List, inspect or create sub-agents.
04 · Models, routing and spend
miton routing- Explain or configure how work gets routed.
miton models [provider]- List models exposed by configured CLI providers.
miton matchmaker <prompt>- Rank catalogue models for a specific prompt.
miton usage- Token and estimated cost history.
miton provider list | use | add | remove- Manage supported built-in and custom CLI providers.
miton auth login <provider>- Connect a provider over OAuth.
05 · Local connections
miton daemon start | status | attach- Manage the local control plane.
miton gateway start | status- Run the messaging gateway.
miton mcp ...- Manage standalone Model Context Protocol servers.
miton doctor- Diagnose provider, model and project readiness.
miton wiki browse [path]- Serve a project's wiki over localhost.
miton uninstall- Remove the local state under ~/.miton.
What CLI supports today.
- Standalone development in your terminal
- Start or resume work, inspect state, run workflows and manage providers from a shell. CLI runs independently of Desktop.
- Use supported Desktop connections
- On the same computer, CLI can read compatible provider connections from Desktop. CLI keeps its own projects and sessions.
- Headless is still guarded
- Workspace trust, permission policy, injection checks, model routing and keychain-held credentials all still apply when there's no window.
- Interactive terminal, or piped output
- A terminal interface for people, structured output for programmes, and a plain readline path for CI, SSH and screen readers.
The CLI is implemented as a standalone host, but it is not publicly downloadable or separately distributable yet. Public beta access has not opened yet.