MCP
Agents create plans, update tasks, stream output, and search institutional memory from Cursor and other MCP clients.
The self-hostable harness that turns plans into agent runs and keeps every commit linked to the work that produced it.
Why it exists
Chat tabs forget. Markdown plans drift. Issue trackers never see the agent run. OpenThrottle keeps plans, tasks, output, and commits in one Postgres-backed system — reachable from your editor over MCP, and owned entirely by you.
How it works
Ralph drives one task at a time. Progress streams live. Merged commits carry Plan-Id and Task-Id so you can ask what shipped — and why the code exists.
Capture intent as durable plans and tasks — not scattered Markdown.
Run agents through Ralph, one scoped task at a time, with live output.
Search plans, tasks, and docs by meaning with semantic memory.
Link shipped commits back to the plan and task that produced them.
Surfaces
Bring your agent host and editor. Every surface reads and writes the same plans and tasks.
Agents create plans, update tasks, stream output, and search institutional memory from Cursor and other MCP clients.
A dashboard for humans: what’s in progress, what shipped, and what’s next — without leaving the loop.
Queue-backed agentic execution with worktrees and commit traceability built for one-task-at-a-time runs.
Self-host
OpenThrottle turns ideas into plans and tasks your agents can execute. Start with the repo, wire up MCP in Cursor or VS Code, and let Ralph loops ship work with full traceability.
# Clone OpenThrottlegit clone https://github.com/openthrottle/monorepo.git # CD in and get setupcd monorepo && ./scripts/setup.sh # And start moving faster!pnpm run start # developer → :6020# server → :6021