nextlevelbuilder / nextlevelbuilder/goclaw

[Bug] Telegram Topic-level requireMention: false does not override group-level requireMention: true

Open
#464 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

agent:github-maintain area:channels maintain:triaged P2-medium P3-low
Dominant language
Go
Stars
3.6k
Forks
1.1k
Avg merge
3d 5h
Merged PRs (30d)
24

Description

Bug Report

Description

When require_mention: true is set at the group level and require_mention: false
is set for a specific topic, the topic-level setting is ignored. Bot still requires
a mention inside that topic.

Config
{
  "channels": {
    "telegram": {
      "token": "...",
      "groups": {
        "-1003710073308": {
          "require_mention": true,
          "topics": {
            "42": {
              "require_mention": false,
              "allow_from": ["tg:USER_ID"]
            }
          }
        }
      }
    }
  }
}
Steps to Reproduce
  1. Set require_mention: true at group level
  2. Set require_mention: false for a specific topic inside that group
  3. Send a message in that topic without mentioning the bot
  4. Bot does not respond
Expected Behavior

Topic-level require_mention: false should override group-level require_mention: true.
Bot responds to all messages in that topic without requiring a mention.

Actual Behavior

Bot ignores the topic-level setting and still requires a mention,
as if inheriting the group-level require_mention: true.

Additional Notes
  • Setting require_mention: false at both group and topic level works correctly
  • Bug only occurs when group and topic levels have conflicting values
  • Docs state config lookup order is: Global → Wildcard → Group → Topic
    topic should take highest priority but does not
Environment
  • Channel: Telegram
  • Chat type: Supergroup with Forum/Topics enabled
  • GoClaw version: v2.13.0:full

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the Telegram configuration lookup for group and topic require_mention values, using the documented Global → Wildcard → Group → Topic order as the reference. Verify with a conflicting group/topic case that false overrides true and the bot responds without a mention.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.