Tack encodes your architecture contract in .tack/, tracks drift, and generates deterministic handoffs. Switch agents, switch branches, switch people — the context stays.
█
Every change the agent makes gets logged with a commit ref and rationale. When something unexpected shows up three sessions later, you don't grep through the codebase — you check the log, find the exact commit, and see what was added and why. The agent's memory doesn't live in a context window. It lives in git.
Everything lives in .tack/ inside your repo. Clone it, branch it, merge it, review it in a PR. No SaaS, no database, no new surface to maintain. Your architecture decisions get a commit history.
spec.yaml · context.md · decisions.md · _drift.yaml · handoffs/
Cursor today, Claude Code tomorrow, Codex next week — your .tack/ comes with you. Tack is the backbone that stays constant while everything else in your AI toolchain churns.
Handoffs are built from your spec, drift state, context docs, and git diff. No LLM in the enforcement loop. No hallucinated summaries. Every claim traces to a file and line number.
Context windows get compacted. Sessions restart. Agents lose track of what they decided three hours ago. Tack sidesteps all of it — every decision is logged with the commit ref where it happened. Any agent can look back at exactly what the code was when the choice was made.
Tack serves your project context over MCP — the protocol that lets tools show up to agents as structured APIs instead of a wall of text. You don't memorize commands. You say "continue this work" and your agent reads the guardrails, checks drift, and logs decisions back.
Your agent calls log_decision and log_agent_note instead of hallucinating its own memory. You don't have to know the commands — your agent already does.
.tack/ folder your tools can agree on.Plug into your existing tools, or let Tack maintain the repo docs you keep meaning to update. It's not editing code — it's handling the paperwork.
Git-native. Agent-agnostic. Deterministic. Every person and tool on your project works from the same context.