fix(slack-researcher): make Slack research opt-in, surface workspace identity#521
fix(slack-researcher): make Slack research opt-in, surface workspace identity#521
Conversation
…ce identity
The slack-researcher was auto-dispatched by ce-ideate, ce-plan, and
ce-brainstorm whenever slack_* tools were detected, with no way to know
which Slack workspace was connected. This risks silently searching the
wrong workspace and injecting misleading context into plans and ideas.
Now the agent only runs when the user explicitly asks for Slack context.
The three calling skills show a lightweight hint ("Slack is connected")
instead of auto-dispatching. The agent itself now extracts the workspace
subdomain from search result permalinks and surfaces it in the output
header so users can verify the right instance was searched. Also adds
search modifier reference from the official Slack plugin's slack-search
skill and removes examples block to match other agents.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4608b79026
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
plugins/compound-engineering/agents/research/slack-researcher.md
Outdated
Show resolved
Hide resolved
- Skills now dispatch slack-researcher when the user explicitly asks for Slack context, rather than only showing a hint. This closes the gap where the consolidation step referenced Slack findings but nothing gathered them. - No-results template handles the case where no permalinks are available to extract a workspace subdomain (falls back to "unknown"). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e4958cfe71
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
…s connected' (#521) The hint checked tool presence, not actual connectivity. 'Slack tools detected' accurately reflects what we know (tools registered) without implying verified auth. The slack-researcher agent itself still performs a runtime connectivity check when actually invoked. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7ae9a443bf
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
…s missing (#521) When a user explicitly requests Slack context but no slack_* tools are available, the skills now surface a clear message instead of silently skipping the request. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…le (#521) Replace dense prose paragraph with a 2x2 routing table (tools available x user asked) for clearer agent processing. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Simpler and renders more reliably across contexts. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c8f9922485
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
…quest (#521) The consolidation step should include Slack context only when the researcher actually returned findings, not merely because the user asked. Prevents the model from inventing Slack-derived constraints when Slack was requested but unavailable. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 participant
Summary
Partially reverts the auto-dispatch behavior introduced in #495. The slack-researcher agent and its synthesis capabilities are preserved, but it is now opt-in only.
slack_*tools are detected, so users know it's available without the risk.**Workspace: mycompany.slack.com**), making it clear which instance was searched.Test plan
bun run release:validate— passes (50 agents, 41 skills)slack_*tools are present🤖 Generated with Claude Code