Technical evaluation

Install. Wrap. Run. Inspect.

This pre-release guide is for people who have received a CutCtx source checkout. Public PyPI and npm packages are not available; request beta access before installing.

Private beta · Python 3.10+ · Rust toolchain required

Access by request

Request beta access from PitchToShip. Source commands below apply only to a checkout supplied for the beta.

Step 01

Install CutCtx

From the root of your supplied source checkout, build the local Python package. This requires Python 3.10 or newer and a Rust toolchain; optional extras may be needed for specific integrations.

pip install .
Step 02

Initialize your local setup

Use the setup flow to detect local agents, configure available MCP integrations and auth, and start and verify the proxy. Host support depends on the confirmed beta path.

cutctx setup
Step 03

Wrap a supported agent

As an optional manual launch path, cutctx wrap claude starts the local proxy and launches the Claude Code CLI. Claude Code and Codex have documented live checks for specific configurations; other hosts include experimental paths. Confirm the host and auth mode included in your beta.

cutctx wrap claude
Use a normal workflow

Run the work you would ordinarily send through the selected agent. A representative evaluation is more useful than a synthetic one-off prompt.

Step 04

Inspect your own result

After using a configured workflow, inspect CutCtx local token estimates and request evidence. These are not provider bills: compare provider input/output, cache reads/writes, routing, retrieval calls, retries, and task outcomes separately.

cutctx savings --no-browser
Step 05

Inspect routing before changing it

When the optional Safe Savings status surface is enabled, inspect the active routing state and the latest privacy-safe decision without changing provider, account, transport, or model configuration.

cutctx routing status --proxy-url http://127.0.0.1:8787
Routing remains deliberate

Read status to understand the active preset and a recent decision. Enabling or changing routing stays on its normal explicit configuration path.

Optional macOS path

Global routing is host-specific

Managed macOS routing is a separate opt-in path for compatible desktop and CLI harnesses; it is not enabled by this quick start and does not cover every client or auth mode. If a managed route is already installed, cutctx global status and cutctx global doctor inspect its state and reported coverage. Confirm the exact host and auth path with the beta team before changing global settings.

Paid plans

Activate a paid license

Billing and license delivery are separate from this pre-release quick start. Activate only with a key supplied for your beta account:

cutctx license activate <license-key>

The CutCtx license portal is for license recovery; invoice and subscription management availability must be confirmed with PitchToShip.

Practical resources

Guides for planning and evaluation

Review context budgeting, provider caching, proxy evaluation, and quality-aware benchmarking.

Browse all CutCtx guides