Repository navigation
fix(server): alerts default to the new CoS thread, not the retired one - #137
Merged
Merged
Conversation
The fork's default model-alert watcher still named the CoS thread that was retired on 2026-11-20, so every machine without its own modelAlertWatcher setting kept waking it with model, usage-limit and (on older builds) thread events. The default now names the replacement CoS thread on the same laptop environment. Model: claude-opus-5-5 Task: fix Agent: claude-code Lane: CLO-916 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Kameron retired the old CoS thread (
0ff5603d-…) on 2026-11-20 and asked that no automated alert wake it again. The fork'sDEFAULT_MODEL_ALERT_WATCHERstill named that thread. So every machine without its ownmodelAlertWatchersetting kept sending model alerts and usage-limit alerts there. Older builds, like the laptop's current desktop release, also sent "needs-person" thread events. Five wakes reached it between 07:48 and 08:44 UTC.Change
packages/contracts/src/settings.ts: the default watcher is now the replacement CoS thread (mcp:launch:4c07a2ef…) on the same laptop environment (2f360b2e-…).docs/operations/watcher-thread.md: the doc now says the default is Kameron's CoS, not Lead.Per bot-baseline rule 19, the fix ships as the fork default rather than as hand edits on each machine.
Live state
As a stopgap until this ships,
modelAlertWatcheris set to the new CoS thread in~/.t3/userdata/settings.jsonon the R720, the laptop, ASUS, Jeff's MacBook Air and omarcy-desktop. Settings are watched, so no restart was needed. The R720 server reloaded settings 0.1 s after the edit.On the R720 runner, the alert-router PR in closura-agent-config (pingdotgg#990) will later move model alerts to Linear (
modelAlertWatcher: nullplus a webhook). That supersedes this default on that host.Verification
vp fmt --checkpasses on both changed files.ThreadIdis a trimmed non-empty string, so themcp:launch:ID decodes.Deploy: fleet
Rollback
Revert this commit. To roll back live, delete
modelAlertWatcherfrom a host'ssettings.json. The per-host backups are in~/.local/state/closura/repoint-old-cos/.🤖 Generated with Claude Code