Skip to content

agy-crew v0.9.13

Choose a tag to compare

@github-actions github-actions released this 10 Nov 18:17
· 4 commits to master since this release

agy-crew 0.9.13 — omp bridge and daily update checks

Background runs, account selection, start, and the permission model behave as in 0.9.12.

What's new

agy-crew omp (experimental). Run omp on one held pool account:

agy-crew omp work1 -- --model google-antigravity/gemini-3.8-flash
agy-crew omp       -- --model google-antigravity/gemini-3.8-flash

-- ends agy-crew's flags; everything after it goes to omp unchanged. The command selects a pool account, holds it until omp exits, and provides the bundled omp extension with the account's runtime credential. The extension takes back the paused google-antigravity provider, installs the credential as a runtime bearer (no agent.db write, no profile, no session restriction), rewrites block 0 to the agy-crew identity, and strips cfg:// and omp:// fingerprints from prompts and tool declarations. A background agy warm-up refreshes the bearer before expiry. agy-crew install --hosts omp installs the extension loader; the extension is inert when AGY_CREW_OMP_ACCOUNT is unset, so a plain omp is unchanged.

The bridge accepts only auto or a pool account. It never reads a live agy login, so there is no special --account live handling in the omp path.

Daily npm update check. Interactive agy-crew start, the full-screen agy-crew inspect, and the human-facing accounts list / accounts quota tables check the npm registry at most once per 24 hours. When a newer release exists they print a one-line update notice on stderr. The result is cached in ~/.agy-crew/update-check.json.

The check requires a TTY and skips known coding-harness environments, so agent skill calls never check, wait, or write the cache. Machine-readable --json account output never checks. Set AGY_CREW_NO_UPDATE_CHECK=1 to disable it.

Fixes

  • Credential refresh no longer waits for agy's print turn. agy can refresh a file token in a fraction of a second and then keep the -p turn open much longer. The bridge and accounts quota --refresh now stop agy as soon as the token file changes, so agy-crew omp starts in seconds instead of appearing to hang for a minute.
  • The omp bridge raises Antigravity's first-event budget. omp's catalog gives Gemini Flash a 60-second first-event timeout. A cold or loaded Gemini start can exceed it, and omp reports Request was aborted before any token arrives. agy-crew omp now passes PI_STREAM_FIRST_EVENT_TIMEOUT_MS=300000 (an explicit user value still wins), matching the five-minute budget used for other providers.
  • The first request uses a valid credential. The launcher resolves and caches the Cloud Code project, and the omp extension registers the cached account credential as a provider fallback before model discovery. The role default no longer briefly falls back to another provider, and session_start still installs the runtime bearer.
  • The omp bridge no longer advertises or attempts live-account support; the bundled extension has no live branch.
  • agy-crew omp takes the account as an optional first positional, matching agy-crew start; its usage text lists [<name>].

Upgrading

npm install -g agy-crew@latest
agy-crew install

Restart the harness. If you use the omp bridge, re-run agy-crew install --hosts omp (or a normal agy-crew install) to refresh the extension loader. No migration is needed.