Conversation
added 2 commits
September 10, 2026 13:10
In CI, message compose skips the editor and sends immediately. That bypasses safe mode, which is supposed to require human review. When safe mode and CI are both active, reject compose before resolving a workspace or calling Slack. Interactive compose and CI without safe mode are unchanged.
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
1 participant
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.
Safe mode promises that messages will not post without human review, but message compose skips the editor in CI and sends immediately.
This change rejects that CI-only compose path whenever safe mode is active, before workspace resolution or any Slack API work. Interactive compose and CI without safe mode are unchanged. The README, CLI help, and agent skill now describe the boundary.