AntFleet

Disagreement · f03404f9-anthropic-4

`telegram.enabled: true` in shared aeon.yml may surprise forks

solo Opus
repo 6f7fc663·PR #22·reviewed 1 week ago

Opus finding

`telegram.enabled: true` in shared aeon.yml may surprise forks

lowmaintainabilitymedium
  • aeon.yml:177-180
All skills in this aeon.yml are disabled (`enabled: false`) except `heartbeat`, suggesting this is the canonical template forks copy from. Setting `telegram.enabled: true` at the bottom means every fresh fork will poll Telegram every 5 minutes (per the comment above) even though no skills are enabled, requiring TELEGRAM credentials to avoid noisy errors. This is a footgun for new operators and inconsistent with the 'opt-in by default' pattern visible throughout the rest of the file.

Recommendation

Default `telegram.enabled: false` and document how to enable it; or scope the default-on behavior to only the upstream anchor repo (not the template forks see).

Other reviewer

The other reviewer flagged nothing in this file/line range.

Why this didn't post

This finding didn't meet AntFleet's unanimous agreement threshold. Both frontier models review every PR independently; only findings they both flag with the same severity and category are posted to the PR. This one fell through.

read the methodology →