Noter

noter sits between your thinking and your coding agent’s execution. It installs via npm as a global CLI and opens Mission Control: four panels that hold your notes, agent context, suggested next tasks, and copy-ready prompts simultaneously. The design premise is explicit — planning and execution are distinct modes, and collapsing them is where developers lose the thread. You write notes while the agent runs, observe what it returns, and dispatch the next prompt without losing the context that made the last decision make sense.

The differentiating feature is Blueprint, a paid-only workflow that converts loose notes into phased, rationale-tagged specs and generates implementation prompts per phase. It includes a clarification loop — noter asks questions about your spec before it outputs anything — and produces an AGENTS.md file that codifies rules for the agent across the project. This is the part that solves the ‘I had to re-explain the whole project on session three’ problem that compounds across longer builds.

noter fits developers who are already in a CLI workflow and want to stay in control of what gets handed to a coding agent rather than prompting freeform. It breaks for teams who need the planning layer to also do the executing — noter does not run agents, trigger pipelines, or integrate with CI. It is a thinking surface, not an orchestration layer. If your team needs the agent to hand off to another system automatically, noter has no mechanism for that.