Phonton CLI

Verified goals from the terminal.

Install one CLI. Plan the change, start cheap, run your checks, escalate only when proof fails, and keep a receipt of cost versus frontier.

Install CLI GitHub releases Extensions

recorded run · phonton 0.22.3 · deepseek-flashreplay

Install

Start with doctor, then run a goal.

The CLI is the canonical release surface. It keeps local state, extension records, verification output, and receipts in the workspace instead of turning every run into a hidden hosted session.

npm install -g phonton-cli
phonton doctor --provider
phonton

Command surface

Commands line up with the product loop.

phontonOpen the TUI for goal, plan, edit, verify, review, and remember.

phonton plan --json <goal>Preview the GoalContract, plan graph, swarm reason, conflict groups, and index backend before execution starts.

phonton extensions doctorInspect local skills, steering, MCP trust, permissions, env vars, and conflicts.

phonton mcp capabilities <server> --yesPreview negotiated MCP tools and proposed permission rules without calling a tool or writing config.

phonton doctor --providerCheck config, provider routing, local tools, and selected index backend.

phonton why-tokensShow provider-reported tokens per subtask for the last goal.

phonton models setup qwen3.5:4bRun goals on a local model: runtime, download, calibration, selection.

phonton review latestInspect the latest review handoff and known gaps.

phonton proof export --latest --format jsonExport typed proof evidence for audit or benchmark packets.

Context mentions

Address files, symbols, folders, and MCPs with @...

Mentions are resolved before dispatch so unsupported, missing, or approval-gated context can be shown in the TUI and receipts. This keeps context explicit instead of hidden inside prompt stuffing.

@README.mdAttach one workspace file as bounded context.

@docs/Reference a directory summary instead of dumping it blindly.

@"release note.md"Reference paths with spaces.

@symbol:GoalContractAsk for a named code symbol.

@mcp:githubMention a configured MCP server.

@mcp:github/create_issueMention a tool while keeping approval requirements visible.

TUI surfaces

Built for repeatable autonomous work.

Prompt bar

Bracketed paste, history, slash commands, and context mentions.

Plan focus

GoalContract, acceptance criteria, assumptions, and run shape.

Problems focus

Verifier diagnostics and repair path when a goal fails.

Flight Log

Commands, tool calls, token records, and extension influence.

Token accounting

Estimates and billing usage are kept separate.

Phonton uses local estimates for prompt budgeting and provider-reported tokens as the billing source of truth when providers return usage. Output below is from a real run.

$ phonton why-tokens
Why tokens: Add a remove(id) method to TodoStore that deletes the todo and throws an Error with the m…

     2122 in     121 out     1152 cached  Implement method `remove`  [deepseek-flash]

total: 2122 input, 121 output, 1152 cached (provider reported)
code context selected: 5 slices, ~309 tokens (local estimate)