hostplan

A home for the plans your agents write.

Coding agents produce plans constantly, and they land wherever — a scratch file, a repo's PLAN.md, a chat scrollback. hostplan gives every plan one address, filed by project and branch, readable in a browser or by the next agent.

or sign in to see your plans →

npm package coming soon — until then, clone the repo and `bun link`.

$ hsp add PLAN.md
✓ stored  Worktree GC  · nest / feat/delivery · a3f9c2
→ https://plans.host-plan.com/p/a3f9c2  asks for the code
→ https://plans.host-plan.com/p/a3f9c2?code=KRWT  opens directly
A plan rendered in the hostplan viewer, with an Open in button

What it does

One address per plan

Every plan gets a short id and a URL the moment it's stored. Hand the link to a teammate or paste it back to an agent — no more 'which PLAN.md did you mean'.

Bucketed by project and branch

Project and branch come from git automatically, so plans file themselves. A branch called feat/delivery stays readable as feat/delivery.

Public or private, per plan

Private by default with a 4-letter share code. Publish a plan when you want a bare link, rotate the code when a link escapes.

Open straight into your agent

Every plan page hands itself to Codex, Claude Code, or Cursor with the prompt pre-filled — so reading a plan and acting on it are one click apart.

Built for agents, not just people

--json on every command that returns data, and `hsp get latest` so an agent can re-read what it just wrote without tracking an id.

Plain markdown on disk

No database, no lock-in. Each plan is a file that describes itself in frontmatter, so the directory tree is the index and nothing can fall out of sync.

Get started

  1. 1hsp add PLAN.mdStore a plan and get its URL back.
  2. 2hsp listSee what's planned for this repo and branch.
  3. 3hsp get latestPull the newest plan back into an agent.

Project and branch are detected from git, so there is nothing to configure. Plans are private until you publish them.