tack

[](https://www.npmjs.com/package/tack-cli) [](LICENSE)

Tack gives your agents persistent project memory that stays accurate instead of going stale.

Static instruction files drift the moment the code changes. Tack keeps a shared record in ./.tack/ and checks that memory against the actual codebase, so the next agent starts from context that is still trustworthy.

1. Install Tack. If you prefer not to install globally, use npx tack-cli@latest instead of tack.

npm install -g tack-cli

1. Initialize the repo and install your agent startup instructions once.

tack init
tack setup-agent

1. Keep tack watch open in a second terminal as live proof.

tack watch

1. Start the MCP server from the repo root with a visible agent label.

TACK_AGENT_NAME=claude tack mcp

On Windows PowerShell, set the label like this instead:

$env:TACK_AGENT_NAME="claude"
tack.cmd mcp

1. Confirm the canonical trust loop in tack watch:

• READY means the MCP session connected
• READ means the agent read tack://session or another Tack context resource
• WRITE means the agent wrote memory back with checkpoint_work, log_decision, or log_agent_note

If you see READY, READ, and WRITE, the agent is actually using Tack.

At the end of a session, package a handoff:

tack handoff

Read the full guides:

• Product Direction
• Getting Started
• Agent Workflow
• MCP Clients
• Watch Mode
• CLI Reference
• Detectors And YAML Rules

• Keep implementation facts aligned with the real codebase
• Stop stale project instructions from misleading the nex