Summary

• Frontend: Replace async params.then() + useState with synchronous React.use(params) so route params are available from the first render, eliminating a race condition where the AG-UI EventSource connection was deferred and historical chat events were missed on re-navigation
• Backend: Fix between-run listener URL to include the session name as thread_id — was calling GET /events (404) instead of GET /events/{sessionName}

Root Cause

Chat history not rendering (frontend)

The session detail page extracted projectName and sessionName from the async params Promise via useEffect(() => { params.then(...) }), initializing both as empty strings. This meant the EventSource connection was deferred to a second render cycle. On fast re-navigation, the timing gap could cause the SSE replay of historical events to be missed.

Between-run listener 404s (backend)

The listenBetweenRunEvents function constructed the runner events URL as GET /events without appending the thread_id path parameter. The runner endpoint requires GET /events/{thread_id}, returning 404 on every attempt. This prevented capture of events emitted between user-initiated runs (e.g., background task completions).

Test plan

• Navigate to a session with existing messages, verify chat history loads
• Navigate away from the session, then back — verify chat history persists
• Repeat with rapid back-and-forth navigation
• Verify new messages can still be sent and received after re-navigation
• Check runner pod logs — no more GET /events 404 entries
• cd components/frontend && npm run build passes with 0 errors
• cd components/backend && go vet ./... passes

🤖 Generated with Claude Code