sam/paperclip-harness
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Cleanup confirms and refreshes; projects switch sessions in place; explain verify.sh, headroom and Mouse-1

Browse Source
This commit is contained in:
Sam
2026-11-11 15:57:42 +11:00
parent 36abdc1f84
commit e02b39943d
13 changed files with 662 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/NEXT.md
View File

@@ -32,6 +32,12 @@ The cheap version first: a `t` entry that opens `~/.pi/paperclips` in Yazi, and
`Agents>agents` that reads the JSONL directly. `GET /api/agents/{id}/task-sessions` maps a task
to its session file, so neither version has to guess.
## Done: Project>projects — switching project
`bin/office` records each adopted project; the tab lists session, machine and folder; `enter`
asks once and switches the client with `tuios call switch-session`, including to a session on
another machine when that machine is in the client's `[hosts]` table. See `docs/SESSIONS.md`.
## 3. Project>projects — switching project
A tab listing every adopted project from a small local registry
@@ -98,8 +104,9 @@ step; a switch is only worth adding after one agent has been run both ways and m
## 9. MOUSE-1
The key is in the environment; the software is not installed. The old project's policy stands:
triage only, never a gate, never a permit. It would order `Board>needs`, never decide a merge.
Corrected: Mouse-1 is a hosted API, not software to install. `MOUSE_API_KEY` is present; what is
missing is a client call from our side. The old project's policy stands: triage only, never a
gate, never a permit — it could order `Board>needs`, never decide a merge.
## Unproven, and worth a test