Roles, messages & claims
The agent bus records coordination messages and scoped work claims. It is distinct from the execution scheduler and does not grant access to a source.
Explore this capabilityAgent Coordination
A local substratefor agent workflows.
LeanCTX is the Context Gateway for AI systems. LeanCTX provides a local context substrate for supported agent workflows. Six Agent Tools language contracts expose task and handoff primitives; Python handoff operations remain in the Preview namespace. Broader multi-agent orchestration is a Research capability, not a universal hosted agent platform.
The approach
Scoped coordination. No borrowed authority.
The host launches and owns each agent. The local substrate can coordinate recorded tasks, messages and claims; a handoff receipt does not prove successful work, and a claim does not grant source access.
Host-owned lifecycle
Your host starts and supervises each agent.
LeanCTX is a local coordination substrate, not a service that launches or supervises a universal agent team. The host chooses the agents, task scope and source permissions.
- Host authority
- The application owns the agent lifecycle and model calls.
- Local substrate
- LeanCTX coordinates only supported task state and messages.
- Source access
- A coordination claim does not grant permission to read a source.
Review a code change
Prepared context · configured policy
Policy before execution
Permitted destination + applicable budget
An admitted route.
The candidate satisfies the example’s route policy and execution limit. The supported call can proceed.
Use the permitted primary route
A permitted alternative.
The primary route is unavailable. The replacement is checked against the same rules before execution.
Use the admitted fallback
A visible stop.
No candidate satisfies the policy or available budget. The example stops instead of choosing a forbidden destination.
Withhold execution
Example states, not a live request or provider benchmark. Controls apply to supported routed calls.
Python SDK Preview
Keep preview operations in preview.
Python SDK task and handoff operations are exposed under leanctx_sdk.preview. Treat their availability and interface as Preview, and confirm the current package contract before relying on them. A handoff receipt confirms transfer, not successful completion.
- Preview namespace
- Use the explicit leanctx_sdk.preview namespace for Preview operations.
- Bounded task
- Pass a defined task and source references without inventing permissions.
- Outcome check
- The host verifies completion separately from handoff receipt.
Research orchestration
Broader orchestration remains research.
The six Agent Tools language contracts and local task substrate do not make a general-purpose agent orchestration product. Broader multi-agent orchestration remains a Research capability; do not plan on it as a released universal platform.
- Supported contracts
- Check the operation list for each language contract.
- Research boundary
- Research capabilities are not release commitments.
- Integration owner
- Your application remains responsible for orchestration and recovery.
Evidence & outcomes
Inspect what happened. Verify what finished.
Review the task state, messages and available usage evidence that the integration records. Check task completion and quality separately; a coordination event alone does not prove the intended work succeeded.
- Recorded state
- Use the state visible through the active integration.
- Separate checks
- Validate the work product and its sources independently.
- Host decision
- The host decides whether to accept, retry or stop.
In your workflow
Bound the work. Keep ownership clear.
Execution can involve more than one agent. Coordination, delegation and transport serve different jobs; none may expand the task’s authority.
Bounded delegation
Represent dependencies, leases, budgets and cancellation in the work graph. Delegated work inherits its applicable limits instead of gaining open-ended authority.
Explore this capabilityDelivery versus acceptance
Transporting a task or result is not proof of accepted execution. Keep failed delivery, cancellation and verified task outcome distinguishable.
Explore this capabilityReference and optional optimization
A deterministic reference remains usable. Optional learned proposals can inform selection, while the host retains policy and budget authority.
Explore this capabilityQuestions & answers
Execution and routing questions.
Does LeanCTX launch and own agents?
No. Your host starts and supervises agents and owns their model calls. LeanCTX provides a local substrate for supported task coordination.
Are Python handoffs a stable production API?
No. These operations remain under leanctx_sdk.preview. Review the current SDK contract and obtain a separate signed written agreement for production embedding or OEM distribution.
Is broad multi-agent orchestration available?
No. Broader orchestration remains a Research capability, and there is no released universal agent platform. Your application owns orchestration, permissions and recovery.
Start with LeanCTX
Start with a supported task.
Check the language contract, use Preview operations only within their stated scope, and let your host verify completion.
Local-first. Model-agnostic. Your context.