fix(telegram): remove the autonomous-silence notice — it only ever landed as a DM nag (DIVE-3910) - #49
Merged
Merged
Conversation
…nded as a DM nag (DIVE-3910) lodar, 2026-09-02: "I feel this works wrongly. better to kill completely. I never seen its been useful. its just confuses clients." DIVE-3422 added a notice after 3 consecutive channel-silent turns, so an autonomous session reporting into the void could be told apart from a hung one. Its own comment named the failure mode it had to avoid: "the same text in a human's DM is a nag, and a nag gets muted." It targeted `getGroupTopics()` first and fell back to `getAllowedChatIds()` — i.e. the human's DM — whenever no group topic was configured. No seat on this host configures one, so the fallback was not an edge case, it was the only path the notice ever took. It also fired wrongly. It reached the paired user at 10:27:55Z claiming 3 silent turns on a session that had replied to him at 10:25:50Z and 10:26Z, so the documented negative control (any turn reaching the channel resets the run) did not hold for a session that was actively conversing. Removes the call site, `lib/autonomous-silence.ts` and its unit file. The agent-side `silence-watchdog` hooks are deliberately UNTOUCHED: they nag the agent in its own transcript, never the user, and they are what keeps a session from going quiet on him. bun test 1048 pass / 0 fail; generator parity byte-exact on both committed forks.
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
1 participant
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.
lodar, 2026-09-02: "I feel this works wrongly. better to kill completely. I never
seen its been useful. its just confuses clients."
DIVE-3422 added a notice after 3 consecutive channel-silent turns, so an
autonomous session reporting into the void could be told apart from a hung one.
Its own comment named the failure mode it had to avoid: "the same text in a
human's DM is a nag, and a nag gets muted." It targeted
getGroupTopics()firstand fell back to
getAllowedChatIds()— i.e. the human's DM — whenever no grouptopic was configured. No seat on this host configures one, so the fallback was
not an edge case, it was the only path the notice ever took.
It also fired wrongly. It reached the paired user at 10:27:55Z claiming 3 silent
turns on a session that had replied to him at 10:25:50Z and 10:26Z, so the
documented negative control (any turn reaching the channel resets the run) did
not hold for a session that was actively conversing.
Removes the call site,
lib/autonomous-silence.tsand its unit file. Theagent-side
silence-watchdoghooks are deliberately UNTOUCHED: they nag theagent in its own transcript, never the user, and they are what keeps a session
from going quiet on him.
bun test 1048 pass / 0 fail; generator parity byte-exact on both committed forks.