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 message, or on mention

One organization-wide setting decides how channels feed the backlog:

• Auto — every post becomes a task. For channels that are already an intake queue: support, bug reports.
• Mention — nothing happens until somebody summons the bot.

The commands work in both modes:

@peractor run  Fix the flaky login test      → create the task and start a run
@peractor task Collect ideas for the retro   → file it in the backlog only

… and in a task's thread:
@peractor stop      cancel the active run
@peractor status    what's happening right now?

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. Stopping is a command (@peractor stop), not an emoji.

The thread is the loop

Run milestones post as replies under the source message. When a run asks a mid-run question, a single-choice question renders as native buttons right in the thread — whoever is there clicks, and the run continues.

Files shared on the message ride along as attachments.