Zokie for Slack
Create tasks and ship code from Slack. Type one line, and Zokie on your computer picks the task up and starts working. Ask how it is going, tell it what to do next, and get the summary with the pull request in the same thread.
Before you start
- A Zokie account. It’s free: get Zokie.
- Zokie installed, open and signed in on your computer. That is where the agent does the work.
- A Slack workspace where you can add apps. Some workspaces need an admin to approve a new app first.
Set it up
- Add Zokie to your workspace. Press Add to Slack, pick your workspace and press Allow. Slack shows what Zokie may do: use the
/zokiecommand, post replies, hear messages that mention it, read the direct messages you send it, and read history in channels it has joined. - Link your Zokie account. In any channel, type
/zokie link. Only you see the reply. Open its link while signed in to zokie.dev. The link works once and expires after 15 minutes. - Start a task. Invite Zokie to a channel with
/invite @Zokie, then type/zokie new Fix the login redirect. Or reply under a bug report with@Zokie fix this issue please: Zokie uses the original report and thread replies as task context. You can also send Zokie a direct message with what to build. - Steer it in the thread. Reply under Zokie’s message with
@Zokieand your next instruction, ask for its status, or allow what it asks for. - Get the summary. When the task is ready, Zokie posts the pull request, the agent’s last words and the estimated spend in the same thread. Reply
@Zokie mergeto merge it.
What it looks like




Commands
| Say | What happens |
|---|---|
/zokie new <what to build> | Starts a task. Zokie posts in the channel and that message's thread follows the task. |
/zokie <what to build> | Same as /zokie new: a chat that starts on your Mac right away. |
/zokie task <what to do later> | Saves it to your Backlog in Zokie. Nothing runs until you reply @Zokie start in its thread. |
@Zokie start | In a backlog task's thread: your Mac starts it, on the model you picked in Settings for tasks from Slack. |
/zokie status | Lists your last five tasks from Slack. Only you see it. |
/zokie link | Connects this Slack account to your Zokie account. |
/zokie help | Lists the commands. |
@Zokie <message> | Under a bug report: starts a task with thread context. In a task's thread: sends the agent your next instruction. |
@Zokie status | In a task's thread: what the agent is doing now. A plain question like “how is this going?” works too. |
@Zokie allow · @Zokie deny | In a task's thread: answers the agent when it asks permission to run something. |
@Zokie stop | In a task's thread: stops the agent. |
@Zokie merge | In a task's thread: merges the task's pull request. |
Only the person who started a task can steer it. Teammates in the thread can read along.
What Zokie sees in Slack
Zokie receives messages that mention it and the direct messages you send it. When a mention starts a task under a bug report, it also reads that thread: up to the first 15 messages before your mention and 9,000 characters of context. It saves this text with the task for the agent on your computer. Longer threads are marked incomplete; files and images are not downloaded. Existing installations need to approve the added history permissions by installing Zokie again. It never asks Slack for your name, email address or profile. It keeps your Slack user and workspace IDs to know which Zokie account is yours, and where each task’s thread is.
Into your own thread, Zokie posts the task’s title and status, the name of the computer it runs on, a progress line while it works (at most one every five minutes), the pull request link, the estimated spend (at public API prices, not your bill) and up to 600 characters of the agent’s last message. Your code stays on your computer. The Privacy Policy has the details.
Remove it
Remove Zokie from your workspace in Slack under Settings & administration, then Manage apps. Zokie stops posting at once. To disconnect your Zokie account but keep the app in Slack, write to support.