Read & shape context

Plan the context before you load it.

Start with a task and budget, then inspect which sources and representations are selected.

AvailableReviewed September 2026

Give the task a boundary

A useful task says what you need to decide: “find the validation path for login requests” is more actionable than “understand the repository.” Pair it with a context budget.

{"name":"ctx_plan","arguments":{"task":"Find the validation path for login requests","budget":4000,"profile":"balanced"}}

The available plan profiles are ultra_lean, balanced and forensic. Choose the tradeoff deliberately; a larger budget does not establish that the right evidence was selected.

Inspect before materializing

Read the plan’s candidates and chosen detail. Check whether the relevant sources were indexed and whether important dependencies are missing. Selection and ranking are based on available context; LeanCTX does not automatically query every connected provider for every task.

ctx_compile materializes context within its configured budget and mode. ctx_fill operates on a supplied path set and budget. Their schemas are separate from the planning schema.

Control the next operation

Use context controls when you need to pin a source, exclude irrelevant material or change a view. Those controls shape LeanCTX operations; they cannot remove text the host has already sent to a model.

Verify the result

Read the actual delivered content. If a plan omits a necessary implementation, request that source explicitly. Budget adherence and task success are different checks.

Planning context is also different from an agent’s work plan. Your host still decides which code to change, which tests to run and when the task is complete.

Sources & versions3 references Reviewed 17 Sept 2026

Core checkout: 0ce2207ee4
Reviewed runtime: 3.10.2
SDK release: 1.1.0

Separate baselines for source, CLI/configuration and SDK contracts. Review does not certify every platform or integration.

Versions & compatibility