Back to Signal Feed
CodeTracked since May 19, 2026

Deliver routed watcher events into conductor tmux panes

The PR adds end-to-end routing of watcher events from the agent dashboard into the matched conductor session’s tmux pane, by adding `RoutedTo` to `watcher.Event`, populating it in `engine.writerLoop`, and dispatching formatted events in `ui.Update` via `ui.dispatchWatcherEvent` instead of leaving them in the TUI only.

watcher.EventRoutedTowriterLoopui.dispatchWatcherEvent

What Happened

  • The PR adds end-to-end routing of watcher events from the agent dashboard into the matched conductor session’s tmux pane, by adding `RoutedTo` to `watcher.Event`, populating it in `engine.writerLoop`, and dispatching formatted events in `ui.Update` via `ui.dispatchWatcherEvent` instead of leaving them in the TUI only.
  • The PR adds end-to-end routing of watcher events from the agent dashboard into the matched conductor session’s tmux pane, by adding `RoutedTo` to `watcher.Event`, populating it in `engine.writerLoop`, and dispatching formatted events in `ui.Update` via `ui.dispatchWatcherEvent` instead of leaving them in the TUI only.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Implements a concrete behavior fix so GitHub/watcher notifications (PRs, comments, labels, CI outcomes) actually reach the intended conductor for action; previously they were only shown in the TUI and never delivered to the routed conductor’s execution pane.

Why Track This

Why It Matters

Conductor operators and automation flows can now see matched watcher events inside the target conductor pane as they happen, so GitHub activity can trigger immediate Claude reactions instead of being silently missed after reaching the dashboard. This is achieved by propagating router matches into each watcher event (`RoutedTo`), pushing them onto `routedEventCh`, and dispatching to `ConductorSessionTitle(evt.RoutedTo)` using the same tmux path already used by health alerts. Watch for whether required source settings are fully wired (dependency on the separate GitHub source settings work) and for coverage gaps where exact human-author matching misses bot-driven events, since those remain unrouted.

Impact

Conductor operators and automation flows can now see matched watcher events inside the target conductor pane as they happen, so GitHub activity can trigger immediate Claude reactions instead of being silently missed after reaching the dashboard. This is achieved by propagating router matches into each watcher event (`RoutedTo`), pushing them onto `routedEventCh`, and dispatching to `ConductorSessionTitle(evt.RoutedTo)` using the same tmux path already used by health alerts. Watch for whether required source settings are fully wired (dependency on the separate GitHub source settings work) and for coverage gaps where exact human-author matching misses bot-driven events, since those remain unrouted.

What To Watch Next

  • Watch whether watcher.Event becomes a repeated pattern.
  • Track follow-up changes around Agent Orchestration Platforms.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: pending_dependency_on_github_source_settings, empty_or_triage_routedto_events_dropped.
Open Topic TimelineOpen Technical EventOpen Original Sourcepending_dependency_on_github_source_settings / empty_or_triage_routedto_events_dropped / exact_author_match_missing_github_bot_events

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

asheshgoplani/agent-deck PR #939: feat(watcher): dispatch routed events to conductor tmux pane

Watcher events now follow the same delivery path as health alerts: matched routed events are forwarded to the proper conductor pane through tmux send-keys, while unrouted/triage events are intentionally skipped.