chore: autonomous agents may commit only in vault/80_agents (else approval)#189
Merged
Conversation
…80_agents, else approval
This was referenced May 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refines the AGENTS.md commit policy (follow-up to #188, which merged before this landed).
Autonomous agents (no human in the loop) may commit autonomously only within their vault workspace
80_agents/— that sandbox is theirs; everywhere else (code repos + the rest of the vault) they stage only and leave commits for human approval. Interactive/session agents commit when the user asks.SDD skip rationale
One-line policy clarification in AGENTS.md, <50 LOC, no new feature.