Skip to content

v0.2.6 — Fix session detail 404 on JSONL-only machines

Choose a tag to compare

View all tags
@Arindam200 Arindam200 released this 03 Apr 11:11
v0.2.6
5147e7d

Bug Fix

/api/sessions/[id] was returning 404 for sessions that exist only as JSONL files (the primary data source on most machines). It was only looking in ~/.claude/usage-data/session-meta/ which is a legacy/secondary path.

The route now falls back to getSessions() (JSONL-derived) when readSessionMeta() returns null, so the session detail and replay pages work for all team members.

Endpoint test results (v0.2.6)

All 11 GET endpoints return 200 with correct shapes:
/api/stats /api/sessions /api/projects /api/activity /api/costs /api/tools /api/history /api/plans /api/todos /api/settings /api/memory

Dynamic routes: /api/sessions/[id] ✓ /api/sessions/[id]/replay ✓ /api/projects/[slug] ✓

POST: /api/export ✓ 404 on bad IDs ✓

Assets 2
Loading