Beacon
Local · no account · no API key

# Give your coding agent eyes and hands.

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 | sh`

then run beacon inside any repo

Works with
Claude Code
Codex
Roadmap Database/plan · review
Magic-link sign-in
Email a one-time link, no passwords
feature auth Pending
Issue + verify token
sub-task Pending
auth_tokens new
id uuid
token_hash text
user_id→ users
expires_at timestamp
1
annotation · you
Expire links after 15 min, not 24 h.
plan ready · waiting for your verdict
Approve
Feedback
Discard
The loop

The loop

## Propose. Review. Verdict. Repeat.

01

### Propose

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-in`

02

### Review

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 table`

03

### Verdict

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 persisted`

feedback sends the agent back to 01 · approval persists the drafts

The surfaces

## Everything the agent plans, drawn

/plan

### Review

Split screen: the proposal on the left, live canvases on the right. Every plan archived with your decision and a snapshot of the moment.

/map

### Roadmap

Features, sub-tasks, and dependencies as a graph. Duplicate features get blocked before they exist.

/db

### Database

Proposed tables and endpoints land as drafts, diffed against your live schema: new, changed, or untouched.

Quickstart

## Five lines to your first approved plan

your-repo — terminal
`$ curl -fsSL https://www.trybeacon.sh/install.sh | sh` 01 · one binary, no account
`$ cd your-repo && beacon` 02 · registers the repo, opens the panel
`› /beacon-init` 03 · maps architecture, schema, roadmap
`› plan: magic-link sign-in` 04 · the plan streams onto /plan
`✓ approve · feedback · discard` 05 · the verdict returns to your session

Reuse 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.

Notes

No notes yet. Hit + to start one.

Select a note, or create one. Then @-mention it in your terminal to turn it into features.