feat(openclaw): switch broadcast strategy to sequential

[shunkakinoki]

Switch broadcast from parallel to sequential so agents can see each other's responses via the shared group context buffer.

• Code Review: 9 agents run in order, each building on previous feedback
• Twitter/Dev/Strategy: same — sequential responses that reference each other

2-file change: openclaw.tpl.json + openclaw.template.json

---

Summary by cubic

Set broadcast.strategy to "sequential" in openclaw.template.json and openclaw.tpl.json to let agents read and build on prior messages via the shared group context. Code Review and Twitter/Dev/Strategy pipelines now run agents one-by-one for incremental, referenced responses.

^{Written for commit b234211. Summary will update on new commits.}

[mesa-dot-dev]

You do not have enough credits to review this pull request. Please purchase more credits to continue.

[gemini-code-assist]

Summary of Changes

Hello @shunkakinoki, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request modifies the agent broadcast mechanism to operate sequentially rather than in parallel. This fundamental change allows agents to build upon previous responses within a shared context, which is crucial for workflows requiring iterative feedback, such as code reviews or conversational strategies where agents need to reference prior interactions.

Highlights

• Broadcast Strategy: The broadcast strategy for agents has been switched from 'parallel' to 'sequential' in the configuration files.
• Agent Interaction: This change enables agents to observe each other's responses via a shared group context buffer, facilitating sequential feedback and interaction.

Changelog

• config/openclaw/openclaw.template.json
  • Changed the 'strategy' field within the 'broadcast' section from 'parallel' to 'sequential'.
• config/openclaw/openclaw.tpl.json
  • Changed the 'strategy' field within the 'broadcast' section from 'parallel' to 'sequential'.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

📝 Walkthrough

Summary by CodeRabbit

• Bug Fixes
  • Updated broadcast delivery strategy to process messages sequentially instead of concurrently, ensuring ordered message delivery.

Walkthrough

Configuration changes to the OpenClaw broadcast system in two template files, altering the broadcast strategy from "parallel" to "sequential" for group delivery processing. No functional logic modifications or structural changes introduced.

Changes

Cohort / File(s)	Summary
OpenClaw Broadcast Configuration config/openclaw/openclaw.template.json, config/openclaw/openclaw.tpl.json	Changed broadcast strategy from "parallel" to "sequential" in both template files, affecting the processing order of group recipient notifications.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• feat(openclaw): add broadcast groups with multi-model agents #817: Modifies broadcast configuration for the same group (120363425148909388@g.us) with parallel broadcast setup; this PR changes that same group to sequential strategy.
• feat(openclaw): 24 agents across 12 WhatsApp groups #821: Updates OpenClaw broadcast configuration settings; directly related to the broadcast strategy changes in this PR.

Poem

🐰 Sequential hops, no more parallel play,
Messages now queue in orderly way,
One after one, like carrots so lined,
A rabbit approves this organized mind! 🥕

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: switching broadcast strategy from parallel to sequential in the openclaw configuration files.
Description check	✅ Passed	The description clearly explains the purpose of the change, the files affected, and the benefits (enabling agents to see each other's responses).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/broadcast-sequential

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[mesa-dot-dev]

Mesa Description

TL;DR

Switch broadcast strategy in OpenClaw from parallel to sequential.

What changed?

• openclaw.tpl.json and openclaw.template.json updated to switch the broadcast strategy from parallel to sequential, allowing agents to see each other's responses via a shared group context buffer.

^{Description generated by Mesa. Update settings}

[gemini-code-assist]

Code Review

This pull request changes the broadcast strategy from parallel to sequential in both openclaw.template.json and openclaw.tpl.json. This change is well-justified by the need for agents to see each other's responses and build upon them. The implementation is straightforward and correct. I have no concerns with this update.

[Copilot]

Pull request overview

Updates Openclaw’s group broadcast behavior to run agents sequentially so later agents can incorporate earlier agents’ outputs via the shared group context buffer.

Changes:

• Switch broadcast.strategy from parallel to sequential in the Openclaw config templates.
• Keep both template variants (.template.json and .tpl.json) aligned.

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	Changes broadcast strategy to sequential for group broadcasts.
config/openclaw/openclaw.template.json	Same strategy change to keep the generated template consistent.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[cubic-dev-ai]

No issues found across 2 files