Headroom: the tool path, measured; provider path documented as blocked
This commit is contained in:
@@ -113,7 +113,14 @@ 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.
|
||||
|
||||
## Headroom: blocked, with a measured reason
|
||||
## Headroom: a tool, not a provider
|
||||
|
||||
The `headroom-bridge` extension gives an agent two tools (`compress_for_agent`,
|
||||
`check_headroom`). The endpoint answers (`POST /v1/compress` → 200). It needs the `headroom-ai`
|
||||
npm package for Pi to resolve, which is not installed; then the extensions picker can give it to
|
||||
one agent. As a *provider* it does not work here: 502 on OpenAI requests, 401 on Anthropic ones.
|
||||
|
||||
## Headroom: blocked as a provider
|
||||
|
||||
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
|
||||
|
||||
Reference in New Issue
Block a user