Files
paperclip-harness/.pi/memory-vault/packs/paperclip-harness/70-runbooks/editing-agent-settings-and-pausing-resuming-in-tui.md

5.1 KiB

type, id, title, status, source_of_truth, freshness, last_reviewed, tags
type id title status source_of_truth freshness last_reviewed tags
runbook runbook.paperclip-harness.editing-agent-settings-and-pausing-resuming-in-tui Editing agent settings and pausing/resuming in TUI active false current 2026-11-10
pack/paperclip-harness
agent-memory/runbook
paperclip
tui
runbook
agents
settings
pause

Editing agent settings and pausing/resuming in TUI

Trigger: need to change an agent's role/job title/model/budget/heartbeat, or pause/resume/wake an agent via the Paperclip TUI.

Prerequisites: TUI running, Agents pane available.

Procedure:

  1. Navigate to Agents>settings tab.
  2. Move cursor to the target agent on the roster; confirm ▸ is on the intended row (pause keys act on the selected agent — misselection can pause a live agent).
  3. enter on a field to edit inline; type value; enter saves, esc cancels. Heartbeat is a toggle.
  4. Save issues a single PATCH /api/agents/{id} that merges into existing config (does not wipe working folder/instructions). Model change applies to the agent's next run, not an in-flight run.
  5. To pause/resume/wake the selected agent press p / P / w respectively.

Verification / rollback: read the agent record back after saving to confirm fields persisted. If you accidentally pause an agent, resume with P; expect resume to return HTTP 200 and status to return to idle.

Detailed procedure from completed turn

Both defects fixed, and the settings editor is in.

The three things you reported

Runs were every run in Paperclip. Correct — 281 company-wide. They are now scoped to this project's tasks, resolved through each run's own task reference, and the task column shows AUD-166 instead of a bare identifier. A toggles between "this project" and "everything in the company", because both are legitimate questions but not the same one.

Scrolling instead of selecting. The run list had no cursor at all — arrows only moved the viewport. There is now one cursor per tab, the selected row is highlighted, and the list scrolls only to keep the cursor visible. enter opens that run's log. Tested: picked the second run, its log opened.

Roster could not be walked. Same cause, same fix. The roster is sorted by name so the cursor stays on the same agent after a reload, and ▸ marks the row.

The log itself also became readable: it is a stream of token deltas, so deltas are gathered back into paragraphs while tool calls, prompts and turn markers become single lines:

15:55:57 toolcall_start
15:55:57 {"command": "pwd && ls -la && git log --oneline -10 2>/dev/null"}
15:55:58 toolcall_end
15:55:58 assistant: I'll start by inspecting the workspace…

Agents>settings is built

Fourth tab. Role, job title, model, monthly budget, heartbeat. enter edits the chosen field inline, esc cancels; heartbeat is a toggle. Every save is one PATCH /api/agents/{id} that merges into that agent's existing configuration, so a model change does not wipe its working folder or instructions — verified by reading the record back after a save.

p, P, w pause, resume and wake, acting on the agent chosen on that tab.

One thing you should know: Builder was paused at 16:56 with pauseReason: manual, from the board key — that was my keystroke test, not you. I have resumed it and it is idle again. Sorry for the scare.

Still missing, in order

  1. Work>review — the ocr verdict beside the diff. That is now the only missing panel.
  2. Tool panes — t opens Lazygit, Hunk, Yazi, Neovim, fzf or ocr in the current workspace; esc closes it.

docs/WORKSPACES.md is updated: 22 panels built across 8 workspaces, one panel missing, six tool panes to wire. Committed as ec7e907.

Which of those two next?

Evidence

  • Confidence: 80%
  • Reason: Repeatable procedure with a safety caveat learned during the turn.; enriched with final-answer detail because persistence should be reusable