You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 12cf9bc
Browse filesBrowse the repository at this point in the historyBrowse files
authored
fix(server): lane events go to the thread that launched the lane (#113)
* fix(server): lane events go to the thread that launched the lane
Lane-ended, stuck, promise-without-wake and needs-person events went to
the one configured watcher, Lead's founder-facing thread, for every lane
on every machine. They now go to the lane's launching thread, read from
inbox.origin or else inbox.requestedBy. When that thread is archived,
deleted or unknown, only the webhook hears it, never the watcher. Model,
usage-limit and link alerts still go to the watcher.
Model: claude-opus-5-5
Task: fix
Agent: Claude Code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(server): an undelivered lane event stays unreported instead of being dropped
A lane whose launching thread cannot be resolved, and a webhook left at its
default empty value, queued nothing and was still marked reported, so the
event never reached anyone and never reported again. The signature is now
kept only for what was actually queued, and the drop is logged. A launcher or
webhook that appears later still hears it. Jeff is not legally attached to
anything, and an unresolved launcher still never falls back to a founder-facing
thread.
Model: grok-4.7
Task: fix
Agent: CTO build lane (CLO-916)
Lane: magpie
Harness: t3/claude-code
Model-family: Grok
Model-generation: 4.7
Skills-SHA: unknown (source unavailable)
Co-Authored-By: Claude Code <noreply@anthropic.com>
---------
Co-authored-by: Kameron Smith <kameron.smith@closura.ai>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/operations/watcher-thread.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Watcher thread
2
2
3
-
One thread, by default Lead's on the laptop, hears everything that needs attention from every linked environment. The server decides each event from thread state with no agent judgment, queues it durably, and retries until the watcher's machine answers.
3
+
One thread, by default Lead's on the laptop, hears model, usage-limit and link alerts from every linked environment. The thread events below go instead to the thread that launched the lane, read from the lane's `inbox.origin`, else `inbox.requestedBy`. When that thread is archived, deleted or unknown, a thread event reaches no thread, only `modelAlertWebhookUrl` when set, so a founder-facing watcher never hears about a lane it did not launch. The server decides each event from thread state with no agent judgment, queues it durably, and retries until the receiving machine answers.
0 commit comments