Repository navigation
Releases
v0.1.12
Full Changelog: v0.1.10...v0.1.12
v0.1.10
Account switching is off by default, and a turn that outlives agy's 180 s tool
deadline is relayed instead of lost.
The default that changed
account_failoveris new and off. A turn that fails on this account's own
quota, sign-in, credit or policy answers409, which Magpie does not fail over,
so the error reaches you and you pick the next account. Turn it on for the old
behaviour.- Two costs, both in
docs/error-routing.md§1.1: Magpie no longer rests the
account on that turn, and every5xxstays retryable whatever a plugin sends.
Tools
- A tool call that outlives
agy's 180 s MCP deadline is answered "still running"
after 150 s with its call id; the model asks again through
mcp_magpie_await_result(advertised from the firsttools/list, sinceagy
caches the catalog) and the caller's result lands in the same native prompt. A
result that arrives between the notice and that question is handed over instead
of being kept for the next prompt.
Usage
- A turn's usage is read from the
session/promptresult, subtracting what tool
batches already reported, with the step rows as the fallback. A row that lands
after the result no longer becomes the next turn's usage. - A local prompt timeout retires the worker: the deadline cancels nothing
upstream, so reusing the session let a later tool result start a second prompt.
Errors
- A bare
429on a prompt that carries a trigger line is answered400with a
hint, whether or not cloaking was on; a429that names which window is spent
keeps its own answer instead of being read as a refused prompt. - A suspended account answers
403, and is held out of routing for six hours only
when the turn's log agrees; a disabled account then fails fast instead of
spawningagyagain. - The refusal hint no longer claims a cause it cannot establish, and no message
promises account switching that is off.
Cloaking stays off by default. Two scope gaps closed: the two Codex lines in
your own messages (never in tool results), and cloak_said_as for
phrase=replacement pairs. Two others are recorded in docs/plan.md item 8.
magpie plugin add magpie-agy-acp@0.1.10393 tests, 11 release checks. CHANGELOG.md has the history; docs/error-routing.md
says why each status and wording is what it is.
v0.1.9
Failure statuses now match what Magpie's router reads, and thinking summaries are
carried the way a client can keep them without inventing an Anthropic signature.
Errors
- A vendor-suspended account answers
403 permission_errorwith Antigravity's own
sentence; aPERMISSION_DENIEDthat is not that suspension gets its own403.
Neither claims Magpie'sgoogleSuspendedroute, which needs the account's agent
to beantigravity/gemini, and a plugin account isplugin. NOT_FOUNDanswers404 not_found_errorso only that model rests; the vendor's
ownUNAVAILABLE/DEADLINE_EXCEEDEDanswers503with "overloaded" so no
failure is counted.- An oversized conversation answers
400whose words match Magpie'stooLongRe:
a member with room is asked, no account rests, and the agent is told to compact.
The vendor's own line follows asUpstream said: …, dropped when it would carry
limit wording or veto the overflow reading. agy's three terminal notices are all recognized (generic, dead connection,
spent credits); the last answers402.Retry-Aftercomes from the last wait a refusal names (clamped 1s…24h);
400/401/404also sendx-should-retry: false.error.typefollows the status as Magpie derives it:503and402say
api_error, notoverloaded_error/invalid_request_error.
Thinking
- Thought summaries carry a UUID-shaped signature: clients keep and replay the
block, and Magpie's preventive filter drops it before a Claude route
(deepseekSignature) instead of letting a fabricated prefix cost a
400 invalid signatureround trip per turn.expose_thinkingis on.
Prompts
- The turned-away harness lines are reworded (
based on→built on, …) rather
than broken up with zero-width characters, which the upstream has read past
since 11-14; a copy already broken up is repaired. Trigger matching reads past
invisible characters and white-space runs, with disjoint classes so a hostile
system prompt cannot stall the thread.
Tools
- ACP HTTP
mcpServersentries carry the requiredheaders: [], and a start
fails with the version whenagysays it has no HTTP MCP support.
v0.1.8
v0.1.7
v0.1.6
Full Changelog: https://github.com/sidkang/agy-acp/commits/v0.1.6