Chat history disappears
Session memory is not a durable project layer.
// free apache-2.0 open core
.knowledge by Pro2Pilot gives Codex, Claude Code, OpenCode and custom agents a local control plane for the repository: one first-read routing bundle, trust and freshness status, repair queue, scoped local search, source-of-truth rules and a Visual Inspector.
Synthetic SaaS-shape fixture
The expensive part is what happens after: repeated repo crawls, stale-summary fixes, and wrong-file loops.
Different agents, same repo. Shared project memory without forcing them into one chat thread.
$ Read .knowledge/Quick-Start.md
$ node .knowledge/tools/flow.js release --no-color
[ ok ] routing
[ ok ] trust
[ ok ] inspector
[ ok ] doctor 93/100 // problem
Without a local knowledge layer, agents burn context rediscovering the repo, trust stale notes, miss critical paths, and lose handoff state between sessions.
Session memory is not a durable project layer.
Old summaries can sound current while code has moved on.
Retrieved context needs explicit trust and freshness rules.
Multiple agents need shared state that survives the session.
Teams cannot see which modules are trusted, suspect, or stale.
// solution
.knowledge turns project memory into files an agent can inspect, verify,
and refresh. Source code and tests remain the source of truth; knowledge helps the
agent route, check trust, and avoid starting from zero.
One first-read file tells agents where to go next.
Stale or low-confidence knowledge is marked before use.
Knowledge debt becomes visible work.
Notes become linked, navigable project context.
Health, token estimates, PR summary, and release evidence.
Codex, Claude Code, OpenCode, and custom entrypoints.
// how it works
Unzip .knowledge into the repo root.
The agent executes Quick-Start.md.
Health, search, metrics, and Inspector are refreshed.
Open the local Visual Inspector and repair queue.
unzip .knowledge.zip
# Tell your agent:
# Read .knowledge/Quick-Start.md and execute it for this repository.
node .knowledge/tools/flow.js release --no-color
open .knowledge/inspector/index.html // metrics
Numbers below are order-of-magnitude estimates from one local estimator, not tokenizer-verified production benchmarks.
// inspector teaser
The open core includes a static local Inspector. Pro2Pilot Inspector adds the paid visual workflow layer: graph filters, repair queue boards, PR impact, policy packs, and team dashboards.
// open core vs paid layer
The local standard stays open. Paid Pro2Pilot products focus on visual workflows, team operations, policy packs, and support.
| Layer | Access |
|---|---|
| .knowledge core | Free, Apache-2.0 |
| Static local Inspector baseline | Included with core |
| Pro2Pilot Inspector Pro | Paid commercial layer |
| Policy Packs Pro | Paid add-on |
| Team dashboards | Paid subscription |
// team fit
Codex, Claude Code, OpenCode, and custom workflows can share the same local layer.
Project context lives beside the code and can be reviewed.
Core runs locally with no required hosted service.
Trust, freshness, and repair work stop hiding in raw files.
// inspector waitlist
Get early access to the paid visual layer for .knowledge: interactive trust
graph, repair queue, critical-path explorer, PR impact, policy packs, and team
dashboards.