Skip to content
Documentation

Integrate

Reduce supported request payloads locally.

The optional proxy operates on traffic routed through it, separately from file reads and MCP tools.

AvailableReviewed September 2026

What the proxy changes

Read-side tools shape retrieved material before it enters the host’s context. The request proxy can transform supported outbound model-request payloads on a configured route.

It cannot inspect or optimize traffic that bypasses it. Protocol support and client authentication determine whether a particular host can use it.

Inspect before enabling

lean-ctx proxy status

Use your installed CLI’s proxy help to inspect start/enable behavior and supported clients. Enabling can change host endpoints and autostart configuration, so review those changes deliberately.

A local proxy and an organizational team gateway are different scopes. This page documents the local integration; a hosted team service is not included.

Login autostart is platform-specific: the reviewed runtime uses a LaunchAgent on macOS and a systemd user service on Linux. It has no equivalent native Windows login-service installer. Do not treat a Windows installation as an automatically running proxy service. The CLI and MCP quickstart work independently of this optional proxy; see platform differences.

Protect cache economics

Changing a request can affect provider prompt caching. The runtime contains cache-aware controls and measurement settings, but an actual billing outcome depends on the provider, request shape, cache hits and workload.

Use proxy configuration to inspect exact fields and defaults. Do not enable experimental transformations merely because the settings exist.

Measure covered traffic

lean-ctx spend --json

Provider usage can only be reported where it is captured. Distinguish provider-reported values from estimates and representation counts. Include retries and compare equivalent tasks.

Integrate applications through the right contract

Use the published SDK for application and agent-tool integration. Old examples using a differently named SDK package or a one-line compress helper are not the current SDK v1 contract.

For local HTTP discovery and MCP tool calls, use the HTTP reference.

Sources & versions4 references Reviewed
Core checkout
0ce2207ee4
Installed 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