Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y [email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
claude mcp add agentpack-cli -- npx -y agentpack-cli@1.11.1รันในเทอร์มินัล
{ "mcpServers": { "agentpack-cli": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดRepo-native task continuity for AI coding agents.
Agent memory remembers how you work. Agentpack remembers where the task stands.
Your agent spent an hour on a task. It found the cause, rejected two approaches, and wrote down the next step. Then the context was compacted, or the chat closed. The next session starts from zero and does the same investigation again.
Agentpack keeps the task state in your repo. Connected agents record the goal, decisions, dead ends, verification evidence, and checkpoints in .agentpack/ while they work. Then the next session loads that state and continues: the same agent after compaction, a different client, or you next week.
Here it is in action. In session 1, an agent works on a flaky test and records a decision, a dead end, and a checkpoint through the Agentpack MCP tools. In session 2, the next day with an empty context, one load_context call brings the task back:
To try the same flow by hand from the CLI, see docs/DEMOS.md.
AGENTS.md, CLAUDE.md, Cursor rules) tell agents when to load and record state.Claude Code memory, Codex memories, and CLAUDE.md or AGENTS.md keep how to work: your preferences, project conventions, and facts that stay true. Agentpack keeps where the work is: the goal of the current task, its constraints, decisions, dead ends, next actions, and verification result.
Use both. Memory keeps how you like to work. Agentpack keeps what the task needs next.
Agentpack needs Node.js 20 or later.
npm install -g agentpack-cli
cd path/to/your/repo
agentpack init # once per repo
agentpack install claude --write # per client: codex | claude | cursor | claude-desktop
agentpack install git-hooks --write # optional: task gate check before each commit
Restart or reconnect your coding agent, and approve the Agentpack server or hooks when the client asks. From then on, the agent loads the task state when a session starts, records decisions and evidence while it works, and creates checkpoints at meaningful points.
To check the setup, run agentpack doctor. To see the task state yourself, run agentpack resume --preset agent --query "<topic>".
In a Git repository, init adds the local Agentpack files to .git/info/exclude. The list includes .agentpack/, .mcp.json, .claude, .codex, .cursor, AGENTS.md, and CLAUDE.md. Agentpack does not change your .gitignore. Files that Git already tracks stay tracked.
For each client, docs/INTEGRATIONS.md shows what the installer writes and why.
Each task has a Task Passport: the goal, status, constraints, write scope (the paths the task may change), next actions, and verification. You can start, park, switch, and finalize tasks, so each handoff is explicit.
The task gate checks edits against the current Passport. The client installers add native hooks for Claude Code, Codex, and Cursor. install git-hooks adds a pre-commit check. By default, the gate only warns. Set "gateMode" in .agentpack/config.json to "block" to stop edits outside the write scope or outside an active task, or to "off" to turn the gate off. Hooks are a guardrail, not a sandbox. See docs/CLI.md.
The summary stays inside a token budget. The agent gets the useful state back, not the full history.
api/, frontend/, cron/) short tasks with their own write scope. The task gate warns when the agent leaves that part.agentpack usage report reads local Claude Code and Codex transcripts and shows the token use of a task, including the Agentpack share. Nothing leaves your machine.agentpack tui shows tasks, evidence, and checkpoints in the terminal. See docs/TUI.md.Agentpack context also uses tokens. The compact output keeps the task state available without the full ledger history.
ignore-scripts=true.npm audit signatures.See SECURITY.md for the full policy, including what Agentpack reads outside the repo.
Clone the repo and use Node.js 20 or later:
npm ci --ignore-scripts
npm test
npm run mcp:smoke
node dist/src/agentpack.js --help
See docs/SETUP.md for the development setup and docs/RELEASING.md for the release steps.
Mirror: Codeberg. Issues, releases, and npm provenance stay on GitHub.
{ "mcpServers": { "agentpack-cli": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Agentpack Cli ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-10 Local task-state ledger for AI coding agents.