Context Gateway for AI Systems
Control what your AI can see.
Select → Control → Prove describes the product. This reference documents the local LeanCTX Engine; the LeanCTX SDK exposes supported application interfaces. The agent, model, task logic and retry policy remain the integrator's responsibility.
Start with What is LeanCTX?, then the canonical product boundary.
| Area | Use it for | Status |
|---|---|---|
| Setup & onboarding | Local CLI and coding-agent setup | Available |
| Daily use | Context-aware reads, search, and shell output | Available |
| Memory & knowledge | Local project/session context | Available, within documented limits |
| Code intelligence | Structural views and impact exploration | Available |
| Advanced integrations | Local proxy, providers, and plugin substrate | Available only where the individual contract says so |
| Lifecycle | Install, diagnose, update, and remove | Available |
| Context engineering | Local context decisions and verification primitives | Available / Preview by feature |
| Customization & governance | Local configuration and safety rules | Available |
These files are retained to make the repository auditable. They are not navigation to an additional public product.
| Record | Status | Boundary |
|---|---|---|
| Multi-agent collaboration | Historical / Research | LeanCTX is not a multi-agent platform or orchestration product. |
| Team, Cloud & CI | Historical / Research | No hosted/team/cloud service is publicly available from this repository. |
| Analytics | Available local observations | Local counters are not universal savings or business-outcome proof. |
| Proof & audit | Available local primitives | Integrity evidence is not a standalone savings claim. |
| Adaptive learning | Research | LeanCTX does not offer AutoTune or autonomous promotion. |
| Hermes context engine | Preview reference integration | Not a general agent framework or stable Embed contract. |
- MCP tools
- Configuration keys
- CLI command map
- SDK surface — what each published artifact is
Generated inventories enumerate implementation surfaces; they do not promote a surface to a stable public API. Check the status map before depending on one.