If your team already uses Discord

Before you start

You need permission to add a bot to your Discord server. If you do not have it, the person who administers the server can invite the bot, and you can use Cook straight afterwards.

Putting it in your server

1. Open Settings → Apps → Chat apps. The same window can also open from a small Add Discord bar at the bottom of the sidebar, but that bar is not always shown: it takes turns with other prompts and disappears once you have connected a chat app or dismissed it.

2. The list shows Slack, Discord, Telegram and iMessage. Press Set up on the Discord row.

3. Press Open Discord invite, invite the bot to your server and approve it.
4. Prove the server is yours: Cook shows a short code. Type /pair <code> in a server channel Cook can see. Cook replies Linked! there and the setup page carries on by itself. If nothing happens, Cook cannot read that channel: try one without restricted permissions.
5. Pick the channels Cook should join.

Asking it for something

Send the Cook bot a direct message, or write @Cook in a channel it has been added to. Plain English — no slash commands. The same short chat commands as in Slack work here: !stop, !fast, !deep and !mute (see Chat commands).

Two things tell you it heard you: a chef mark appears on your message, and in a direct message Cook is typing… shows for as long as it is working.

Images and documents you attach to a direct message are read, and if a request needs an app you have not connected, the reply in a direct message carries a Connect button.

What comes back

• Numbers arrive as a card built from Discord’s own components: real text, themed to your server, readable on a phone.
• Documents arrive as real Discord attachments you can forward. Discord caps a bot upload at 10 MB per file; anything larger arrives as a download link instead, so a big file is never lost.
• Recordings of anything Cook did in its cloud browser come back as a watchable link. It opens in a browser, needs no Cook account, and does not expire.
• Long research is written up and filed in your Drive, with a link in the conversation rather than pages of text.

Approving what it proposes

Anything that spends money or leaves the building arrives as a card with Approve, Request changes and Reject buttons. Press one and it runs exactly as proposed; the request is frozen when the card is created.

When a proposal is a list, the card carries a picker. Untick anything you do not want before approving, and only the rest runs.

Who may press depends on your workspace’s own roles, set in Settings → Team → AI approvals. An owner can run some things without a card; a teammate’s request routes to whoever can sign it off.

Where the request turns up

The card goes to the person who has to decide, as a direct message, in the chat app they used most recently. If Cook cannot message that person directly, the card appears in the conversation where it was proposed instead, and anyone there who is allowed to decide can press it.

If something does not arrive

• Cook does not answer in a channel: the bot has not been added to that channel, or the channel is not linked yet. Open Settings → Apps → Chat apps, press Manage on the Discord row, and pick the channel.
• A teammate is refused: Cook does not know which Cook account their Discord account belongs to. There is no screen yet where a teammate can link their own Discord account, so ask us at support if this happens.
• A button says you are not the person it is routed to: the approval went to someone else under your workspace’s policy. They can press it, or an owner can.

If your team uses Slack instead

Cook works the same way in Slack. See If your team already uses Slack.