LeanCTX
EN
Start for Free

Context Gateway for AI Systems

One task.
A controlled path.

LeanCTX sits between AI and the systems it reads. It selects relevant context, applies supported controls, and records what the integration can observe.

Get LeanCTXExplore context selection
Select01
Control02
Prove03

The chapters below follow these three steps and the capabilities behind each. Access and policy checks apply throughout the supported flow.

Select

Find what the task needs. At the right depth.

LeanCTX turns a task into a focused search across the sources your workflow may access, then reads each match at the depth the question needs. Source references stay attached, so you can read deeper or inspect the evidence behind a match.

Available sourcesTask + read depthFocused context

A coding workflowFor a code review: locate the checkout implementation and its tests, then read only the functions the change touches.

  1. 01

    Decide

    Define the task.

    Set the question, available sources and context budget. Give the next read a clear purpose.

    Task & budget
  2. 02

    Retrieve

    Find relevant sources.

    Search the sources available to your workflow. Relevant matches become candidates for the next context.

    Search & relationships
  3. 03

    Extract

    Read the relevant detail.

    Open the file structure, function or passage behind a match. Choose the read depth your question needs.

    Read modes & detail
  4. 04

    Compress

    Reduce the noise.

    Remove unnecessary detail from the prepared view. Use source references to read deeper when the task requires it.

    Progressive context

Control

Your rules first. Then the model.

Your boundaries and enabled filters check supported operations before anything is delivered. Source access and content inspection answer different questions: may this source be read, and may this result be delivered? When execution runs through LeanCTX, the selected route must also pass the applicable policy and budget checks.

Prepared contextRules + budgetsControlled delivery

A coding workflowRestrict customer-data directories and inspect supported text results with enabled filters. Send the request through a permitted model route; any fallback must meet the same constraints.

  1. 05

    Govern

    Apply your rules.

    Access boundaries and enabled filters check supported operations before delivery. These controls accompany the lifecycle rather than running only at this step.

    Security & governance
  2. 06

    Run

    Execute through an allowed route.

    Use prepared context in your own model call, or route supported execution through LeanCTX. In the governed path, the selected route must pass the applicable policy and budget checks.

    Execution & routing

Prove

Show what was delivered. And why.

LeanCTX records what the integration can observe: the context it delivered, the configured checks that affected delivery and the usage behind it. Evaluate the task itself separately: a completed model call is evidence of execution; task checks establish whether the work succeeded.

Context receiptUsage + outcomeEvidence to inspect

A coding workflowReview the proposed change and run its tests. Before you accept it, check which context the agent received and which filters applied.

  1. 07

    Evaluate

    Measure what changed.

    Inspect delivered context, observed usage and the basis of any cost estimate. Evaluate the task outcome separately, including the cost of failed attempts and retries.

    Measurement & evaluation
  2. 08

    Replay

    Revisit the context decision.

    Use the source and recorded state still available to investigate a result. Context replay does not guarantee an identical model answer.

    Trace & revisit

Next task

Keep what helps. Pass on what matters.

Record what is worth reusing and pass work on with its source references, so the next session, person or agent picks up from what is already known.

  1. 09

    Remember

    Save useful findings.

    Record decisions, findings and working state. Retrieve what the next session needs to continue.

    Memory & continuity
  2. 10

    Hand off

    Prepare the handoff.

    Pass a task, selected findings and source references to the next person or agent. The Python SDK exposes local handoffs in Preview; broader agent orchestration remains Research. The host owns agent launch, lifecycle and permissions.

    Supported handoffs

Integrations

Keep your tools. Control their context.

Add the Context Gateway to the workflow you already use. Connect through supported clients, MCP, hooks or the SDK, and check which reads and results the integration covers.

Choose the connection you need.
LayerExamplesRole
AI toolsCursor · Claude Code · Codex · CopilotHost-specific setup for supported tool calls.
Data sourcesFiles · GitHub · GitLab · Jira · MCPLocal reads or configured providers with their own credentials and permissions.
Models & frameworksYour host + LeanCTX SDKPrepared tool results for your model. The host owns the model call.

Check host setup, adapter versions, source permissions and filter coverage together. These layers do not promise identical capabilities.

Your first workflow

Start with one real task.

Connect your tool, prepare context from a familiar project and compare the result with its source. Add execution controls and continuity as your workflow needs them.

Follow the setup guide

Start with LeanCTX

Make your next task a better-informed one.

Bring your tools. Keep your model. Put deliberate context between them.

Get LeanCTXExplore the SDK

Local-first. Model-agnostic. Your context.