Best for
- Developers who need task continuity between AI coding agent sessions
- Teams that prefer local, reviewable files over cloud services
- Users of Claude Code, Cursor, or Codex seeking consistency across sessions
A
68FMRS · C
Agentpack is a specialized MCP server for privacy-focused developers who value task continuity among various local AI agent sessions. It offers strong concepts like Task Passports and checkpoints but lacks a fully documented tool list in official sources, making undocumented initial integration a challenge.
Agentpack is a local-first MCP server that preserves task continuity for AI coding agents. It maintains a reviewable task ledger (.agentpack/) inside your repository, recording goals, decisions, dead ends, verification evidence, and checkpoints. Agents record durable state while working through MCP tools, and any next session — the same agent after compaction, a different client, or a future you — loads that state and continues from where it left off. Agentpack also generates project instructions (AGENTS.md, CLAUDE.md, Cursor rules) to guide when agents should load and write state. A CLI provides the same state for human inspection and manual handoff. Core features include task passports, task gates (hooks that warn or block edits outside the active task), and budgeted context output.
Setup
Requires Node.js >= 20. Install agentpack-cli globally via npm. In your repository, run agentpack init. Install client config with agentpack install claude --write (or codex or cursor). Restart/reconnect the coding-agent client, then the agent loads context at session start. Verify with agentpack doctor.
Fit and risk
Not for
- Teams needing cloud sync or collaboration features (it is local-first)
- Users not on Node.js 20+ or who prefer a single binary
- Those who want integration with issue trackers or project management tools (not provided)
Required permissions
- Access to the local repository filesystem (reads/writes .agentpack/)
- Global npm package installation (agentpack-cli)
- May configure git hooks or client hooks for task gating
Risks and side effects
- Mistakes in task state could lead to incorrect assumptions by agents
- Local files could be accidentally modified or lost
- Secret redaction is best-effort and not guaranteed
- Task gate could block legitimate edits if over-restrictive
Troubleshooting
- Run agentpack doctor to verify setup.
- Ensure Node.js >= 20.
- Restart/reconnect the client after installation.
- Use CLI commands like agentpack resume --preset agent --query "topic" to inspect state. Check docs/INTEGRATIONS.md for client-specific settings.
Use cases
Working on a long-running refactor or bugfix across sessions
Switching between Claude Code, Cursor, Codex, or multiple MCP clients
Returning to a task days later without context
Keeping agents focused on a scoped task in a monorepo with task gates