Next: Evidence & Outcomes
Inspect the record. Check the work.
Review what the integration recorded and verify the task outcome separately.
How your work connects
See what belongs together.Before the agent reads.
LeanCTX is the Context Gateway for AI systems. LeanCTX builds a local graph of your project: which files import each other, which functions call each other and which files change together. The next task starts from those relationships, not from a blank search.
The approach
Relationships first. Then the detail.
A file rarely matters on its own. Its callers, its tests and the files that usually change with it decide what a change affects and what the agent should read next.
Project graph
Map the project once. On your machine.
The Engine indexes your project into a graph it stores locally: imports and module links, references between code, files that the git history shows changing together and files that sit side by side.
- Imports
- Which files and modules depend on each other.
- Change history
- Files that were changed together in past commits.
- Freshness
- A status check compares the graph with the current commit, so you know when to rebuild it.
Impact
Know what a change touches.
Before an edit, trace the callers and callees of a function and the files that depend on it. The agent reads the code a change affects instead of guessing from file names.
- Callers & callees
- Who calls a function and what it calls in turn.
- Affected files
- The modules that depend on the file you change.
- Architecture
- An overview of the main modules and how they link.
Linked knowledge
Connect decisions to the work.
Facts and decisions kept as project knowledge can be linked to each other and recalled with their relations. Knowledge stays with its project; searching across projects needs explicit permission.
- Relations
- Which facts and decisions belong together.
- Project scope
- Knowledge stays with the project it was recorded in.
- Next session
- Work starts from what is already known and linked.
Questions & answers
Project graph questions.
Does the project graph leave my machine?
The Engine stores the graph locally, in its data directory. Context selected for a task still goes to the model you use.
Is the graph always up to date?
Not automatically. A status check reports whether it is fresh or stale compared with the current commit; rebuild it after larger changes.
Start with LeanCTX
Map one project today.
Index a project you know, ask what a change would affect and compare the answer with your own understanding.
Local-first. Model-agnostic. Your context.