Context layer
What shared memory is good at
AGENTS.md, tool rules, project docs and agent memory can tell the next session what the project has decided. That reduces repeated explanation and gives agents more consistent context.
Claude Code · Cursor · Codex
Shared memory helps. A shared repo decision boundary is what stops drift.
Switching between Claude Code, Cursor and Codex can leave the same project represented in different agent contexts. CrossCheck keeps supported project decisions with the repository so a later agent can be checked against the same direction instead of silently choosing another one.
Enforcement layer
Where CrossCheck starts
Knowing the decision and following the decision are different things. CrossCheck pins supported canonical choices in a repo-level contract and checks later supported agent work against that boundary.
Concrete failure modes
The expensive disagreement is often a project decision, not a syntax error.
Database engine
Claude follows PostgreSQL; a later Cursor or Codex task assumes MySQL.
ORM
One agent continues with Prisma while another introduces Drizzle.
Authentication
One path is built around Clerk while another starts Auth.js.
Package manager
A repo standardized on pnpm later receives npm assumptions or artifacts.
Early-access detection is intentionally limited to these supported decision classes. CrossCheck does not claim general semantic conflict detection or that every architectural disagreement can already be blocked.
One repository boundary
Switch agents without switching the canonical decision.
CrossCheck currently documents native adapters for Claude Code, OpenAI Codex, Cursor, GitHub Copilot / VS Code hooks in Preview, Gemini CLI, Windsurf / Cascade and Cline. Git and GitHub CI provide shared repository boundaries underneath those local integrations.
See exact compatibility and limits →- 1
Scan the repo
Run the free browser/local scan first. No signup and no source-code upload.
- 2
Pin supported decisions
The paid product stores supported canonical choices with the repository.
- 3
Check future agent work
Supported proposals and edits are checked near the agent workflow, with Git/CI as backstops.
- 4
Migrate intentionally
When the architecture really should change, open a controlled migration instead of disabling the guardrail.
Proof before payment
Find out whether your repo has one of the supported conflicts first.
The free scan runs locally in the browser or from the repo, requires no account and uploads no source code. Continuous protection is US$29 per protected repository per month if the guardrail is useful to you.