Govern what your agents
see, use and remember.
LeanCTX is the governance layer for agent fleets: PathJail confines file access, a shell allowlist blocks dangerous commands, secrets are redacted before models see them, budgets cap spend per role, and an Ed25519-signed audit ledger proves what happened. Local-first: nothing leaves the machine.
What it costs you today.
"Trust us" is not a security model
Agents touch production code and customer data. Without enforced boundaries, every prompt is one injection away from an incident.
Spend without accountability
Token bills arrive as one number. Which team, which agent, which task? Most stacks cannot attribute a single dollar.
Audits have nothing to read
When compliance asks what an agent read and ran in March, a log folder of raw prompts is not an answer.
The capabilities that do the work.
Everything below ships in the open-source binary today. No roadmap items, no waitlists.
From zero to first gain.
One guide. Two journeys. Full reference.
Questions teams ask before adopting.
What leaves the machine?
Nothing, and you can verify it. LeanCTX runs locally with zero telemetry. The audit ledger, cache and knowledge store are local files; network egress happens only where your own configuration sends it.
How does the audit ledger resist tampering?
Entries are hash-chained and Ed25519-signed. Any modification breaks the chain, and lean-ctx savings verify proves integrity end to end, exportable for compliance.
Does governance slow agents down?
No. Policy checks run in-process in the same Rust binary that serves reads. Microseconds, not round-trips. Governance and compression share one pass.
Take back control of your context.
Free for local use, forever. CI enforces it. One binary, ten minutes to the first measured gain.