The Board
The Board is the primary view for a watched repo. It combines a planning surface for the operator with an execution surface driven by the daemon - live, drag-and-drop, and updated in real time via Server-Sent Events.
Two Layers, One Board
The board is divided into two clear domains. Everything left of In Progress belongs to the operator; everything right belongs to the daemon.
You decide which issues are worth doing and in what order. Drag issues from Backlog to Ready to queue them. Drag within Ready to reprioritize.
- Refine issues before queuing
- Set story points and model overrides
- Close or re-queue failed work
Workers run automatically. The board shows what they're doing, for how long, and lets you pause, resume, or stop them.
- Pause/resume in-flight workers
- Stop a runaway worker
- View elapsed time and status
Backlog
Contains every issue not yet promoted to the work queue. Issues are grouped by decision and sorted by issue number within each group. The sort order is most actionable first: reviewed → refined → reviewing → refining → unrefined.
Ready
The ordered work queue. The daemon claims issues top-down: the card at position 1 is the next to be picked up. Drag cards vertically within the column to reprioritize.
In Progress
Populated by the daemon. Shows every worker that is actively implementing, verifying, waiting for CI, resolving conflicts, or otherwise not yet merged. Workers paused by the operator also appear here, classified by their pre-pause status.
What each card shows
Merged
Shows workers that have successfully merged or are in the final reporting step. Also includes recently merged workers loaded from the database on page load. Cards here are read-only - no actions available.
issueState === "closed", a card shows issue_closed regardless of internal status. When prState === "merged", it shows merged regardless of internal status.
Issue Cards - Backlog & Ready
Backlog and Ready cards show a richer set of controls than In Progress cards. Every control is conditionally shown based on the current decision state.
Always shown
Links to GitHub for GitHub issues. Links to the internal issue page for internal issues. Internal issues also show a small Slop mark icon.
Rendered for every decision except unrefined. A refined card that was also reviewed shows an additional reviewed badge.
Links to the worker's run page when a worker exists for the issue; otherwise links to the issue itself.
Shown for pre-claim decisions
(unrefined, refining, reviewing, reviewed, refined, queued)
Starts a /refine skill run. Hidden once the issue has refined, reviewed, refining, or reviewing labels.
Starts a /review skill run. Hidden once reviewed or a review/refine is already in flight.
For queued, cancelled, or failed without a prior worker. Immediately starts a worker, optimistically removing the card.
For failed when a prior worker exists. Re-runs the failed worker from the beginning.
Numeric input. Valid values: 1, 2, 3, 5, 8, 13, 21. Each point maps to a fixed agent model + effort tier.
Asks the AI to score the issue from its description. Opens a harness picker (Claude / Codex / Copilot). A checkmark icon replaces the sparkle after auto-scoring.
Closes the issue. Shown for unrefined, refining, reviewing, reviewed, refined, and queued decisions.
Opens the per-issue config popover. Set model, effort, implement mode, auto-merge/review/address modes, and accepted review level before the daemon claims the issue.
Drag and Drop
Dragging is optimistic: cards move instantly in the UI. The snapshot from the next daemon poll confirms or reverts the position.
Drag a Backlog card to Ready to promote it to the work queue. Drag a Ready card back to Backlog to demote it. The target column highlights with an accent ring while a card is dragged over it.
Drag a Ready card on top of another Ready card to insert it before that position. A drop slot highlights with an accent border and ring. The daemon always claims the topmost card first.
Filters
Filter controls appear on the left side of the toolbar. They apply to Backlog and Ready only (except Batch, which also scopes In Progress and Merged).
| Control | What it filters |
|---|---|
| Search box | Issue number, title, or decision - substring match, case-insensitive. |
| Stage | All stages / Unrefined / Refined / Reviewed / In Progress (issues labeled refining or reviewing). |
| Points | Specific story-point values, or Unpointed to find issues that still need scoring. |
| Harness | Claude Code / Codex / Copilot - filters by the effective agent harness for each issue. |
| Batch | Scopes the board to only the issues belonging to a saved batch. Also scopes In Progress and Merged to the batch's issue set. |
Status & Actions
Controls on the right side of the toolbar manage repo-level state and automation settings.
An "Automation" pill, highlighted when any automation is active. Opens a popover with four toggles: Autopilot, Auto-merge, Auto-review, Remote.
Shows whether base-branch CI is passing, failing, pending, or absent (links to GitHub Actions). When failing and no fix is in flight, a Fix CI button appears.
Shows ↑ahead ↓behind commit counts relative to origin. A sync button appears when out of sync.
Suspends the daemon's poll-and-claim loop. In-flight workers continue. A "polling paused" badge appears inline next to the button while paused.
Opens the watched repo on GitHub in a new tab.
Pull Requests & Worktrees
Below the columns, two collapsible panels surface additional operational context.
Open Pull Requests
Lists every open PR in the watched repo, whether or not Slop created it.
- CI status badge (passing / failing / pending / none)
- PR number linking to GitHub
- Draft indicator when applicable
- Linked issue number (if Slop can infer the link)
- Merge button - active only when CI is passing and PR is not a draft
···menu: Review PR, Address comments, Close PR
Worktrees
Lists local git worktrees parked at waiting_merge in local mode (no GitHub PR).
- Issue link and title
- Branch name
- Worktree path on disk
- Merge button - fast-forwards the worktree into the base branch
Base CI Alert
When the base branch CI is failing, a red alert banner is rendered above the board:
Issue Flow Summary
Issues follow a forward path from GitHub through Backlog, Ready, and In Progress to Merged. They can move backwards by dragging from Ready back to Backlog, or be retried from failed/cancelled states.