Platforms and integrations

Caude Clode in Slack

The Slack integration adds Caude Clode to your workspace as a bot user. You can mention it in any channel it's been invited to, or DM it directly. It can read threads, summarize channels, search your workspace, and answer questions about code. It cannot send messages on your behalf, set your status, or join calls.

Install

A workspace admin installs the app from the Slack App Directory. Once installed, anyone in the workspace can invite the bot to a channel with /invite @caude.

How to talk to it

In a channel:

bash

@caude summarize this thread
@caude what's the status of the checkout refactor
@caude link me to the PR we discussed on Monday

In a DM:

bash

(just type. no mention needed.)

Most questions are answered in the thread they were asked in. Long answers go to a DM to avoid overwhelming the channel, with a short summary posted inline so others can follow.

What it reads

By default, Caude Clode can read only messages in channels it's a member of, and only after the point at which it was invited. It cannot read history it wasn't there for. It cannot read channels it was never added to. If a conversation is relevant but happened somewhere else, the answer is that Caude Clode does not know.

What it writes

Replies to direct mentions or DMs. Threads where it was asked a question. It will not post unprompted. It will not react with emoji unless you explicitly ask it to. It will not add FYI! to a message.

The channel it wasn't added to

Most Slack workspaces have at least one channel where the real decisions happen, and Caude Clode is not in that channel. This is correct. Caude Clode does not need to be in every channel. If the decision was made there and you need it to act on the decision, paste the decision into a channel Caude Clode is in. Treating Caude Clode like a team member who cannot see DMs is accurate to how it works.

Tip: Do not invite Caude Clode to a channel with more than 5,000 members. It will join. It will not complain. But its responses will slow perceptibly as the history scales. Use DMs or smaller channels for actual back-and-forth.

Slash commands

A handful of shortcuts:

/caude summarize — summarizes the current channel's recent activity.
/caude thread — summarizes the thread you're in.
/caude digest — sends you a daily digest of channels you've subscribed it to.
/caude stop — cancels whatever Caude Clode is currently doing in the background.

Connecting to your repo

If you also have the GitHub App installed (see Vibe review), Caude Clode in Slack can reference PRs, issues, and commits by URL. Paste a GitHub link in a thread and ask a question. The link becomes context.

Permissions and privacy

The bot sees messages in channels it is in. Messages are sent to the model for inference. They are not stored long-term beyond the session. DMs to the bot are treated identically to channel messages in terms of model access. If your workspace has a retention policy, the bot respects it.

If you need stricter controls (Enterprise Grid, compliance mode, HIPAA, etc.), the admin settings expose the relevant toggles. Read them before enabling. Toggling them off later requires a workspace reinstall.

Removing

A workspace admin removes the app from the App Directory. Caude Clode leaves all channels. Message history with the bot remains in Slack (per your retention policy) but the bot can no longer read or respond.