Observe
See context, token, and workflow signals entering a compatible agent or application path.
CutCtx is a pre-release, local-first tool for compressing selected tool outputs, logs, RAG chunks, and files through compatible proxy and MCP paths. An agent can retrieve retained originals when the required retrieval integration is enabled; model routing is optional and separate.
Private beta · Access by request · Host and auth support vary
Provider adapters and host paths are catalogued; live acceptance varies by client and auth mode
Host support depends on the client, authentication mode, provider, and configuration. See the integration limits before relying on a listed path.
Wrappers and managed routes exist for selected hosts. Whether a request passes through CutCtx depends on the client, authentication mode, provider, and route configuration. A configured URL or healthy proxy alone does not prove that a request was processed.
On a compatible configured path, CutCtx can inspect requests, reduce selected context, and expose local telemetry. Retrieval and routing require their own enabled integrations and remain subject to host-specific limits.
See context, token, and workflow signals entering a compatible agent or application path.
Classify protocol and request context before an optimization decision is made.
Reduce selected context; retrieve retained originals only when the required integration is enabled.
Use opt-in routing only for clearly eligible work; retain the requested model when safety gates do not pass.
Send the focused request through the provider and compatible endpoint your team selected.
Review local token estimates separately from provider usage, cache, routing, and retrieval costs.
Add policy, identity, audit, retention, tenancy, and entitlement controls only when the deployment needs them.
Start with a local evaluation. Add coordination and governance only when the workflow and organization call for them.
Observe, compress, recover, proxy, and measure close to the workflow.
Use opt-in routing only when complexity, capability, provider, account, and transport conditions are eligible.
Review savings, latency, budgets, routing, health, and diagnostics with evidence from your workload.
Source includes SDKs, compatible proxy routes, CLI wrappers, MCP, plugins, and IDE setup paths; publication and live acceptance vary.
See integrationsIdentity, policy, audit, retention, tenancy, and entitlement controls have separate availability and acceptance gates.
CutCtx is designed for a low-friction technical evaluation. Use a workflow you already trust, then inspect what changed.
Add CutCtx locally without replacing your agent or provider.
Route a supported coding agent or compatible application through the proxy.
Use the workflow normally so the evaluation reflects real traffic.
Review local token estimates and routing evidence before drawing conclusions about total cost or task quality.
Local token reductions are not provider billing counters. Separate compression from provider input/output, cache reads and writes, and routing; include retries, retrieval calls, and task outcomes when evaluating a full workload.
Core transformations can run in an environment you control, while model requests continue to the configured provider. Optional telemetry egress, licensing, and account flows have separate destinations and settings.
The core compression workflow does not require hosted prompt analytics; review optional external service paths separately.
Keep OpenAI, Anthropic, Gemini/Vertex, Bedrock, or the compatible endpoint selected by your team.
Add shared reporting, policy, identity, audit, retention, and deployment support when the organization needs them.
Plan descriptions are indicative; confirm current terms and beta availability with the team.
Core compression, proxy, CLI wrapping, SDKs, MCP, local dashboard, and Docker.
Shared analytics, savings reports, policy presets, budget controls, and support.
Identity-aware administration, RBAC, audit export, retention controls, fleet APIs, and deployment support.
Install locally, wrap an agent, and inspect the result on your own traffic.
Use these worksheets to plan and evaluate context budgets, caching, proxy paths, and quality checks.