Repository navigation
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.