SuperAPI AI Directory

docket

Shared todo list and backlog for coding agents, filed per project by git remote, with claims to avoid duplicate work and a local web dashboard.

Open website

About this tool

Docket is a local-first, self-hostable coordination workspace for AI coding agents. Its core purpose is to host to-dos and to-do lists: before formal work items are created, the ideas or tasks generated by agents during a session land here first, and afterward it is decided whether to escalate them into a Notion page, GitLab Issue, or another form of formal work item.

Main capabilities:

  • Shared task list: all entries are aggregated into a single list, and agents such as Claude Code, Codex, Cursor, and Warp can all write to it.
  • Automatic categorization by project: entries are automatically assigned to the corresponding project based on the git remote of the agent's working directory, with no manual input required; entries without project context go into Unfiled. The same repository cloned at different paths is still treated as the same workspace.
  • Claim mechanism: prevents multiple agents from processing the same task repeatedly.
  • MCP integration: connects to agent hosts through the MCP protocol, and all hosts use the same toolset.
  • Local Web dashboard: runs by default at http://localhost:8787,提供工作区切换、每项目未完成计数、实时更新(SSE)、搜索、排序、内联编辑、撤销删除、明暗主题和移动端响应式布局。
  • Bidirectional bridging: the sourceUrl field can link to GitLab Issues, Notion pages, Obsidian share links, Slack threads, GitHub PRs, etc., and clickable links are shown on the cards.
  • Digest: agents can read merge requests, PRs, Notion work items, local commits, and docket entries, verify their status, and publish a digest as the dashboard homepage; when published, the digest calculates the differences from the previous one (new items, status changes, removed items).
  • Session continuity: Claude Code can get a SessionStart hook that injects up to 7 unfinished entries for that project, no more than 120 tokens, at the start of a session; it can be disabled with DOCKET_HOOKS=off.

Usage: Requires Node.js 18+ and at least one MCP host. Installation can be run via npx, or for Claude Code only use claude mcp add docket -- npx -y @pasichdev/docket. After installation, restart the agent so it can add to-dos, and the dashboard starts automatically. For non-Claude Code agents, copy the contents of skills/docket/SKILL.md into the corresponding configuration file (such as Codex's AGENTS.md, Cursor's .cursor/rules/docket.mdc, etc.).

Upgrades and data: Upgrading from 2.x to 3.0 automatically migrates the storage format from v7 to v8 on first run. Before migration, a copy of the pre-migration storage is kept, and its path is printed in the upgrade output; if you need to roll back to 2.x, you must first restore that copy. docket backup is provided to package the entire data directory into a password-protected single file (AES-256-GCM, scrypt-derived key), and docket restore can write it back.

Security and deployment: Data is encrypted and stored locally by default in ~/.docket on the local machine, and a self-hosted server is also possible. Docker provides four independent threat models: local encrypted storage, P2P sync, LAN viewer access control, and self-hosted client/server traffic. Data at rest uses AES-256-GCM encryption; the LAN viewer access control requires the host to explicitly approve access from other browsers; self-hosted mode uses per-device HMAC signatures and timestamp+nonce replay protection. P2P sync has been deprecated since v3.0; it is still usable, but claims are only advisory, and self-hosted mode is recommended for multi-machine scenarios.

Use cases: Suitable for temporarily recording and coordinating tasks during multi-agent, multi-project parallel development, especially in scenarios where to-dos need to be unified across different AI coding tools and duplicate work needs to be avoided.

Limitations: Some facts are not yet provided, such as specific pricing, charging model, and complete compatibility details for each host. The README explicitly states that P2P sync is deprecated, and its 15-second polling interval cannot provide atomic guarantees.