Call manifests and layered observability

The idea

Each metered call records its role, model, layers, files, tokens, cache reads and stage budget, plus a digest of its input taken before the call. A task can be read at any level, from a glance down to these internals.

The problem
Nobody could trace context bloat or what was sent to a model.
Why it matters
Anyone can see what each call loaded and what it cost, at the depth they need.
Where it stands
In production as of

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

  • Run waste analysis

    When a run ends, the platform analyses its steps and requests for repeats, missed fusions, context growth, large outputs and long logs. It estimates the tokens each mechanism would save.

  • Worker insights and verified work per token

    Reports built from the call records show how each worker spends time, tokens, context, models and tools. The Performance tab shows verified results beside the tokens they took.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.