feat(openclaw): add dev-opus and dev-gpt-codex WhatsApp group bindings - #1385
Conversation
Added WhatsApp group bindings for dev-opus and dev-gpt-codex to the dev group (120363405790595065@g.us), matching the existing broadcast config.
|
You do not have enough credits to review this pull request. Please purchase more credits to continue. |
📝 WalkthroughWalkthroughAdded a new agent Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
Mesa DescriptionTL;DRConfigured OpenClaw agents for WhatsApp group bindings, introducing a new What changed?
Description generated by Mesa. Update settings |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds agent bindings for dev-opus and dev-gpt-codex to a specific WhatsApp group in both openclaw.template.json and openclaw.tpl.json. The feedback indicates that these additions are redundant and inconsistent with the existing configuration pattern, as multi-agent groups are typically managed via the broadcast section to avoid duplicate message processing.
| }, | ||
| { | ||
| "agentId": "dev-opus", | ||
| "match": { | ||
| "channel": "whatsapp", | ||
| "peer": { | ||
| "kind": "group", | ||
| "id": "120363405790595065@g.us" | ||
| } | ||
| } | ||
| }, | ||
| { | ||
| "agentId": "dev-gpt-codex", | ||
| "match": { | ||
| "channel": "whatsapp", | ||
| "peer": { | ||
| "kind": "group", | ||
| "id": "120363405790595065@g.us" | ||
| } | ||
| } | ||
| } |
There was a problem hiding this comment.
Adding these agents to the bindings array appears to be redundant and inconsistent with the existing configuration pattern in this file.
In this repository, groups that handle multiple agents (like the one for dev-opus and dev-gpt-codex at line 739) are typically configured only in the broadcast section. Other multi-agent groups, such as the code-reviewer group (line 724) or the twitter group (line 735), do not have corresponding entries in the bindings list.
The broadcast configuration already ensures that messages from this group are routed to both agents. Adding them to bindings might cause unexpected behavior or duplicate processing (e.g., the agent triggering once via the binding and once via the broadcast). Since the broadcast entry for this group already exists, these bindings should be removed to maintain consistency.
}| }, | ||
| { | ||
| "agentId": "dev-opus", | ||
| "match": { | ||
| "channel": "whatsapp", | ||
| "peer": { | ||
| "kind": "group", | ||
| "id": "120363405790595065@g.us" | ||
| } | ||
| } | ||
| }, | ||
| { | ||
| "agentId": "dev-gpt-codex", | ||
| "match": { | ||
| "channel": "whatsapp", | ||
| "peer": { | ||
| "kind": "group", | ||
| "id": "120363405790595065@g.us" | ||
| } | ||
| } | ||
| } |
There was a problem hiding this comment.
Adding these agents to the bindings array appears to be redundant and inconsistent with the existing configuration pattern in this file.
In this repository, groups that handle multiple agents (like the one for dev-opus and dev-gpt-codex at line 739) are typically configured only in the broadcast section. Other multi-agent groups, such as the code-reviewer group (line 724) or the twitter group (line 735), do not have corresponding entries in the bindings list.
The broadcast configuration already ensures that messages from this group are routed to both agents. Adding them to bindings might cause unexpected behavior or duplicate processing (e.g., the agent triggering once via the binding and once via the broadcast). Since the broadcast entry for this group already exists, these bindings should be removed to maintain consistency.
}There was a problem hiding this comment.
Pull request overview
This PR extends the Openclaw WhatsApp routing configuration by adding explicit bindings entries for the dev-opus and dev-gpt-codex agents to the existing dev WhatsApp group (120363405790595065@g.us), aligning bindings with the already-present broadcast mapping.
Changes:
- Add WhatsApp group binding for
dev-opusto the dev group. - Add WhatsApp group binding for
dev-gpt-codexto the dev group. - Apply the same update to both the template source (
openclaw.tpl.json) and its generated output (openclaw.template.json).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| config/openclaw/openclaw.tpl.json | Adds two new WhatsApp group bindings entries for dev agents. |
| config/openclaw/openclaw.template.json | Keeps generated Openclaw config output in sync with the updated template bindings. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
All broadcast groups now respond simultaneously instead of sequentially.
- Added dev-gpt agent using __GPT__ (gpt-5.4) - dev group now routes to dev-gpt (was dev-gpt-codex) - dev-gpt-codex still exists for other uses
feat(fish): rename llmu to lmu for consistency in function naming
…gents with updated models
…gents with new configurations
… fallback configurations
Added WhatsApp group bindings for
dev-opusanddev-gpt-codexto the dev group (120363405790595065@g.us), matching the existing broadcast config.Summary by cubic
Switched the dev WhatsApp group (120363405790595065@g.us) to
dev-gpt(keptdev-gpt-codexfor other uses; removeddev-opus) and changed broadcast to parallel so groups respond at the same time. Addedcode-reviewer-gptandcode-reviewer-minimaxand updated broadcast to use them (removed deprecated reviewers incl.code-reviewer-gemini); moved Twitter totwitter-gptwith new fallbacks/tools; updated Security Scanner and Docs Checker to Minimax; added GPT↔Codex fallbacks across GPT configs for reliability; and renamed fish aliasllmutolmu.Written for commit 83ef7f7. Summary will update on new commits.