Skip to main content

Workflow

Phonton is built around one loop:

flowchart LR
  Goal["Goal"] --> Plan["Plan"]
  Plan --> Cheap["Cheap model"]
  Cheap --> Verify["Verify"]
  Verify --> Receipt["Receipt"]
  Receipt --> Memory["Memory"]

1. Check your setup​

phonton doctor
phonton doctor --provider

In the TUI:

/plan add validation to config loading
/approve

Headless:

phonton plan "add validation to config loading"
phonton goal "add validation to config loading"

The plan shows subtasks, likely files, and verify steps before anything mutates your repo.

3. Run and watch​

  • TUI: type your goal and press Enter
  • Headless: phonton goal "your goal here"

Use Shift+L for the flight log, Alt+[ / Alt+] to cycle focus panels (Plan, Receipt, Code, Problems, …).

4. Review the receipt​

When verification finishes, read the Receipt focus or:

phonton review latest
phonton proof export --latest --format json

A good receipt answers: what changed, which models ran, what passed, what it cost, and what a frontier-only run would have cost at a published list rate.

5. Memory (optional)​

Phonton remembers decisions across tasks:

phonton memory list

In the TUI: /memory opens the browser. p pins, d deletes selected rows.

Good first tasks​

Pick something small and verifiable:

  • Fix the golden-path fixture at fixtures/add-one (one failing add_one test)
  • Add validation to one module
  • Refactor one file with tests still green

Avoid “rewrite the whole app” until you have seen one full receipt you trust.