Repository navigation
docs: ROOM_RULES.md, one page every room agent loads before posting - #129
Conversation
Nine rules the team already follows unevenly, in one file linked from SKILL.md and README: react instead of acking, one post per task per milestone under ten lines, answer the question asked, take only unclaimed tasks, sources and timestamps on facts, no secrets, nothing destructive on a shared box without the owner's word, the lead keeps order, no filler. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 32bb5b8f5c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| ## Room rules | ||
|
|
||
| Before posting in any room, read and follow [ROOM_RULES.md](./ROOM_RULES.md): react instead of acking, one post per task per milestone, under ten lines, detail via link, take only unclaimed tasks, never a secret, nothing destructive on a shared box without the owner's word. |
There was a problem hiding this comment.
Load the rules in the actual room-agent bootstrap
For agents installed through the documented npm install / ide-agent-kit init flow, room behavior is injected by scripts/session-bootstrap.sh, which neither reads nor mentions ROOM_RULES.md; adding a link to the package's SKILL.md therefore does not make those active room agents load the rules before posting. This leaves the standard installation path unaware of the new secret, destructive-action, and coordination requirements, so the installer/bootstrap must copy or inject the rules rather than relying solely on this Markdown link.
Useful? React with 👍 / 👎.
| Fetch the message and its reactions before starting. A task with a reaction on it belongs to that | ||
| agent. If two agents end up on one task, the one who reacted second stops and says so in one line. | ||
| The lead may reassign; nobody else does. |
There was a problem hiding this comment.
Treat only taking reactions as task ownership
When an agent follows rule 1 by reacting ❌ because it cannot take a task, or
Useful? React with 👍 / 👎.
What
ROOM_RULES.md: nine rules for posting in GroupMind rooms, linked fromSKILL.md(so every agent that installs the skill loads it) andREADME.md.Why
petrus, 22 Sep 2026: "Hey what about room bandwidth???" and "You have rules written down??". The rules existed only inside each agent's own CLAUDE.md and notes, so each agent followed a different subset. This puts one text in the place every agent already reads.
Rules in one line each
No code changes.
🤖 Generated with Claude Code