The decision and enforcement layer for AI coding agents.
Quick start · How it works · Enforcement · Console · FAQ · Benchmark · Docs · Discord
New: Contexer Personal Cloud & Teams: sync decisions across machines, share a team decision layer.
Train your AI agents to work exactly how you want. And enforce it.
If you work with AI agents every day, you already know these:
- "My agent ignores my instructions the moment the context window fills up, and I'm back to re-explaining what it must never do."
- "I switched to a new agent and every rule and decision I'd built up stayed behind with the old one."
- "I run a whole stack of AI tools, and I still can't drive what they decide, let alone enforce it."
- "The answer is in there somewhere, buried under a thousand lines of session slop."
- "I have no idea what my team's agents are being told, or why they built it that way."
Contexer is the decision and enforcement layer: it captures engineering decisions as you work and keeps them current as your architecture evolves. It selectively injects the relevant decision, constraint, or convention the moment the agent needs it. At commit time, staged changes that violate an approved decision get flagged, or blocked outright for rules you arm. The settled answer arrives before the agent starts reasoning; it stops re-exploring and just builds.
Questions about capture accuracy, privacy, supported agents, instruction files, or the difference between open source and Teams? Read the public FAQ →
What it solves
Contexer gives developers one reviewable, versioned decision store across Claude Code, Cursor, Codex, and Gemini CLI. It brings approved context back into later sessions and can check staged changes against decisions before they land. The open-source product is local and individual; Contexer Teams adds reviewed shared decisions and GitHub workflows.
Benchmarks
The honest part: a complete, up-to-date CLAUDE.md ties Contexer on cost. The difference is that nobody has to write that file or keep it perfect. Every number is recomputable from raw session rows, scored by code (no LLM judge), independently validated, negative findings included. Read the benchmark →
Quick start
Requires Python 3.12+ and uv. Under two minutes.
uv tool install contexer # 1. install
contexer install # 2. wire into your AI assistants
contexer install auto-detects Claude Code, Cursor, Codex, and Gemini CLI, and wires everything it finds. Restart your assistant and open any git repo. On first use, Contexer analyzes the repo and proposes its starting knowledge. It runs silently from there.
Details: installation & verification · per-tool integration notes
How it works
- Capture: Contexer records engineering decisions and supporting provenance while you work.
- Review: Developers decide which proposed decisions become trusted.
- Replay: Relevant approved context is delivered to supported coding agents in later sessions.
- Check: Optional safeguards compare changes with approved decisions.
Read How Contexer works for the mechanism and the FAQ for capture limitations, authority, lifecycle, relevance, agent parity, privacy, and product boundaries. Day-to-day commands live in Usage & CLI.
Enforcement / guardrails
The local Guard is an optional pre-commit safeguard:
contexer guard --install-hook # wires .git/hooks/pre-commit for this repo (opt-in, not run by `install`)
It is advisory by default. Blocking requires an approved decision that the developer explicitly arms with a machine-checkable rule. See the FAQ for behavior and limits, the mechanism for design, and the CLI reference for commands.
See every decision, with its evidence
contexer ui --open
A local web console over every repo on your machine, not just the one you're in, because "what does my agent actually know?" is a question you shouldn't have to answer by reading JSON.
- Read it, then fix it. Browse and search every stored decision with its full revision history. Edit one; history is kept, nothing is overwritten. Delete one for good: a delete sticks, instead of quietly reappearing next session from a memory file or a mined conversation. Restore it if you change your mind.
- See the whole review queue at once, not one terminal prompt at a time: what's pending, and proposed changes to decisions you already approved shown as before/after diffs. The graphical counterpart to
contexer review. - The whole picture. Per-repo dashboard, global rules, cached team context, deleted decisions, and your settings: one switcher, seven views.
It binds 127.0.0.1, every route is authenticated, and the server itself never reaches the network. It is also off until you ask for it: contexer ui starts it on demand, and the printed link is short-lived on purpose. Set [ui] autostart = true and every session start hands you the URL for the repo you just opened.
Details, the [ui] settings, and the security model: the local console
Documentation
| FAQ | Product questions, capture limits, authority, privacy, Guards, OSS and Teams |
| Installation | Install, verify, update, uninstall |
| Integrations | Claude Code, Cursor, Codex, Gemini CLI: wiring and parity notes |
| How it works | Capture, bootstrap, session injection, review/versioning, cost, privacy |
| Usage & CLI | Natural-language commands, CLI reference, teams login, troubleshooting, limitations |
| Local console | contexer ui, the seven views, [ui] settings, security model |
| Benchmark | Live-session A/B methodology, findings (including negative ones), raw data |
Contributing
Bug reports, fixes, and documentation improvements are welcome. See CONTRIBUTING.md for setup, code style, and the PR process. Questions or ideas? Join the community on Discord.
License
MIT. See LICENSE for full terms.
The Contexer name and logo are trademarks of Contexer.ai. The MIT license does not grant rights to use the Contexer name, logo, or brand in any way that implies official affiliation.
1 maintainer
Metadata
1 maintainer
Release files for contexer 0.47.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| contexer-0.47.0.tar.gz | 2.1 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| contexer-0.47.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.8 MB
Release files / contexer-0.47.0.tar.gz
| Download URL | contexer-0.47.0.tar.gz |
|---|---|
| Size | 2.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0a8d12e053f1e262a7fa5e78f69a6f574dd2eb367d4ca8d9d8d2f8ef84daa114
|
|
BLAKE2b-256 checksum How to use checksums |
7b6cbd3fa45c6295823029b14e05e702c83842846561549d9cc695108ede8f22
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 15, 2026.
Transparency logRelease files / contexer-0.47.0-py3-none-any.whl
| Download URL | contexer-0.47.0-py3-none-any.whl |
|---|---|
| Size | 652.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
225524d2946d4a6f29e0d0f99d81aef592ff5a5a97f8a633471a148f77d28c43
|
|
BLAKE2b-256 checksum How to use checksums |
4d83141d5af9723ef99a8f313633a9f5cac9b78318522d716efffcc46c0ac57a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 15, 2026.
Transparency log
