Lockstep for Claude Code
Lockstep briefs Claude Code on every approved decision through MCP, so the agent starts already knowing the constraints instead of rediscovering them one broken PR at a time.
What Lockstep captures from Claude Code
- approved decisions delivered via get_product_context
- constraints an agent must respect across repos
- drift flagged before the change ships
How the loop runs
Lockstep captures the decision from Claude Code, routes it to its owner for one-click approval, then briefs every engineer and every AI coding agent before they touch the code, and flags any pull request that drifts from it. See the full pipeline on how it works.
Access & trust
MCP server exposing get_product_context; read-only.
Frequently asked questions
- How does Claude Code start a session already briefed?
- Lockstep hooks Claude Code's session start and delivers the approved decisions governing the code it's about to touch, ranked and truncated to what matters. Mid-session, the agent can call get_product_context whenever it needs more.
- What's the difference between this and a CLAUDE.md or AGENTS.md file?
- A static file is written once, goes stale, and is the same for every task. Lockstep's briefing is generated per session from the live, approved decision record, scoped to the surfaces being worked on, and backed by a PR check when something slips through.
- Are decisions the agent makes captured too?
- Yes. Claude Code is the one agent with automatic capture today. Choices it makes mid-session are recorded through the same MCP connection and land in the review queue for a human to approve.
Other integrations