CI logs torch your budget
A failing pipeline dumps megabytes of logs into your triage agent. The signal is three lines; you pay for all of them.
Use case · Workflow automation
Every tool call becomes model input.
LeanCTX normalizes, compresses and audits the tool output your automations feed to models: 95+ shell patterns, provider connectors for GitHub, GitLab, Jira and Postgres, composable context via ctx_compose, and a complete audit trail. Pipelines get cheaper, deterministic and reviewable.
Same engine. Different workflow. Always the right context.
What it costs you today.
Each integration is bespoke
Jira here, GitHub there, a database somewhere. Every workflow glues its own fetch-and-paste code with no shared layer.
Nobody can audit what agents saw
When an automation acts on stale or wrong context, you need to know exactly what it read. Most stacks can’t answer that.
The capabilities that do the work.
Everything below ships in the open-source binary today. No roadmap items, no waitlists.
Your tools→LeanCTX→Model
95+ shell patterns
cargo, npm, docker, terraform, pytest… 88–99% smaller output
Provider pipeline
GitHub, GitLab, Jira, Postgres and REST sources, one consolidation path
ctx_compose
assemble task-scoped context packs deterministically
Audit trail
every read, command and saving is recorded locally
Budgets
per-role token budgets keep pipelines inside limits
From zero to first gain.
terminal
# compress any command in a pipeline
$ lean-ctx -c "npm test"# works for builds, containers, terraform…
$ lean-ctx -c "docker compose up --build"# review what your automation consumed and saved
$ lean-ctx savings summary# reproducible savings + recall + latency scorecard
$ lean-ctx benchmark scorecardOne guide. Two journeys. Full reference.
01
guide · Data sources & providers
Connect GitHub, GitLab, Jira, Postgres and REST.
Learn more02
journey · MCP tool catalog & gateway
Route external tools through one governed layer.
Learn more03
journey · Team, Cloud & Self-Hosting
LeanCTX inside pipelines and shared environments.
Learn more04
reference · Shell patterns
What gets compressed and by how much.
Learn moreQuestions teams ask before adopting.
88–99% on common tools: a cargo build shrinks from hundreds of lines to errors plus result, npm install to the dependency delta. 95+ patterns ship today, and unknown commands fall back to safe generic compression.
Yes. Providers for GitHub, GitLab, Jira and Postgres ship today, plus a custom REST provider. All provider data flows through the same consolidation pipeline into search, graph and knowledge.
Every read, command and saving lands in a local, Ed25519-signed ledger. You can export exactly what an automation consumed and verify the chain.
Take back control of your context.
Free for local use, forever. CI enforces it. One binary, ten minutes to the first measured gain.