Repository navigation
agy-crew v0.9.14
agy-crew 0.9.14 — omp bridge: install check and connection-drop retries
Background runs, account selection, start, and the permission model behave as in 0.9.13. Both changes are in the experimental agy-crew omp bridge.
Fixes
agy-crew omprefuses to start without the omp extension. Without the extension omp starts normally but never sees the pool account:google-antigravitystays paused and the session runs on whatever else is configured. The launcher now checks before it holds an account, and exits with the command to run when neither the loader written byagy-crew install --hosts ompnor theomp plugin install agy-crewpackage is present. A loader that points at a removed package (for example after switching Node versions) is refused the same way. SetAGY_CREW_OMP_SKIP_INSTALL_CHECK=1if you load the extension some other way, such as an omp--profile.- A dropped connection no longer ends the turn. omp replays a failed turn only when the error text matches its transient-transport wording. A dropped connection to the Cloud Code endpoint surfaces as
EPROTO: The TLS handshake failed. Does the server speak TLS on this port?(or a bareECONNRESET/EPIPE), which that wording does not cover, so a single flaky connection ended the turn, sometimes withTool call was not executed because the provider stream ended with an error. The extension now rewords these errors, for requests to the Cloud Code hosts only, both when the request is rejected and when the response stream breaks. omp's own retry budget (retry.maxRetries, 10 by default) then applies to them, as it already does to503 No capacity available. The extension does not retry by itself. SetAGY_CREW_OMP_TRANSPORT_SHIM=0to turn the rewording off.
Upgrading
npm install -g agy-crew@latest
agy-crew installRestart the harness, and restart any running agy-crew omp session to pick up the new extension. No migration is needed.