namp Ask for an invite

Not A Meat Proxy.

Stop carrying text between your Claude Code sessions and your head. namp is a page in your browser where your sessions bring their canvases, the questions they need you to settle and the threads you hold with them. You answer there, and they get back to work.

namp's page for a topic, Offline maps: its canvas with a question the session asked, the recommended choice taken as the answer, and the question's thread open on the right

What's on the page

A canvas per topic
Each piece of work is a topic, and its session writes the topic's canvas: the brief, the design, the plan, in Markdown you read like a document rather than scroll back through.
Questions you settle
When a session needs a decision, it asks in the canvas, with its options and the one it recommends. You pick one or write your own, and it carries on from your answer.
Threads beside the text
Comment on any line and the session replies there. A session waiting on you wakes up when you write, so nothing sits unread in a terminal.
Home
The digest lists what waits for you across every topic, the most urgent first. j and k step through it, a acknowledges what you read.
Sessions that start sessions
A topic's session can split its work into tasks and start a sibling for each, in a herdr pane on a git worktree of its own, then merge their work back.

It runs on your machine

namp is a server on your own computer, on port 4321, and the page it serves. Your sessions run in herdr panes beside it, and nothing passes through a namp service.

It needs:

  • macOS on Apple Silicon, or Linux on x86-64 or ARM64
  • herdr, which runs the sessions in its panes
  • Claude Code

namp is in a private alpha

Each tester gets a personal invite link. Opening it here shows your install command, and every update comes through it.

Ask for an invite