Reduce chat-history tokens while keeping the facts the next turn needs

Classify old turns

Mark a turn as active requirement, durable fact, completed work, obsolete attempt or raw evidence. Active requirements and durable facts should remain explicit. Completed work can often become a concise state summary.

Summarize with structure

A useful summary states the goal, current state, decisions, unresolved problems, exact identifiers and next action. Avoid vague phrases such as “continue as before” because the model may no longer have the earlier context.

Use a quality gate

Varion keeps its proprietary engine implementation private. Commercial evaluation is based on measurable workload-specific outcomes, clear validation boundaries and customer-specific testing rather than disclosure of internal mechanisms. Use the dedicated Token Optimisation product area to evaluate whether the commercial result is suitable for your traffic; no universal performance percentage is promised.

Measurement checklist

1. Choose a representative completed task, not an artificial one-line prompt.
2. Record the selected model, provider input, cached input, output, retries and final result.
3. Change one optimization mechanism at a time so the cause remains visible.
4. Verify required identifiers, tool calls, code changes or business fields.
5. Keep passthrough available when the reduced request does not pass.

Varion commercial evaluation

Varion keeps proprietary product implementation details private. Evaluate Token Optimisation on representative traffic and judge it by the measured commercial result. New verified users receive 100,000 processed input tokens and 50 local test runs.