WINDOW / %Context pressure
Watch the active context window grow and see genuine compaction resets.
GUIDE Claude Code observability
See what Claude Code
is doing to your context.
Aether turns Claude Code's local session trail into a live operational view. Find expensive turns, compaction resets, tool-heavy work, and nested agents without adding an SDK or uploading prompts.
01 The operational gap
Claude Code is productive. Its resource use is easy to miss.
A long coding session can accumulate context, repeat cached input, launch agents, compact history, and touch many files. Aether keeps those events on one timeline so a slow or expensive turn has an explanation, not just a number.
02 What becomes visible
Useful signals.
One shared timeline.
TOKENS / USDToken economics
Separate input, output, cache reads, and reasoning emitted by Claude Code.
PARENT / CHILDAgent hierarchy
Keep sub-agents attached to the parent turn, with their tools and code impact.
INPUT / SPLITWork attribution
Estimate which inputs consumed each request: context, tools, agents, memory, hooks, and runtime.
03 Local pipeline
Native trails in.
Operational clarity out.
Discover
Aether detects existing Claude Code session files automatically.
Normalize
Provider-native events become turns, usage, actions, agents, and compactions.
Observe
The terminal UI updates as Claude Code writes new events.
04 Practical questions
Know what Aether
does and does not do.
Does Aether require a Claude API key?
No. Aether reads Claude Code's existing local session data and never calls another model.
Does it upload Claude Code prompts or responses?
No. Parsing and rendering happen locally, and Aether does not modify provider transcripts.
Can it show Claude Code sub-agents?
Yes. Agent work is nested under the parent session rather than appearing as unrelated top-level chats.
05 Start observing
Three commands.
No instrumentation.
AETHER SETUPLOCAL SHELL
$
brew trust --formula connectchiragg/tap/aether$
brew install connectchiragg/tap/aether$
aether watch