nextlevelbuilder / nextlevelbuilder/goclaw
[Bug] Telegram Topic-level requireMention: false does not override group-level requireMention: true
Nobody has claimed this yet.
- 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
- Set
require_mention: trueat group level - Set
require_mention: falsefor a specific topic inside that group - Send a message in that topic without mentioning the bot
- 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: falseat 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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- 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