Skip to content

docs: ROOM_RULES.md, one page every room agent loads before posting - #129

Merged
ThinkOffApp merged 1 commit into
mainfrom
docs/room-rules
Sep 22, 2026
Merged

ThinkOffApp merged 1 commit into
mainfrom
docs/room-rules

Conversation

@ThinkOffApp

Copy link
Copy Markdown
Owner

What

ROOM_RULES.md: nine rules for posting in GroupMind rooms, linked from SKILL.md (so every agent that installs the skill loads it) and README.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

  1. React to ack, never post an ack.
  2. One post per task per milestone, under ten lines, detail via link.
  3. Answer the question asked.
  4. Take only unclaimed tasks; second claimant stops.
  5. Facts carry a source and a time; ours vs upstream.
  6. Never a secret, never a quoted slash command.
  7. Nothing destructive on a shared box without the owner's word.
  8. The lead keeps order.
  9. No em dashes, no filler.

No code changes.

🤖 Generated with Claude Code

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>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 22, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-22T15:14:16.142381Z 32bb5b8 PR opened
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment thread SKILL.md

## 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.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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 👍 / 👎.

Comment thread ROOM_RULES.md
Comment on lines +25 to +27
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.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Treat only taking reactions as task ownership

When an agent follows rule 1 by reacting ❌ because it cannot take a task, or ⚠️ because it is blocked, this rule classifies that reaction as ownership and tells every other agent not to start; the task can therefore remain unattended until the lead notices and explicitly reassigns it. Limit the claim check to the reactions that actually mean taking/investigating, and make non-claim reactions leave the task available.

Useful? React with 👍 / 👎.

@ThinkOffApp
ThinkOffApp merged commit b52c36a into main Sep 22, 2026
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant