aindex cache "refactor auth callbacks" --json
Context · For: agent
Reduced tokens are only half the cost story; unstable prompt order kills cache reuse.
AiIndexer classifies repo facts, architecture, symbols, task files and tool output so agents send stable context in a deterministic order.
$ aindex cache "refactor auth callbacks" --json
stable_tokens
volatile_tokens
cache_hit_estimate
cache_plan
stable_prefix
volatile_suffix
content_hashCommand
Cache-Aware Context
Order context so prompt caching can actually hit.
context action=cache
stable_tokensvolatile_tokenscache_hit_estimatecache_planstable_prefixvolatile_suffixcontent_hash
What the Brain does automatically
The Brain fires this workflow for you.
The buyer sees that AiIndexer reduces tokens and protects prompt-cache hit rate at the same time.
refactor
When a task is classified as a refactor.
public/assets/benchmarks.jsonRequired tier
Where this becomes commercially available.
Orders stable repo facts first so prompt caching actually hits across agent turns.
Foundation
Visible as a product workflow and pilot proof target; do not treat as fully shipped enterprise automation yet.
Foundation
Names the parity workflow and proof path without claiming full Sourcegraph-class depth.
- CLI cache
- Autopilot pack
- ROI dashboard
- Benchmarks
- Pilot report
This workflow stays discoverable across setup, CLI, MCP status, docs, dashboard and pricing — never a hidden command.
Feature visibility checklist
Buyer-visible names covered by Cache-Aware Context.
This keeps grouped product names discoverable without claiming a separate maturity level from the underlying workflow.
Cache-Aware ContextFoundation
Cache-Aware Context
Stable and volatile context are separated so cache behavior is visible.
- Surface
- Autopilot, benchmarks, ROI dashboard, pilot report
- Buyer-safe status
- Foundation · Foundation
- Runtime
- preview only
Context
Make the reusable part of context stay reusable.
Stable tokens visible