Context & usage

Token X-Ray

Investigate where context goes.

Investigate provider-reported token usage and recurring activity by task.

01
Inspect a breakdown in the actual Token X-Ray interface.Actual Linqbase interface · demonstration project
TURN IDEAS INTO POSSIBILITIES

Investigate where context goes.

During or after a task whose usage you want to understand.

A single token total does not show which parts of a conversation occupy most space. Token X-Ray breaks down the context that can be measured or estimated.

Inspect categories and large contributors, then decide what information remains useful. Keep estimates distinct from provider-reported usage.

YOUR NEXT STEP

How to get started.

From your first choice to the result. Here is how to use this feature in your own project.

  1. 01

    Choose the conversation and inspect available usage data.

  2. 02

    Explore the distribution across tasks and signals about repeated tool activity.

  3. 03

    Use findings to refine future requests, context or budgets.

IN PRACTICE

How it could work for you.

Find that a repeated tool result contributes more context than the actual instructions.

How to assess the result

Token estimates differ by tokenizer and route. They are not a substitute for the provider invoice.

GET STARTED IN LINQBASE

Where to find it.

Conversation → Tools → Token X-Ray

Available actions depend on your plan, mode and project state. Features that require a task become available within an appropriate conversation.
SAVE & CONTINUE

What is saved?

Reported measurements stay in the conversation and task history.

GOOD TO KNOW

What you need to know

Missing provider data is not counted as zero usage. Repetition signals are clues rather than automatic proof of a fault.