fix(slack): clarify named-channel posting limits#232
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
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.
Clarify that
slackChannelPostMessageonly applies to the active channel and add a regression eval for cross-channel post requests.The issue in #231 is model behavior, not deterministic tool routing. The active-channel post tool was being treated as if it could satisfy requests for another named channel, which let Junior post in the wrong place and report success.
This tightens the tool description so the model is told to explain the limitation instead of calling the current-channel post tool, and adds a routing eval that requires an in-thread refusal with no channel post for
#discuss-design-engineeringrequests.Fixes #231