Note the loopback bridge for shared dev servers

62ec83f22e94 · AtlantisPleb · · parent fe816df06eb0

Note the loopback bridge for shared dev servers

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GoYpb8FEmdxVErsv7ABCYi
Co-Authored-By
Claude Fable 5 <noreply@anthropic.com>

Deploy story

What this commit did to the running system — joined from the forge receipt chain, the part a commit page elsewhere cannot show.

Not deployed through the forge lane

No push, promotion, build, or deploy receipt references this commit (receipts are scanned over a bounded recent window). Changes shipped by full node replacement carry their proof in the release gate receipt instead.

Changed files

  • modified bench/README.md

Diff

1 file changed, +5 -0

bench/README.md modified +5

@@ -28,6 +28,11 @@ PYTHONPATH=bench OPENAGENTS_TOKEN=... harbor run \

28 28
`POST /api/v3/gym/runs`. Post only runs whose verifier actually ran: a
29 29
score is a claim, and a crashed grader is not a grade.
30 30
31
If the dev server binds loopback only (another session started it
32
without `PHX_LISTEN_ALL`), bridge instead of fighting over the port: run
33
a forwarder from `0.0.0.0:4001` to `127.0.0.1:4000` and point the
34
adapter at it with `OPENAGENTS_CODER_API_URL=http://host.docker.internal:4001`.
35
31 36
Known constraint on Apple Silicon: Terminal-Bench task images are amd64,
32 37
and under qemu emulation the verifier's `uv`/`pytest` segfaults after the
33 38
agent phase completes. Enable Docker Desktop's Rosetta emulation

This page updates live while a promote is in flight · changelog