LeanCTX SDK
Embed LeanCTX context control into your application.
LeanCTX is the Context Gateway for AI Systems. Control what your AI can see. The SDK lets an application select task-relevant context, apply the controls supported by its integration, and inspect the resulting output and evidence. Your application keeps its model, workflow, and user interface.
SELECT → CONTROL → PROVE
- Select: gather relevant context with supported search, read, tree, compose, and lifecycle APIs.
- Control: apply the permissions and command policy available in the chosen integration and Engine release.
- Prove: inspect returned results and measurements; the stable lifecycle also exposes receipts. A context-only integration cannot observe what the host later sends to its model.
Choose your path
- Coding agent: use Stable
AgentContextorAsyncAgentContextfor local context tools with explicit permissions; your host keeps the model and agent loop. - Enterprise copilot: use only the five Stable lifecycle primitives:
ContextSession,ContextSource,ContextView,ContextPlan, andContextReceipt. - Product builder: embed the SDK and Engine in your application. The source license permits non-production use; production use, OEM embedding, and commercial redistribution require a written agreement signed by Thinkery AG.
Build with the SDK when your application needs its own LeanCTX integration. Use the Engine's CLI or MCP integration directly when an existing supported agent already provides the context tools you need.
The SDK does not contain a second implementation of the Engine. It starts one verified local Engine process and exposes its negotiated capabilities as stable language-native methods.
your model / agent loop
↓
AgentContext or AsyncAgentContext
↓ versioned local Agent Tools Interface
LeanCTX Engine (release-specific; see [Compatibility](COMPATIBILITY.md))
↓
project-jailed files, cache, search, patches, approved commands
Install
This SDK 1.1.1 maintenance release preserves Engine 3.10.1 compatibility and its exact companion-wheel dependencies. Install the Python SDK and Engine together: Standard Engine:
python -m pip install "thinkery-leanctx-sdk[agent]==1.1.1"
With the certified OpenAI Agents integration:
python -m pip install "thinkery-leanctx-sdk[agent,openai-agents]==1.1.1"
CUDA and Windows-GNU builds use the documented agent-cuda and
agent-windows-gnu extras. The core SDK remains pure Python.
Language SDKs
All six language SDKs implement the five Stable lifecycle primitives and the separate Stable Agent Tools surface. The table describes this maintenance release, which requires Engine 3.10.1. Registry publication is per artifact; verify the version at the registry before installation.
| Runtime | Package source | Package identity |
|---|---|---|
| Python 3.9–3.14 | repository root | thinkery-leanctx-sdk |
| Node.js 22+ / TypeScript | packages/typescript |
@thinkery/leanctx-sdk |
| Go 1.24+ | packages/go |
github.com/Thinkery-AG/leanctx-sdk/packages/go |
| Rust 1.76+ | packages/rust |
thinkery-leanctx-sdk |
| Java 21 / Kotlin 2.1 | packages/jvm |
com.leanctx:leanctx-sdk |
| .NET 8+ | packages/dotnet |
Thinkery.LeanCtx |
Each package follows the shared protocol and release gate. The Engine remains a
separate local binary. Python's Preview workspace APIs live only under
leanctx_sdk.preview; they are outside the Stable v1 guarantee.
Registry releases use language-scoped tags from the same commit:
packages/typescript/vX.Y.Z, packages/go/vX.Y.Z,
packages/rust/vX.Y.Z, packages/jvm/vX.Y.Z, and
packages/dotnet/vX.Y.Z. See
docs/LANGUAGE-PACKAGES.md.
Go follows the standard monorepo module convention and is tagged
packages/go/vX.Y.Z. Registry-backed packages use their native registries:
PyPI, npm, crates.io, Maven Central, and NuGet.
Custom agent example
from leanctx_sdk import AgentContext
def my_model(task: str, context: str) -> str:
# Replace with any model or framework call.
return f"{task}\n\nRelevant project context:\n{context}"
with AgentContext(".", task="Explain the public API") as ctx:
files = ctx.tree(depth=2)
matches = ctx.search("class AgentContext", path="src")
source = ctx.read("src/leanctx_sdk/agent.py", mode="signatures")
answer = my_model(ctx.task, "\n".join((files.text, matches.text, source.text)))
print(answer)
print(f"saved tokens: {ctx.metrics.saved_tokens}")
Default permissions are read-only. A coding agent must opt in explicitly:
from leanctx_sdk import AgentContext, AgentPermissions, ExecutionPolicy
with AgentContext(
".",
permissions=AgentPermissions(write=True, execute=True),
execution_policy=ExecutionPolicy(allowed_executables=("git", "pytest")),
) as ctx:
ctx.replace_unique("app.py", "old_name", "new_name")
tests = ctx.run(("pytest", "-q"), timeout=30)
The permission policy is immutable for the session and is enforced again by
the Engine. call() cannot bypass it, and process tools must use run(argv).
SDK 1.1 Stable Agent Tools
read,search,glob,tree,compose, andsymbol- safe
create_file,patch, andreplace_unique - allowlisted argv execution with compressed output
- persistent per-agent cache and aggregate token measurements
- synchronous and asynchronous APIs
- capability negotiation and typed fail-closed errors
- optional OpenAI Agents 0.8.4 function tools
The SDK supplies the tool substrate, not an autonomous planner, model, hosted service, or universal quality guarantee. Savings are measured per call against the Engine's raw-output baseline; they are not a promise for every workload.
Compatibility
The five SDK 1.0 lifecycle primitives remain available unchanged:
ContextSession, ContextSource, ContextView, ContextPlan, and
ContextReceipt. Stable Agent Tools is a separate API surface. SDK 1.1.1
preserves SDK 1.1.0's exact Agent Tools Engine 3.10.1 requirement. The older
context-view/recover Engine Interface v1 remains separate.
See:
License
The SDK is source-available under a license that permits non-production use. Production use, OEM embedding, and commercial redistribution require a separate written agreement signed by Thinkery AG. LeanCTX Engine is licensed separately under Apache-2.0; that license does not grant SDK production or OEM rights.
Metadata
Release files for thinkery-leanctx-sdk 1.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| thinkery_leanctx_sdk-1.1.1-py3-none-any.whl | Python 3 | none | any | Details for thinkery_leanctx_sdk-1.1.1-py3-none-any.whl |
Release files / thinkery_leanctx_sdk-1.1.1-py3-none-any.whl
| Download URL | thinkery_leanctx_sdk-1.1.1-py3-none-any.whl |
|---|---|
| Size | 94.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
23cfa48772ad509404ad41a5cebbfa3610321b877cdc8a26ddb2f381cdeae172
|
|
BLAKE2b-256 checksum How to use checksums |
a2f1ffeecfa47907b617a6e8dc3e88038514e3093a41a9396aa9cfb3209fad5f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 3, 2026.
Transparency logSecurity for thinkery-leanctx-sdk 1.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
1 file in this release has been uploaded with provenance metadata.
Attestation for thinkery_leanctx_sdk-1.1.1-py3-none-any.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 3, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.