You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Slack and other integrations need discoverable setup without crowding the simple participant-first installation.
Scope
Add a separate optional-integrations picker for Coworker, Graphify, Slack, and hosted Devin; keep the participant default Claude + Codex. Add Slack manifest/OAuth/policy/channel/provider readiness doctor checks, redacted remediation, installation/upgrade/troubleshooting docs, and Board/cloud status links.
Fresh default setup has no Slack login, dependency, service, or extra prompt.
Scripted and interactive users can opt in explicitly.
Doctor distinguishes app install, identity mapping, repository/channel authorization, provider readiness, and cloud telemetry readiness.
Diagnostics disclose no private identities, channels, repository mappings, URLs, tokens, or task text.
Code Mower delivery
Produce exactly one independently reviewable PR for this issue. Record the named builder, keep one writer on the branch, run focused tests and applicable full checks, obtain an independent Code Mower review against the exact current head, resolve every P0/P1/P2 finding, and pass normal CI plus code-mower/gate. Update the parent epic with PR/head, review, validation, outcome, and safe metadata-only upload evidence. Do not put credentials, source, diffs, prompts, transcripts, private context, task/message prose, or raw provider output in cloud data.
Part of #903.
Problem
Slack and other integrations need discoverable setup without crowding the simple participant-first installation.
Scope
Add a separate optional-integrations picker for Coworker, Graphify, Slack, and hosted Devin; keep the participant default Claude + Codex. Add Slack manifest/OAuth/policy/channel/provider readiness doctor checks, redacted remediation, installation/upgrade/troubleshooting docs, and Board/cloud status links.
Dependencies
Acceptance criteria
Code Mower delivery
Produce exactly one independently reviewable PR for this issue. Record the named builder, keep one writer on the branch, run focused tests and applicable full checks, obtain an independent Code Mower review against the exact current head, resolve every P0/P1/P2 finding, and pass normal CI plus
code-mower/gate. Update the parent epic with PR/head, review, validation, outcome, and safe metadata-only upload evidence. Do not put credentials, source, diffs, prompts, transcripts, private context, task/message prose, or raw provider output in cloud data.