Slack bot integration roadmap

Summary

Track Slack-specific development independently from the TypeScript SDK.

The reference implementation is delivered. It supports Slack DMs and channel
threads, streaming responses, cancellation, remote authentication, caller
restrictions, and rate limiting. The remaining work concerns operating and
expanding the Slack integration rather than completing the SDK.

The delivered foundation is recorded in #881, #882, and #883. Those issues
close as completed.

Current work

Operations and deployment

• Use a hardened runtime image (#1085).
• Expose readiness and health for the Socket Mode connection (#1191).
• Reconcile the checked-in and deployed Slack app manifests (#1345).

Authorization and safety

• Complete interactive OAuth authorization from Slack (#1298).
• Add a manual permission approval flow using Slack UI components (#1397).
• Enforce a per-run token or spend budget (#1396).

Session continuity and behavior

• Persist Slack thread-to-Mecatl session bindings across bot restarts
  (#1399).
• Live-verify channel streaming, stop handling, and fallback behavior
  (#1398).
• Decide how stale or deleted Mecatl sessions affect retained Slack
  thread bindings.

Identity and expansion

• Explore multiple mentionable identities backed by Mecatl agent
  definitions (#1053).

Boundaries

This parent owns Slack events, interaction design, deployment, identity,
authorization presentation, and Slack-specific persistence.

Generic TypeScript SDK release work remains under #1394. Mecatl server,
MCP broker, and Redis storage changes retain their own parents and are linked
here only when the Slack integration depends on them.

Delivered foundation

• #995: initial Slack bot reference implementation.
• #1054: TLS, remote deployment, and machine authentication.
• #1245 and #1287: safer user-scoped failures and authorization handling.
• #1289: consumption through the published SDK package.

Completion

Close this parent when every linked Slack issue is either completed or moved
to a separately approved integration milestone.

Fully or partially written by an AI agent.

Start by reviewing the linked Slack work, especially #1085, #1191, #1345, #1298, #1397, #1396, #1399, and #1398, to understand the remaining integration scope. This parent is complete only when every linked Slack issue is completed or moved to a separately approved integration milestone.