Slack
Buck listens for mentions in Slack channels and threads, with platform support for message handling, thread continuity, and interactive messages.
How to use
Section titled “How to use”Mention @buck in any channel where the Slack app is installed:
Buck — engineering
Section titled “Buck — engineering”@buck investigate the spike in 500 errors on the payments service@buck implement the caching layer described in AD-1234Thread continuity
Section titled “Thread continuity”Buck maintains conversation context within a Slack thread. Follow-up messages in the same thread are routed to the same ADK session, so you can have multi-turn conversations:
User: @buck what does the payment webhook handler do?Buck: [explains the handler]User: can you add retry logic to it?Buck: [creates a Jira ticket and dashboard session, dispatches a plan session]Buck uses a session index to track thread-to-session mapping.
Interactive messages
Section titled “Interactive messages”Buck posts Block Kit interactive messages with buttons, select menus, and date pickers. When you interact with these (click a button, choose an option), your selection is routed back to the agent session as a follow-up message.
Common interactive patterns:
- Buck — plan approval buttons (approve, reject, request changes)
Multimodal support
Section titled “Multimodal support”Buck can process images shared in Slack threads. Images are:
- Downloaded via the Slack bot token
- Uploaded to S3 for permanent storage
- Sent to Claude as inline image data for visual understanding
- Included as URLs in any dashboard sessions created from the conversation
Supported formats: JPEG, PNG, GIF, WebP.
Slash commands
Section titled “Slash commands”| Command | Description |
|---|---|
/debug | Returns the session ID, trace count, and a link to PostHog AI traces for the current session |