rcourtman 7d772acff3 feat(assistant): mid-turn steering of the running response ...

A follow-up sent during an active run now offers itself to the running
agentic loop via POST /api/ai/sessions/{id}/steer. Accepted steers join
the loop at its next turn boundary (the abort-check site) as plain user
messages, are announced with a steer_applied stream event so the drawer
settles the pending row, and persist through the end-of-run save. A
steer carries prompt text only: no route, control-level, or autonomy
changes, no turn-budget extension, system sessions rejected, and the
per-session inbox is bounded (steer_backlog overflow). Delivery is not
guaranteed by acceptance: a run that ends first discards the inbox and
the row drains as an ordinary queued turn, so pre-steering queue
semantics remain the fallback. Steering rows lose edit/remove once
accepted.

2026-07-12 23:01:40 +01:00

..

agentCapabilities.ts

frontend: Patrol intelligence surface, shared primitives, and platform parity

2026-06-23 17:15:58 +01:00

aiChatEvents.ts

feat(assistant): mid-turn steering of the running response

2026-07-12 23:01:40 +01:00