fix(session): handle Qoder requires_action idle state and SSE reconnection

[heimanba]

Problem

agents session run produced no output (or hung indefinitely) when the Qoder agent needed to execute tools (e.g. Bash). The command would exit prematurely after receiving only thinking + tool_use events, missing the tool results and the final assistant reply.

Root Cause

Four interrelated issues:

1. Mapper: requires_action treated as terminal — Qoder mapper mapped all session.status_idle events to status: "idle", which is a terminal status. But idle with stop_reason=requires_action means the agent paused for tool execution and will resume. Poll/stream exited on the first idle before tool results arrived.

2. Stream: no SSE reconnection — streamWithResume did a single yield* of the SSE stream. When Qoder closes the SSE connection after requires_action, the generator exited without reconnecting for subsequent events (tool_result, final message).

3. SSE parser: id: field discarded — BaseApiClient.sse() only parsed data: lines, ignoring the SSE id: field. This made event.id always undefined, so stream reconnection could not use after_id to skip already-consumed events.

4. Polling: fixed 2s interval — collectEventsUntilTerminal used a fixed 2-second polling interval, adding unnecessary latency for fast responses.

Fix

File	Change
qoder/mapper.ts	Map session.status_idle + requires_action → "running" (non-terminal); extract raw.id → event.id
base-client.ts	Parse SSE id: lines and inject into yielded objects
session-runtime.ts	streamWithResume: reconnect loop with exponential backoff until terminal status; collectEventsUntilTerminal: exponential backoff (300ms → 2s) instead of fixed 2s
session-event-mappers.test.ts	Test coverage for requires_action mapping

Performance

Scenario	Before	After
No tools (say hi)	~10s	~10s (unchanged)
Single tool (echo) stream	hang / 107s	21s
Single tool (echo) polling	no output / 80s	22s

Remaining latency is dominated by Qoder BYOC tool execution time (server-side), not client-side overhead.

[heimanba]

Problem

agents session run produced no output (or hung indefinitely) when the Qoder agent needed to execute tools (e.g. Bash). The command would exit prematurely after receiving only thinking + tool_use events, missing the tool results and the final assistant reply.

Root Cause

Four interrelated issues:

1. Mapper: requires_action treated as terminal — Qoder mapper mapped all session.status_idle events to status: "idle", which is a terminal status. But idle with stop_reason=requires_action means the agent paused for tool execution and will resume. Poll/stream exited on the first idle before tool results arrived.

2. Stream: no SSE reconnection — streamWithResume did a single yield* of the SSE stream. When Qoder closes the SSE connection after requires_action, the generator exited without reconnecting for subsequent events (tool_result, final message).

3. SSE parser: id: field discarded — BaseApiClient.sse() only parsed data: lines, ignoring the SSE id: field. This made event.id always undefined, so stream reconnection could not use after_id to skip already-consumed events.

4. Polling: fixed 2s interval — collectEventsUntilTerminal used a fixed 2-second polling interval, adding unnecessary latency for fast responses.

Fix

File	Change
qoder/mapper.ts	Map session.status_idle + requires_action → "running" (non-terminal); extract raw.id → event.id
base-client.ts	Parse SSE id: lines and inject into yielded objects
session-runtime.ts	streamWithResume: reconnect loop with exponential backoff until terminal status; collectEventsUntilTerminal: exponential backoff (300ms → 2s) instead of fixed 2s
session-event-mappers.test.ts	Test coverage for requires_action mapping

Performance

Scenario	Before	After
No tools (say hi)	~10s	~10s (unchanged)
Single tool (echo) stream	hang / 107s	21s
Single tool (echo) polling	no output / 80s	22s

Remaining latency is dominated by Qoder BYOC tool execution time (server-side), not client-side overhead.

[heimanba]

Problem

agents session run produced no output (or hung indefinitely) when the Qoder agent needed to execute tools (e.g. Bash). The command would exit prematurely after receiving only thinking + tool_use events, missing the tool results and the final assistant reply.

Root Cause

Four interrelated issues:

1. Mapper: requires_action treated as terminal — Qoder mapper mapped all session.status_idle events to status: "idle", which is a terminal status. But idle with stop_reason=requires_action means the agent paused for tool execution and will resume. Poll/stream exited on the first idle before tool results arrived.

2. Stream: no SSE reconnection — streamWithResume did a single yield* of the SSE stream. When Qoder closes the SSE connection after requires_action, the generator exited without reconnecting for subsequent events (tool_result, final message).

3. SSE parser: id: field discarded — BaseApiClient.sse() only parsed data: lines, ignoring the SSE id: field. This made event.id always undefined, so stream reconnection could not use after_id to skip already-consumed events.

4. Polling: fixed 2s interval — collectEventsUntilTerminal used a fixed 2-second polling interval, adding unnecessary latency for fast responses.

Fix

File	Change
qoder/mapper.ts	Map session.status_idle + requires_action → "running" (non-terminal); extract raw.id → event.id
base-client.ts	Parse SSE id: lines and inject into yielded objects
session-runtime.ts	streamWithResume: reconnect loop with exponential backoff until terminal status; collectEventsUntilTerminal: exponential backoff (300ms → 2s) instead of fixed 2s
session-event-mappers.test.ts	Test coverage for requires_action mapping

Performance

Scenario	Before	After
No tools (say hi)	~10s	~10s (unchanged)
Single tool (echo) stream	hang / 107s	21s
Single tool (echo) polling	no output / 80s	22s

Remaining latency is dominated by Qoder BYOC tool execution time (server-side), not client-side overhead.

[heimanba]

Problem

agents session run produced no output (or hung indefinitely) when the Qoder agent needed to execute tools (e.g. Bash). The command would exit prematurely after receiving only thinking + tool_use events, missing the tool results and the final assistant reply.

Root Cause

Four interrelated issues:

1. Mapper: requires_action treated as terminal — Qoder mapper mapped all session.status_idle events to status: "idle", which is a terminal status. But idle with stop_reason=requires_action means the agent paused for tool execution and will resume. Poll/stream exited on the first idle before tool results arrived.

2. Stream: no SSE reconnection — streamWithResume did a single yield* of the SSE stream. When Qoder closes the SSE connection after requires_action, the generator exited without reconnecting for subsequent events (tool_result, final message).

3. SSE parser: id: field discarded — BaseApiClient.sse() only parsed data: lines, ignoring the SSE id: field. This made event.id always undefined, so stream reconnection could not use after_id to skip already-consumed events.

4. Polling: fixed 2s interval — collectEventsUntilTerminal used a fixed 2-second polling interval, adding unnecessary latency for fast responses.

Fix

File	Change
qoder/mapper.ts	Map session.status_idle + requires_action → "running" (non-terminal); extract raw.id → event.id
base-client.ts	Parse SSE id: lines and inject into yielded objects
session-runtime.ts	streamWithResume: reconnect loop with exponential backoff until terminal status; collectEventsUntilTerminal: exponential backoff (300ms → 2s) instead of fixed 2s
session-event-mappers.test.ts	Test coverage for requires_action mapping

Performance

Scenario	Before	After
No tools (say hi)	~10s	~10s (unchanged)
Single tool (echo) stream	hang / 107s	21s
Single tool (echo) polling	no output / 80s	22s

Remaining latency is dominated by Qoder BYOC tool execution time (server-side), not client-side overhead.

[heimanba]

Problem

agents session run produced no output (or hung indefinitely) when the Qoder agent needed to execute tools (e.g. Bash). The command would exit prematurely after receiving only thinking + tool_use events, missing the tool results and the final assistant reply.

Root Cause

Four interrelated issues:

1. Mapper: requires_action treated as terminal — Qoder mapper mapped all session.status_idle events to status: "idle", which is a terminal status. But idle with stop_reason=requires_action means the agent paused for tool execution and will resume. Poll/stream exited on the first idle before tool results arrived.

2. Stream: no SSE reconnection — streamWithResume did a single yield* of the SSE stream. When Qoder closes the SSE connection after requires_action, the generator exited without reconnecting for subsequent events (tool_result, final message).

3. SSE parser: id: field discarded — BaseApiClient.sse() only parsed data: lines, ignoring the SSE id: field. This made event.id always undefined, so stream reconnection could not use after_id to skip already-consumed events.

4. Polling: fixed 2s interval — collectEventsUntilTerminal used a fixed 2-second polling interval, adding unnecessary latency for fast responses.

Fix

File	Change
qoder/mapper.ts	Map session.status_idle + requires_action → "running" (non-terminal); extract raw.id → event.id
base-client.ts	Parse SSE id: lines and inject into yielded objects
session-runtime.ts	streamWithResume: reconnect loop with exponential backoff until terminal status; collectEventsUntilTerminal: exponential backoff (300ms → 2s) instead of fixed 2s
session-event-mappers.test.ts	Test coverage for requires_action mapping

Performance

Scenario	Before	After
No tools (say hi)	~10s	~10s (unchanged)
Single tool (echo) stream	hang / 107s	21s
Single tool (echo) polling	no output / 80s	22s

Remaining latency is dominated by Qoder BYOC tool execution time (server-side), not client-side overhead.

[heimanba]

Problem

agents session run produced no output (or hung indefinitely) when the Qoder agent needed to execute tools (e.g. Bash). The command would exit prematurely after receiving only thinking + tool_use events, missing the tool results and the final assistant reply.

Root Cause

Four interrelated issues:

1. Mapper: requires_action treated as terminal — Qoder mapper mapped all session.status_idle events to status: "idle", which is a terminal status. But idle with stop_reason=requires_action means the agent paused for tool execution and will resume. Poll/stream exited on the first idle before tool results arrived.

2. Stream: no SSE reconnection — streamWithResume did a single yield* of the SSE stream. When Qoder closes the SSE connection after requires_action, the generator exited without reconnecting for subsequent events (tool_result, final message).

3. SSE parser: id: field discarded — BaseApiClient.sse() only parsed data: lines, ignoring the SSE id: field. This made event.id always undefined, so stream reconnection could not use after_id to skip already-consumed events.

4. Polling: fixed 2s interval — collectEventsUntilTerminal used a fixed 2-second polling interval, adding unnecessary latency for fast responses.

Fix

File	Change
qoder/mapper.ts	Map session.status_idle + requires_action → "running" (non-terminal); extract raw.id → event.id
base-client.ts	Parse SSE id: lines and inject into yielded objects
session-runtime.ts	streamWithResume: reconnect loop with exponential backoff until terminal status; collectEventsUntilTerminal: exponential backoff (300ms → 2s) instead of fixed 2s
session-event-mappers.test.ts	Test coverage for requires_action mapping

Performance

Scenario	Before	After
No tools (say hi)	~10s	~10s (unchanged)
Single tool (echo) stream	hang / 107s	21s
Single tool (echo) polling	no output / 80s	22s

Remaining latency is dominated by Qoder BYOC tool execution time (server-side), not client-side overhead.

[heimanba]

Problem

agents session run produced no output (or hung indefinitely) when the Qoder agent needed to execute tools (e.g. Bash). The command would exit prematurely after receiving only thinking + tool_use events, missing the tool results and the final assistant reply.

Root Cause

Four interrelated issues:

1. Mapper: requires_action treated as terminal — Qoder mapper mapped all session.status_idle events to status: "idle", which is a terminal status. But idle with stop_reason=requires_action means the agent paused for tool execution and will resume. Poll/stream exited on the first idle before tool results arrived.

2. Stream: no SSE reconnection — streamWithResume did a single yield* of the SSE stream. When Qoder closes the SSE connection after requires_action, the generator exited without reconnecting for subsequent events (tool_result, final message).

3. SSE parser: id: field discarded — BaseApiClient.sse() only parsed data: lines, ignoring the SSE id: field. This made event.id always undefined, so stream reconnection could not use after_id to skip already-consumed events.

4. Polling: fixed 2s interval — collectEventsUntilTerminal used a fixed 2-second polling interval, adding unnecessary latency for fast responses.

Fix

File	Change
qoder/mapper.ts	Map session.status_idle + requires_action → "running" (non-terminal); extract raw.id → event.id
base-client.ts	Parse SSE id: lines and inject into yielded objects
session-runtime.ts	streamWithResume: reconnect loop with exponential backoff until terminal status; collectEventsUntilTerminal: exponential backoff (300ms → 2s) instead of fixed 2s
session-event-mappers.test.ts	Test coverage for requires_action mapping

Performance

Scenario	Before	After
No tools (say hi)	~10s	~10s (unchanged)
Single tool (echo) stream	hang / 107s	21s
Single tool (echo) polling	no output / 80s	22s

Remaining latency is dominated by Qoder BYOC tool execution time (server-side), not client-side overhead.

[heimanba]

Problem

agents session run produced no output (or hung indefinitely) when the Qoder agent needed to execute tools (e.g. Bash). The command would exit prematurely after receiving only thinking + tool_use events, missing the tool results and the final assistant reply.

Root Cause

Four interrelated issues:

1. Mapper: requires_action treated as terminal — Qoder mapper mapped all session.status_idle events to status: "idle", which is a terminal status. But idle with stop_reason=requires_action means the agent paused for tool execution and will resume. Poll/stream exited on the first idle before tool results arrived.

2. Stream: no SSE reconnection — streamWithResume did a single yield* of the SSE stream. When Qoder closes the SSE connection after requires_action, the generator exited without reconnecting for subsequent events (tool_result, final message).

3. SSE parser: id: field discarded — BaseApiClient.sse() only parsed data: lines, ignoring the SSE id: field. This made event.id always undefined, so stream reconnection could not use after_id to skip already-consumed events.

4. Polling: fixed 2s interval — collectEventsUntilTerminal used a fixed 2-second polling interval, adding unnecessary latency for fast responses.

Fix

File	Change
qoder/mapper.ts	Map session.status_idle + requires_action → "running" (non-terminal); extract raw.id → event.id
base-client.ts	Parse SSE id: lines and inject into yielded objects
session-runtime.ts	streamWithResume: reconnect loop with exponential backoff until terminal status; collectEventsUntilTerminal: exponential backoff (300ms → 2s) instead of fixed 2s
session-event-mappers.test.ts	Test coverage for requires_action mapping

Performance

Scenario	Before	After
No tools (say hi)	~10s	~10s (unchanged)
Single tool (echo) stream	hang / 107s	21s
Single tool (echo) polling	no output / 80s	22s

Remaining latency is dominated by Qoder BYOC tool execution time (server-side), not client-side overhead.