Repository navigation
fix(app): refuse a blocked teammate's @ace instead of posting a dead mention - #612
Merged
Merged
Conversation
This was referenced Oct 22, 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.
Fixes #600. In a teammate's channel with agent access off, a typed "@ace …" posted as a green "ace" mention and nobody was told the agent wouldn't answer.
The channel already refuses a blocked teammate's ask ("Only the owner can invoke agents here"). This fix stops the client from posting the same words as a
saythat reads like an ask.Smoke: isolated loopback host on port 4771 from this lane, rebuilt app. I created the channel with
ACE_USER=sam, so the browser's user is a teammate there, and agent access is off by default. The placeholder showed "Message the channel (agent access is off)". I typed "@ace what branch is this?" and pressed Enter. The toast appeared, the draft stayed, and nothing posted. Not covered: the owner still gets no notice when access is turned on or off (also in #600).Built in Ace
No. Built by Claude Code as a fix worker after the two-Mac pair study because the worker runs outside an Ace channel. Dogfooding gap tracked in #5.