The session in your terminal is the brain. Beacon is where its plans become visible: features, tables, and endpoints on a canvas you annotate, edit, and approve with one click.
$curl -fsSL https://www.trybeacon.sh/install.sh | shthen run beacon inside any repo
The loop
01
Ask the session in your terminal to plan a feature. It calls beacon_propose_plan and blocks until you decide. No fire-and-forget.
› plan: magic-link sign-in02
The plan renders as feature nodes, tables, and endpoints. Select any passage to annotate it, mark it for deletion, or edit the boards directly.
/plan · 2 features · 1 table03
Approve persists the drafts. Feedback sends your notes back and the agent re-plans. Discard throws it away. Every plan is archived either way.
✓ approved · drafts persistedfeedback sends the agent back to 01 · approval persists the drafts
The surfaces
/map·Steer the agent's work order
Features, sub-tasks and dependencies as a graph — priority on the border, a layer stripe for frontend or backend, and the work-on-next ring marking the agent's next move.
Quickstart
$ curl -fsSL https://www.trybeacon.sh/install.sh | sh01 · one binary, nothing to configure$ cd your-repo && beacon02 · registers the repo, opens the panel› /beacon-init03 · maps architecture, schema, roadmap› plan: magic-link sign-in04 · the plan streams onto /plan✓ approve · feedback · discard05 · the verdict returns to your sessionReuse first
Beacon blocks duplicate features. Check the map before you create.
Design data first
Tables and endpoints before code. Review the schema as a draft on /db.
Close every loop
Register finished work so the map stays accurate next session.