Without a charter
Five agents. Five versions of the project.
Duplicated guidance quietly diverges while every provider reports success.
Local-first infrastructure for agentic development
One repo charter.Every coding agent.
Keep project instructions, on-demand context, and tested guardrails in one portable system—so every coding agent works from the same repository truth.
kit/agentkit census --repo ~/dev/your-repoRead-only. No dependencies. No files changed.
repo / context map live
AGENTS.mdCANONICAL
CLClaudeadapter
CXCodexnative
OCOpenCodenative
Policy probe passeddeny + allow paths testedverified
204negative-first tests
0CLI runtime dependencies
1canonical charter
5+agent harnesses reached
One source of truth
Your repository should not change personality when the agent does.
Parallel instruction files drift. Huge startup prompts crowd out the task. A hook that merely exists gets mistaken for a guardrail that works. RepoCharter gives each concern one clear home—and makes the adapters prove their reach.
With RepoCharter
One authored truth. Small, explicit adapters.
◆AGENTS.mdalways loaded
├docs/project/on demand
├.agents/skills/on demand
└compatibility.jsonmechanical policy
Provider files point inward. They do not become competing sources of truth.
Built for real repositories
Portable context without hand-wavy safety.
RepoCharter separates what every agent can read from what each harness can actually enforce.
Portable by construction
Switch agents. Keep the map.
Claude Code, Codex, OpenCode, Hermes Agent, and ZCode all reach the same checked-in instructions and procedures through explicit, reviewable adapters.
Lean by default
Load the task, not the archive.
Keep startup rules compact. Pull specifications, decisions, state, and skills only when they matter to the work in front of the agent.
Startup contextcompact
charterroom for the work
Guardrails with receipts
Installed is not the same as enforced.
RepoCharter fires real forbidden and benign calls, records provider-backed evidence, and keeps unsupported surfaces explicitly advisory.
✓ destructive command denied
✓ benign command allowed
✓ malformed input failed closed
verified for this checkout
How it works
Human-authored truth. Mechanical reach.
RepoCharter does not generate the meaning of your project. It gives that meaning a durable structure, connects it to each harness, and checks the connection.
Write the charter
Keep the rules every agent needs in one human-authored AGENTS.md. RepoCharter never invents your project truth.
AGENTS.mdMove detail on demand
Specifications, decisions, current state, and repeatable procedures stay at named paths until the work actually needs them.
docs/project/ · .agents/skills/Wire each harness
Small provider adapters connect the same charter and policy to the controls each coding-agent harness really exposes.
CLAUDE.md · .codex/hooks.jsonProve what runs
Live deny and allow probes separate installed configuration from verified enforcement. No checkmark by assumption.
self-test · measure · verifyCompatibility, stated plainly
Shared context everywhere. Verified enforcement where proven.
Providers expose different controls. RepoCharter reports context reach and safety enforcement separately so an adapter never gets credit for a test it did not pass.
CX
Codex
proven path- Context
- Native context
- Guardrails
- Verified per checkout
CL
Claude Code
- Context
- Shared context
- Guardrails
- Advisory
OC
OpenCode
- Context
- Native context
- Guardrails
- Advisory
HA
Hermes Agent
- Context
- Native context
- Guardrails
- Advisory
ZC
ZCode
- Context
- Context adapter
- Guardrails
- Advisory
+
Other harnesses
- Context
- AGENTS.md fallback
- Guardrails
- Explicit status
Verified enforcement is earned per provider, checkout, hook hash, and probe matrix. Advisory means “use the shared context and pre-commit gate,” not “mechanically blocked.”
Your repository stays yours
No context service between you and your code.
The RepoCharter CLI is dependency-free Python 3. It runs offline, vendors into the repository, and leaves project truth under human review and version control.
- No hosted memory or required account
- Existing hooks and settings are preserved
- Dirty worktrees are refused by default
- Every mechanical change is previewable
$ kit/agentkit verify --repo .
schemavalid
context budgetwithin limit
provider adaptersreachable
declared checkspassed
0 errors · ready for review
Start with a read-only baseline
Give your agents one map.
See what loads today before RepoCharter changes a file. Then preview the mechanical layer and adopt it on your terms.
kit/agentkit census --repo ~/dev/your-repo