kite 0d530f3b73 fix(viewer): use real API token usage in session page instead of tiktoken estimates ...

The session page was showing significantly lower token counts than the console
summary because it used local tiktoken estimation while the console used actual
API-reported usage data. Now SetResponse prefers resp.Usage when available
(falling back to tiktoken), persists cache token fields to JSONL, and the
viewer displays cache read/write stats alongside prompt/completion totals.

2026-06-06 21:17:47 +08:00

..

static

feat(agent): integrate session recording and token tracking for re-location task

2026-05-30 23:25:12 +08:00

templates

fix(viewer): use real API token usage in session page instead of tiktoken estimates

2026-06-06 21:17:47 +08:00

handler.go

feat: init

2026-05-20 22:03:52 +08:00

hostguard_test.go

style: apply go fmt formatting

2026-06-03 17:34:28 +08:00

hostguard.go

fix(viewer): add Host-header allowlist to block DNS rebinding (#10)

2026-06-03 17:21:27 +08:00

server.go

fix(viewer): add Host-header allowlist to block DNS rebinding (#10)

2026-06-03 17:21:27 +08:00

store.go

fix(viewer): use real API token usage in session page instead of tiktoken estimates

2026-06-06 21:17:47 +08:00