Expand description
How many ambient CLI calls may run at once. AmbientGateway coalesces and
cancels only within one (entity, purpose) key; without a cap, N panes
finishing a turn at the same moment would each spawn their own CLI.
Two classes, each with one cap, so the total is bounded and a burst of background work can never hold up a call the user is waiting on. These replace six separate semaphores (pull calls, definition previews, backlog naming, narration, the recovery sweep’s own, and none at all for the continuity summary), each justified alone, none bounding the total. docs/reports/REPORT_AMBIENT_FRAMEWORK_REASSESSMENT_2026_10_08.md section 6.4.
Enums§
- Class
- Which queue an ambient call waits in.
Constants§
- BACKGROUND_
CAP - Simultaneous background calls, across all panes. One more than interactive: a continuity summary can run for up to 90 s, and narration should not wait behind two of them.
- INTERACTIVE_
CAP - Simultaneous interactive calls, across all panes.
- INTERACTIVE_
MAX_ QUEUE_ WAIT - The longest an interactive call waits for a permit before giving up. With
the 30 s interactive time limit (
purpose), a call ends within 40 s, inside the pane’s 45 s RPC timeout (ambient-rpc.ts), so a reply is never paid for after the pane has stopped waiting for it.