Phonton CLI

The ADE loop in your terminal.

Install one CLI and get plan preview, typed swarm metadata, selectable code-index backends, MCP capability previews, sandboxed command evidence, verifier gates, review receipts, and local memory.

Download latest Install guide Extensions

phonton cli - live simulationinteractive

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
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-tokens --by-sourceSeparate local prompt estimates from provider-reported usage.

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 tokenizer estimates for prompt budgeting and provider-reported tokens as the billing source of truth when providers return usage.

phonton why-tokens --by-source
local_prompt_estimate_tokens: 1800
estimate_source: local tokenizer estimate
provider_usage_source: provider reported
provider_reported_input_tokens: 1200