Skip to content

[Docs] Explain repository-owned agent instructions - #1677

Draft
roomote-roomote[bot] wants to merge 1 commit into
developfrom
docs/repository-agent-instructions
Draft

[Docs] Explain repository-owned agent instructions#1677
roomote-roomote[bot] wants to merge 1 commit into
developfrom
docs/repository-agent-instructions

Conversation

@roomote-roomote

Copy link
Copy Markdown
Contributor

​Opened on behalf of @mrubens. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

What changed

  • documented how Roomote's repository workflows discover scoped AGENTS.md guidance
  • clarified the generated shared-workspace AGENTS.md role without implying that it replaces repository instructions
  • limited CLAUDE.md discovery and precedence claims to the environment-setup workflow where they are explicitly supported
  • explained why AGENTS.md is the portable repository-owned source for mixed-model and mixed-harness teams

Why this change was made

Roomote already guides task agents through repository-owned instruction hierarchies, but the public environment documentation did not explain the behavior or its scope. Users should be able to centralize portable repository rules without relying on undocumented assumptions or duplicating guidance for each compatible agent tool.

Impact

Users can now see which repository instruction files Roomote workflows inspect, how scoped guidance is resolved during environment setup, and which higher-priority instructions repository guidance cannot override. This is documentation-only and does not change runtime behavior.

Screenshots

The Environment definition page explains portable AGENTS.md guidance and scopes CLAUDE.md precedence to environment setup.

@roomote-community

roomote-community Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

No code issues found. See task

Reviewed bc68c2f

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