Existing proposals
Problem
Agent Zero is currently centered on source-control workflows, but engineering teams also coordinate review, incidents, approvals, and task status in chat platforms. Without first-class Slack and Discord integrations, users must leave those environments to inspect Agent Zero tasks or trigger supported workflows.
Chat integrations must remain adapters around the control plane rather than becoming part of the agent runtime.
Desired outcome
Add first-class Slack and Discord integrations that expose a common provider-neutral interaction model.
Initial capabilities should include:
- install/connect Agent Zero to a Slack workspace or Discord server
- associate channels with repositories or projects using explicit authorization
- receive task, finding, verification, failure, and completion notifications
- inspect task status and verification evidence from chat
- trigger explicitly supported Agent Zero operations from commands/interactions
- request and record human approval for gated operations
- deep-link back to the relevant pull request, issue, task, or dashboard view
- use shared integration contracts so Slack and Discord do not duplicate business logic
- provide granular configuration for which events are posted to which channels
Implementation should introduce a provider-neutral integration boundary, with Slack and Discord as adapters. Provider-specific event payloads should be normalized before reaching the control plane.
Likely area
Developer experience
Safety and compatibility
High impact. Chat messages, commands, mentions, and interaction payloads are untrusted input. The integrations must verify provider signatures, map identities and repository permissions explicitly, prevent a channel command from bypassing repository policy, avoid leaking secrets or sensitive logs, and require existing approval gates for high-impact actions. Slack/Discord credentials must stay outside agent state and model prompts.
Alternatives considered
Webhook-only notifications are simpler but cannot support approvals or interactive task inspection. Building Slack and Discord logic directly into the agent runtime was rejected because it would couple orchestration to communication providers. A shared integration contract with thin provider adapters is preferred.
Existing proposals
Problem
Agent Zero is currently centered on source-control workflows, but engineering teams also coordinate review, incidents, approvals, and task status in chat platforms. Without first-class Slack and Discord integrations, users must leave those environments to inspect Agent Zero tasks or trigger supported workflows.
Chat integrations must remain adapters around the control plane rather than becoming part of the agent runtime.
Desired outcome
Add first-class Slack and Discord integrations that expose a common provider-neutral interaction model.
Initial capabilities should include:
Implementation should introduce a provider-neutral integration boundary, with Slack and Discord as adapters. Provider-specific event payloads should be normalized before reaching the control plane.
Likely area
Developer experience
Safety and compatibility
High impact. Chat messages, commands, mentions, and interaction payloads are untrusted input. The integrations must verify provider signatures, map identities and repository permissions explicitly, prevent a channel command from bypassing repository policy, avoid leaking secrets or sensitive logs, and require existing approval gates for high-impact actions. Slack/Discord credentials must stay outside agent state and model prompts.
Alternatives considered
Webhook-only notifications are simpler but cannot support approvals or interactive task inspection. Building Slack and Discord logic directly into the agent runtime was rejected because it would couple orchestration to communication providers. A shared integration contract with thin provider adapters is preferred.