Adaptive Intelligence
Context-aware.
Gets smarter as it fills.
Pith watches your context window in real time and takes action before it causes problems — automatically ratcheting compression, flagging waste, and front-loading what future requests will need.
Auto-escalation
Always on
50% context fill→ LEAN mode activated
70% context fill→ ULTRA mode activated
85% context fill→ Dynamic ceiling injected
Ratchets up, never down mid-session. Prevents runaway responses from eating the remaining headroom. Toggle with /pith escalate on|off.
Before / After
68% fill — auto-escalated
Context fill136k / 200k
Response size (before)1,840 tok — growing
Mode injectedULTRA (auto)
Response size (after)510 tok -72%
Hindsight pruning Hindsight · 2026
60% trigger
Scan telemetryEvery tool call logged
Superseded readsFile read 2+ times → flag
Early-session blobsLarge old outputs → prune
Fires once per session when context passes 60%. Reports stale token cost. Recommends /compact with exact savings estimate.
Symbol extractor + Speculative Fetch
~95% reduction
Full file read1,800 tokens
/pith symbol auth.ts handleLogin38 tokens -98%
Speculative fetch+callee signatures auto-appended
Tree-sitter AST when available, regex fallback. Appends signatures of called functions defined in the same file — eliminates ~60% of follow-up lookups.
adaptive intelligence · live session
── turn 24 · context fill: 52% ──────────────────────
[PITH AUTO-ESCALATED: context 52% full → LEAN compression active.
Previous mode: off. Run /pith escalate off to disable.]
── turn 31 · context fill: 71% ──────────────────────
[PITH AUTO-ESCALATED: context 71% full → ULTRA compression active.]
── turn 33 · hindsight nudge (fires once at 60%+) ───
[PITH HINDSIGHT: 3 stale reads detected · 4,200 tokens recoverable
auth.ts read 3× (keep latest: turn 29) · 1,840 tok
npm install output (turn 2, now irrelevant) · 1,120 tok
→ Run /compact to recover ~4.2k tokens (21% of remaining headroom)]
$ /pith symbol src/auth.ts validateToken
[PITH SYMBOL: validateToken in auth.ts (lines 47–81, tree-sitter)]
47 async function validateToken(token: string): Promise<User | null> {
48 const decoded = jwt.verify(token, process.env.JWT_SECRET);
··· (35 lines extracted · 97% fewer tokens than reading auth.ts)
[PITH SPECULATIVE: called functions in same file → signToken (ln 31), hashPassword (ln 94)]
Cache-Lock Phase 9 · 2026
~300 tok/session
Session-start hashMD5 of rules block
Same settings as last session1 line emitted, not full block
Settings changedFull block, hash updated
Protects prompt cache. Dynamic values (token counts, timestamps) are excluded from the hash so cache hits are genuine stability signals.
Session Report /pith report
HTML dashboard
Token flow barsBaseline → removed → sent
Savings donutPer-bucket breakdown
Cost tableActual vs without Pith
Standalone Chart.js dashboard written to ~/.pith/report.html. Opens in browser. Run any time — refreshes to current session data.
$ /pith status
Live output
