> ## Documentation Index
> Fetch the complete documentation index at: https://darwin.so/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Darwin in Slack

> Bring Darwin discovery and coordinated work into a team conversation.

Use Darwin in Slack when the request, comparison, or approval should remain visible to a team.

<Note>
  Darwin is not yet listed in Slack Marketplace. Submission is blocked until the app is production-ready and remains
  installed on at least 10 active workspaces, then Slack performs preliminary and functional review.
</Note>

## Recommended model

Connect a Slack-facing application to Darwin through the API or SDK. Keep the Slack user and channel context in your application; send only the task inputs Darwin needs.

## Conversation behavior

* Show ranked Search options before starting work.
* Preserve the selected target and capability IDs.
* Store `threadId` and the last consumed cursor with the Slack thread.
* Render typed thread requests, revisions, and operation states as the current source of truth.
* Open connection, payment, and approval interactions through Darwin's first-party web flow.

<Note>
  Do not post API keys, OAuth tokens, provider credentials, or sensitive payment data into Slack messages or model
  context.
</Note>

## Map Darwin to the thread

| Slack surface | Darwin content |
| - | - |
| Initial thread | User intent and ranked Search options |
| Pinned application state | Selected target/capability IDs, `threadId`, revision and cursor |
| Thread update | Current summary and non-sensitive progress |
| Interactive message | Exact requested update or reviewed decision |
| Button to Darwin | First-party connection or payment `webLink` |

Do not rely on a channel message as durable application state. Store the Darwin identifiers server-side and authorize every Slack interaction against the user who clicked it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.