// Blog / open source discovery
Open-source agent context layer for coding teams
For coding teams, an agent context layer should be inspectable, versionable, and honest about what the agent should not trust.
// direct answer
Short answer
An open-source agent context layer should keep routing, trust, freshness, evidence, repair work, and local tools in the repository so the team can inspect the agent's operating context alongside the code.
Evaluate whether a free, open-source repository context layer is a better foundation than private prompt memory or hosted-only context.
// the problem
Agent context becomes hidden and vendor-specific
Agent context often becomes a private mix of chat history, local scratch files, hosted memory, and one-off prompts.
That makes it hard for a team to review what the agent is relying on, especially when multiple tools touch the same repo.
For coding teams, the context layer should be inspectable, versionable, and able to mark low-trust material instead of hiding it.
// open repository layer
Keep shared agent context beside the code
.knowledge keeps the core context layer in the repository: routing, module summaries, evidence, linked documentation, items to re-check, metrics, and workflows.
The free, open-source .knowledge core runs locally and does not require a hosted service for setup, health checks, search, or the static Inspector.
Commercial Pro2Pilot tools can add team Inspector views, multi-repository dashboards, policy checks, and advanced PR impact workflows.
// concrete example
Where GitHub, .knowledge, and Inspector fit
GitHub keeps the code, issues, PRs, and review history. .knowledge keeps repository-owned context that agents can read before planning.
The local Inspector shows the free core in a static dashboard. Pro2Pilot Inspector Pro adds interactive team review for follow-up work, policies, and PR impact.
// files you can inspect
What you can inspect in the repository
Some repository-specific files appear only after setup or a health check. Run the documented setup workflow to create routing, confidence, freshness, search, metrics, and PR summary outputs.
.knowledge/agent-integrations/
The same local context can be exposed to Codex, Claude Code, OpenCode, and command workflows.
- Multi-agent consistency
- Repeatable onboarding
- Locking the team into one chat product
.knowledge/tools/
Import, release, metrics, search, graph, and inspector commands are inspectable code.
- Auditing how reports are generated
- Running checks in local or CI workflows
- Treating generated output as permanent truth
.knowledge/github-action-templates/
The free core can be copied into repository automation without requiring a hosted management service.
- PR health checks
- Release evidence
- Assuming CI replaces human review
.knowledge/inspector/
A local read-only dashboard makes trust, graph, and repair state visible.
- Visual sanity checks
- Team discussion around stale modules
- Editing code from the dashboard
- Bypassing source-of-truth rules
.knowledge/LICENSE
The free core license is inspectable in the public archive together with NOTICE.
Apache-2.0 core: see LICENSE and NOTICE.
- License review
- Open-core due diligence
- Assuming paid Inspector Pro terms
.knowledge/maintenance/pr_summary.md
The health-check workflow can generate reviewer-facing context using the included free tools.
- Review handoff
- Open-core automation proof
- Replacing reviewer judgment
// commands to try
Commands and expected checks
node .knowledge/tools/flow.js release --no-color - what it does
- The free core refreshes routing, confidence, metrics, linked documentation, search, and Inspector outputs.
- where to look
- .knowledge/maintenance/quality_report.json
node .knowledge/tools/serve-inspector.js - what it does
- The local static Inspector can be viewed from the generated repository files.
- where to look
- .knowledge/inspector/index.html
node .knowledge/tools/generate-pr-summary.js - what it does
- A PR-facing summary of trust, health, and repair state is generated.
- where to look
- .knowledge/maintenance/pr_summary.md
What is included in the free core
// practical reference
Free .knowledge core vs Inspector Pro
| Free .knowledge core | Inspector Pro |
|---|---|
| .knowledge routing, trust, freshness, evidence, and local tools. | Team dashboards, policy checks, and advanced review workflows. |
| Local read-only Inspector. | Interactive Inspector Pro with follow-up boards and PR impact views. |
| GitHub Action templates and local command workflows. | Commercial support, team operations, and paid build delivery. |
// quick FAQ
FAQ
Is the free core useful without Pro2Pilot Inspector Pro?
Yes. The free core contains repo-local routing, trust, freshness, tools, integrations, metrics, and a local read-only Inspector.
Why keep agent context in GitHub?
Because coding teams already review code, tests, docs, and automation there. Keeping agent context in the repo makes it inspectable and versionable.
What works without Pro2Pilot Inspector Pro?
The free core still provides local routing, trust and freshness files, tools, agent integrations, GitHub Action templates, metrics, search, PR summaries, and the local read-only Inspector.
// next step
Use this page when evaluating open agent infrastructure
Start with the GitHub repository and the local .knowledge layer. Add Pro2Pilot Inspector when the team needs visual review and coordination on top of the free core.