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

Headroom measured and blocked; Mouse-1 triage command built and run

Browse Source
This commit is contained in:
Sam
2026-11-11 18:39:38 +11:00
parent 70e1f55486
commit 7a2d4358d3
10 changed files with 1091 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
docs/NEXT.md
View File

@@ -113,12 +113,20 @@ The one place it would earn its keep here: a failed run in `Agents>agents` offer
asks "what does this failure need" with four options and records the answer, the confidence and
the options on the task. A person still decides, and it never decides a merge.
## Done: Headroom
## Headroom: blocked, with a measured reason
A provider entry in `~/.pi/agent/settings.json` pointing at `http://192.168.20.13:8787/v1`, and
an agent's model set to `headroom/<model>`. Per agent, because the model is per agent; per
project is not possible. The exact steps and the one unknown to measure are in
`docs/PLAN-INTERFACE.md`.
A provider entry was added, tested and removed. Headroom answers `502 proxy_error` to OpenAI
chat requests and `401 invalid x-api-key` to Anthropic ones: its backend is Anthropic and this
machine has no Anthropic credential. It cannot sit in front of the agents until either headroom
accepts the omni router's key, or the agents move to an Anthropic-shaped provider. The detail is
in `docs/PLAN-INTERFACE.md`.
## Done: Mouse-1 triage
`bin/triage <task> [--ask next|failure]` asks Mouse-1 one four-option question about a task and
writes the answer, the confidence and the option meanings onto the task as a comment. Measured
on `AUD-162`: 0.5 s warm, answer `person` at 0.97 confidence. The cold start reproduces: `503`
after 30.5 s, then `200` in 21.7 s, so the command retries exactly once and says so.
## Unproven, and worth a test

24
docs/PLAN-INTERFACE.md
View File

@@ -640,6 +640,30 @@ without the provider.
to the company, not to a project. The finest granularity is one agent, which is what the
`Agents>settings` model field already gives.
### Measured afterwards: it does not work yet, and why
A provider entry was added and removed again after testing, because requests fail:
```
POST http://192.168.20.13:8787/v1/chat/completions → 502 {"code":"proxy_error"}
POST http://192.168.20.13:8787/v1/messages → 401 "invalid x-api-key" (Anthropic shape)
POST http://192.168.20.13:20129/v1/chat/completions → 400 (the router's own model naming)
```
Headroom's backend is `anthropic`: it speaks the Anthropic Messages API and authenticates with
an Anthropic key, which this machine does not have. The omni router uses an OpenAI-shaped API
with its own key. So headroom cannot be put in front of the agents as things stand.
To use it, one of these is needed:
1. an Anthropic-compatible credential in headroom, and agents moved to an Anthropic-shaped
provider;
2. or headroom configured to accept the omni router's OpenAI API and key;
3. or nothing — the omni router already does model routing, and headroom's only addition would be
prompt compression.
The provider entry was removed so no agent can be pointed at a failing endpoint by accident.
## Mouse-1, measured
The person supplied `docs/MOUSE-1-NOTES.md`, written from measurements on 2026-11-08/09. The