Skip to content

fix(server): alerts default to the new CoS thread, not the retired one - #137

Merged
nullStack65 merged 1 commit into
release/native-0.1.10from
fix/watcher-default-new-cos
Nov 20, 2026
Merged

nullStack65 merged 1 commit into
release/native-0.1.10from
fix/watcher-default-new-cos

Conversation

@nullStack65

@nullStack65 nullStack65 commented Nov 20, 2026 •

Copy link
Copy Markdown
Owner

Problem

Kameron retired the old CoS thread (0ff5603d-…) on 2026-11-20 and asked that no automated alert wake it again. The fork's DEFAULT_MODEL_ALERT_WATCHER still named that thread. So every machine without its own modelAlertWatcher setting 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

  1. packages/contracts/src/settings.ts: the default watcher is now the replacement CoS thread (mcp:launch:4c07a2ef…) on the same laptop environment (2f360b2e-…).
  2. 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, modelAlertWatcher is set to the new CoS thread in ~/.t3/userdata/settings.json on 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: null plus a webhook). That supersedes this default on that host.

Verification

  • vp fmt --check passes on both changed files.
  • ThreadId is a trimmed non-empty string, so the mcp:launch: ID decodes.
  • CI covers typecheck and tests.

Deploy: fleet

Rollback

Revert this commit. To roll back live, delete modelAlertWatcher from a host's settings.json. The per-host backups are in ~/.local/state/closura/repoint-old-cos/.

🤖 Generated with Claude Code

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>
@coderabbitai

coderabbitai Bot commented Nov 20, 2026

Copy link
Copy Markdown

Important

  • Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@nullStack65
nullStack65 merged commit eb9d79b into release/native-0.1.10 Nov 20, 2026
4 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant