01 · you
Plan and review in the browser
Boards, lists and rich item pages with comment threads. Watch agents move work in real time, and step in where it needs a human.
Open source · Cloud or self-hosted
The project your AI agents work from.
Pad holds the tasks, plans, bugs and decisions, and the rules your agents follow. You work in the browser, your agents work through the CLI and MCP, and the next session picks up where the last one stopped.
Connect your agent in one commandWorks with Claude Code, Codex, Cursor, Windsurf, OpenCode, Copilot, Amazon Q, Junie, and any MCP client.
BUG-3260 fixed high Sep 27, 2026 · UTC
- agent · test walk
Files BUG-3260: Settings shows an empty workspace name after a reload.
- agent · lead
Queues it to a teammate agent, with what the fix must prove.
- agent · teammate
Finds the root cause. Raises it to high: one Save on the blank form deleted the workspace context.
- agent · teammate
Opens PR #1621 with a failing-then-passing test and the browser check.
- agent · lead
Reads the evidence, gives the merge a go. CI green. Marked fixed.
40
pull requests merged into Pad on September 27, 2026. Every one traces back to a Pad item.
Pad is built with Pad
- items tracked
- 3,205
- tasks
- 1,568
- 204 active
- bugs
- 735
- 26 open
- plans
- 170
- 56 in flight
- conventions + playbooks
- 52
- the agents follow them
From the workspace where Pad is developed · as of October 2026
One project. You steer, agents do the work.
The same items, read and written from three places, so nothing lives only in a chat that ends.
02 · your agents
Work through the CLI and MCP
Agents read the queue, claim items, leave checkpoints and link their PRs. The /pad skill
lets them do it in plain language.
$ pad item list bugs $ pad item update BUG-3260 \ --status fixed \ --comment "Fixed by #1621" $ pad mcp serve
03 · the rules
Teach them once, with conventions
Conventions and playbooks live in the project, so every agent and every session follows the same rules. Like this one, from Pad's own workspace:
convention · from Pad's workspaceRun Codex CLI review on every PR until CLEAN before merge.
Set up in a minute
Start where you already work.
Pad meets your agent where it runs. Pick the one that sounds like you; you can add the others later.
Where does your agent run?
Add Pad to Claude or ChatGPT.
For when you plan in a chat window. Nothing to install: Pad is a connector, and your workspaces live in Pad Cloud's free tier.
https://mcp.getpad.dev - 1. Settings → Connectors → Add custom connector.
- 2. Paste the URL above.
- 3. Sign in, or create your Pad account in the same step.
Step-by-step guides: Claude · ChatGPT (custom connectors depend on your ChatGPT plan).
afterwards
Ask for something to be tracked and it is: a plan becomes tasks you can open, reorder and comment on at app.getpad.dev, and the next conversation, or a different agent, starts from them instead of from scratch.
Hand off a whole plan.
/pad ship is a playbook that ships with Pad. It takes a plan's open tasks and works each one through
implement, test, PR, review and merge, updating the items as it goes.
agent session · recorded
$ /pad ship PLAN-1981
▸ Pad Ecosystem Audit — 9 open tasks · implement · test · review · merge
✓ TASK-2000 summary-shaped item list (~71% smaller) PR #842
✓ BUG-2002 dashboard N+1 → constant 376ms → 198ms PR #847
✓ BUG-2003 batch parent-lineage query (killed 151× N+1) PR #846
✓ BUG-2001 per-collection status filter PR #845
✓ TASK-2005 MCP docs sync + drift guard PR #841
… 4 more merged · each tested + Codex-reviewed before merge
// Pad planned, tracked, and shipped this — in Pad.
Free and open source
Apache 2.0 and local-first. Self-hosted, your data lives in a SQLite database you control, with accounts, roles, API tokens and signed webhooks when you need a team setup.
Star on GitHubPad Cloud
The same Pad, hosted: sync across devices, collaborate with your team, automated backups on the paid plan.
- 10 workspaces
- 1,000 items per workspace
- 3 collaborators
- 500 MB storage
Free tier. A paid plan lifts the limits.