Slack as a task source

A message is a task, its thread is the activity log, and reactions are the board.

Some teams' real backlog is a Slack channel. Peractor treats it as a first-class tracker.

Connect

The same Add to Slack install serves notifications and task sourcing — one app, one authorization. Then invite the bot to each source channel (/invite @peractor) and connect the channel from the tracker's settings page.

Capture: every post

Every top-level post in a connected channel becomes a task, so connect the channels that are already an intake queue: support, bug reports. Thread replies and bot posts are not tasks.

Posting is not acting. A task filed this way is an import, like an issue from Linear, and nothing runs in the poster's name. Nothing typed in Slack is a command either: the @peractor commands were removed, so start, stop and follow runs in Peractor. The Mention capture setting went with them, and a channel that had it now captures every post too.

Reactions are the board

No reaction means to do, 👀 means in progress, and ✅ means done — both emoji configurable. Peractor sets reactions as runs progress, and reads yours: a ✅ from a person resolves a task that is not running.

While a run is active, Peractor owns the status. A run is stopped in Peractor; no emoji stops one.

The thread is the loop

Run milestones post as replies under the source message. When a run asks a mid-run question, the thread gets the question and a link to the run, where it is answered.

Files shared on the message ride along as attachments.