Skip to main content

handle_reactive_transcript

agentmux_srv::server::reactive

Function handle_reactive_transcript 

Source 
pub(super) async fn handle_reactive_transcript(
    __arg0: State<AppState>,
    __arg1: Query<TranscriptQuery>,
) -> Response
Expand description

GET /agentmux/reactive/transcript?agent=<name>&max_lines=<n> — read the tail of a registered agent’s session output, for a Warden Supervisor watcher agent to inspect on its own poll interval (v1 is pull/poll, not push — see docs/analysis/ANALYSIS_WARDEN_AUTO_CONTROLLER_CONTINUATION_WATCHER_2026_08_12.md).

As of SPEC_MUXSPECT_CROSS_TIER_CONVERSATION_VISIBILITY_2026_08_21.md Phase A, a miss on this instance’s own host-tier registry falls back to the host-global cross-channel shared registry and forwards a single-hop HTTP GET to the owning channel’s own instance — same auth (entry.auth_key as X-AuthKey) and loopback-only pattern handle_reactive_inject’s Tier 2b already uses (see that handler for the security rationale). Response carries "tier" so callers can tell which tier answered.