Skip to content

Slack

All three agents — Buck, Dolly, and Pearl — listen for mentions in Slack channels and threads. They share the same platform infrastructure for message handling, thread continuity, and interactive messages.

Mention the agent you need in any channel where the Slack app is installed:

@buck investigate the spike in 500 errors on the payments service
@buck implement the caching layer described in AD-1234
@dolly decompose this epic into tickets
@dolly what's the status of the auth migration?
@pearl review this design for accessibility
@pearl generate a card component for the product list

All agents maintain 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]

This works the same way for all three agents — each uses a shared session index to track thread-to-session mapping.

Buck and Dolly post 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)
  • Dolly — epic decomposition approval (approve individual tickets, approve all, request changes)

Buck and Pearl can process images shared in Slack threads. Images are:

  1. Downloaded via the Slack bot token
  2. Uploaded to S3 for permanent storage
  3. Sent to Claude as inline image data for visual understanding
  4. Included as URLs in any dashboard sessions created from the conversation

Pearl uses images as design context — upload screenshots, mockups, or design files and she incorporates them into reviews and component generation.

Supported formats: JPEG, PNG, GIF, WebP.

CommandDescription
/debugReturns the session ID, trace count, and a link to PostHog AI traces for the current session