Claude Code, Cursor, and Copilot plan from the context files in your repo. Every merged PR widens the gap between what those files say and what the code does. You pay for that gap twice: once in wasted tokens, once in rework. Kontrua closes it.
Committed to branch
chore: update agent context
kontrua-bot · just now · feat/auth
Files updated
The same understanding that refreshes your context layer also renders the docs your team reads. Updated on every PR approval.
README
README.md
Project overview, installation, features, and usage. Always reflecting your current codebase.
API Reference
docs/API.md
Every exported function, class, and type, with signature, parameters, and description.
Architecture
docs/ARCHITECTURE.md
System structure, module boundaries, data flow, and key design decisions.
Changelog
CHANGELOG.md
Version history in Keep a Changelog or Conventional Commits format.
Changed file
Extracted exports
processPayment(amount, currency)
validateCard(card: CardData)
PaymentResult
Reads your full codebase, not just the diff. Every type, export, and dependency is verified against the source before it lands in your context layer. Facts, not guesses.
PR approval is exactly when context goes stale, so it is the default trigger. Schedule, CI step, and CLI work too.
Install the GitHub App. When a reviewer approves, Kontrua traces the diff and commits refreshed context to the branch - no YAML, no extra steps.
Kontrua listens to the webhook automatically, nothing to configure in CI.
sarah wants to merge 8 commits into main
Context layer updated
Hand-maintained context vs. Kontrua.
Start free. Scale when you're ready. Open-source repos always get Max features, free.
For solo devs and small projects
For growing engineering teams
For teams shipping at scale
Custom solutions for your team
The context layer of your repo: AGENTS.md, a codemap, conventions, and architecture facts - the files AI coding agents read before they plan. It also renders doc views (README, API reference, architecture, changelog) for your human readers, from the same understanding of the code.
Any tool that reads context files from your repo: Claude Code, Cursor, Copilot, and anything else that follows the AGENTS.md convention. Kontrua commits standard files into your repo, so there is no SDK, no plugin, and no vendor lock-in.
It analyzes the diff of each approved PR and builds a semantic model of what changed. It rewrites only the affected context artifacts and doc sections, leaving everything else untouched.
Kontrua never stores your source code. Diffs and file contents are analyzed in memory during a run and discarded when the run completes. We request the minimum permissions needed to read code and commit updates. All data is encrypted in transit.
No. Kontrua commits updates as regular commits on your branch. You can edit, revert, or ignore them like any other change. If you've customized a section, Kontrua updates only the parts the code diff actually touches.
Yes. Doc views - README, API reference, architecture, changelog - stay fully supported and update on the same runs. The context layer is the agent-facing output; doc views are the human-readable one.
Yes. Kontrua uses a template system. You can choose from built-in templates for context artifacts and doc views or write your own. Templates are versioned in your repo so your team can review changes.
Kontrua works with any GitHub or GitLab repository. It currently supports TypeScript, JavaScript, Python, and Go, with more languages on the roadmap.
Free for up to 2 repos and 20 runs per month. Pro is $15/month for 10 repos and 150 runs. Max is $30/month for unlimited repos and 1,000 runs. Open-source repos always get Max features for free.
Kontrua commits updates as regular git commits. If something looks off, revert the commit or edit the file directly. Your manual edits are preserved on subsequent runs. You stay in full control.
Connect your repo. Kontrua keeps the context layer current from there.