Latenode

Cursor cuts agent token costs 7% with prompt and cache changes

Agent teams can lower per-run spend by auditing harness overhead, not just switching models. Persistent prompts and rarely used tool definitions are direct cost targets.

Cursor cuts agent token costs 7% with prompt and cache changes

Cursor changed its agent harness to reduce user token costs by 7% without lowering agent quality, the company says.

Cursor’s breakdown attributes the savings to a system prompt trimmed by roughly 66%, dynamic tool loading that cut static-context description tokens by 60%, and cache changes that reduced cold misses by 20%. It also reports a 1.6% drop in cache-read tokens after numbering only every tenth line. These measurements are vendor-reported and have not been broadly validated.

Instead of packing every tool definition into persistent context, Cursor now keeps high-frequency tools loaded and fetches the rest on demand. It also separates stable setup from variable input through a “phantom user message,” preserving more reusable context.

For agent builders, the pattern is practical: prune persistent instructions, lazy-load rarely used tools, and isolate changing context before tuning the model itself.

When models and APIs shift keep the workflow running

Connect the models and apps from stories like this in one scenario. If a vendor changes routing, pricing, or availability, you update the workflow — you don't start over.

Start Free

Free forever plan. No credit card required.