SuperCompress Proxy — One Command, Every Coding Agent

If you use a coding agent like Cursor or Windsurf every day, you've probably noticed two things:

1. Your token usage is massive — every file context, conversation history, and tool output gets sent to the LLM as prompt tokens
2. Your bill grows with it — at GPT-4 Turbo pricing ($10/1M input tokens), a heavy Cursor user spends $50–200+/month on prompt tokens alone

We built SuperCompress to solve this: it compresses prompt context before it reaches the LLM — query-aware extractive selection that keeps original lines and drops junk. Measure original_tokens / kept_tokens on your traffic. The problem was always integration — adding middleware, configuring agents, setting up proxies. Too many steps.

Not anymore.

One Command

That's it. npm install alone does not rewrite agent configs. setup links your SuperCompress account, then:

1. Detects coding agents installed on your machine
2. Installs the compress_context MCP plugin for supported agents
3. Optionally opts into a localhost OpenAI/Anthropic base-URL proxy if you pass --proxy

From this moment forward, hooks compress every submit with context (tiny asks skip), and agents can still call compress_context on dumps. Provider-managed subscription sessions stay on MCP — no API-key mode required.

Works With Compatible Agents

When a new agent exposes a configurable OpenAI- or Anthropic-compatible endpoint, run supercompress setup again to detect it and follow its manual configuration steps.

How It Works

The proxy runs on your machine at localhost:8080. Your coding agents are configured to send their LLM requests there instead of directly to OpenAI/Anthropic. The proxy:

1. Receives the messages from your coding agent
2. Compresses the context using the SuperCompress API (billable through your plan)
3. Forwards the compressed messages to the real provider (OpenAI/Anthropic)
4. Returns the response back to your coding agent

Your provider API key stays on your machine. Only the context text is sent to the SuperCompress API for compression. Compression is a preprocess before the provider call — measure wall time on your path.

The Cost Math

Metric	Without SuperCompress	With SuperCompress
What you send	Raw dumps, history, tool output	Query-relevant original lines
How you measure	—	original_tokens / kept_tokens
Context window fit	Fat dumps fill the window fast	More room for the next turn

What About SuperCompress Pricing?

Every compression call goes through the SuperCompress API. Free accounts get 5M tokens/month; enable pay-as-you-go for more:

Tier	Price	Tokens	With a Coding Agent
Free	$0	5M / month included	Light daily use for most solo agents
Pay as you go	$0.10 / 1M tokens	Prepaid usage after the free allowance	Heavy Cursor / Claude Code days

Measure the cut on your traffic. Do not treat any single percentage as a product-wide API-cost guarantee. Over the free 5M, SuperCompress overage is $0.10 per million tokens compressed. Published suites live on /benchmarks.

For Teams

Run the proxy as a shared Docker container for your whole team:

docker run -p 8080:8080 \
  -e SUPERCOMPRESS_API_KEY=sc_live_team_key \
  -e PROXY_PORT=8080 \
  supercompress/proxy

Every developer on the team configures their agent to point at the shared proxy. Usage is centralized under one API key with pay-as-you-go enabled. The dashboard shows per-developer usage.

What Developers Are Saying

"I was spending $180/month on Cursor. After installing the SuperCompress proxy, it dropped to ~$60/month. The setup took 30 seconds and I haven't touched it since."

"The auto-detection found all three of my agents (Cursor, Continue, Claude Code) and configured them all at once. This is how every developer tool should work."

Get Started

You'll need a SuperCompress account. If you don't have one, setup opens supercompress.dev/dashboard to sign in and link this install.

For complete documentation, see the coding agents guide. Source: GitHub.