You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Observations on omp + CLIProxyAPI Antigravity fingerprinting & 429 behavior vs official agy CLI
#19230
We audited the request pipeline when running omp through CLIProxyAPI against the official Antigravity CLI (agy v1.5.9) to understand potential client-fingerprinting vectors and 429 behavior on Cloud Code Assist (daily-cloudcode-pa.googleapis.com/v1internal:*).
1. Directly Observed Behavior
System prompt forwarding (omp + CLIProxyAPI):
Official agy v1.5.9 embeds and sends its own identity prompt ("You are Antigravity, a powerful agentic AI coding assistant designed by the Google Deepmind team working on Advanced Agentic Coding." or the generic-system-prompt variant).
CLIProxyAPI (internal/runtime/executor/antigravity_executor.go) has its systemInstruction constant commented out and does not inject an Antigravity identity prefix. As a result, omp's own system prompt and tool definitions are forwarded verbatim in request.systemInstruction while CLIProxyAPI sets "userAgent": "antigravity" and User-Agent: antigravity/hub/2.29.0 (aidev_client; os_type=darwin; arch=arm64; cl=1013060670).
Other observed payload/transport differences in CLIProxyAPI vs agy:
safetySettings: CLIProxyAPI deletes request.safetySettings (antigravity_executor_request.go), whereas agy defines SafetySetting in its request protos.
429 handling in CLIProxyAPI: In antigravity_executor_credits.go (decideAntigravity429), 429s that are not RESOURCE_EXHAUSTED with QUOTA_EXHAUSTED / RATE_LIMIT_EXCEEDED (or RATE_LIMIT_EXCEEDED without retryAfter) fall into antigravity429DecisionSoftRetry, which skips per-auth cooldown/transport eviction in antigravity_executor_execute.go / antigravity_executor_stream.go and returns 429 to the conductor (conductor_selection.go), allowing immediate retry/rotation across auths.
2. Hypothesis (Unverified Server-Side Behavior)
Our hypothesis is that upstream may use positive markers (Antigravity system prompt prefix, slash-delimited requestId, safetySettings) and negative markers (non-Antigravity harness prompts like omp's sent under "userAgent": "antigravity", plus immediate retry/auth-rotation on non-quota / firewall 429s) to flag accounts or link credentials.
Discussion
Sharing these concrete payload/header observations here so omp users routing through CLIProxyAPI (or similar Antigravity OAuth proxies) are aware of what is currently sent on the wire, and to see if others have observed similar 429 patterns or have thoughts on client-side vs proxy-side mitigation.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
We audited the request pipeline when running
ompthroughCLIProxyAPIagainst the official Antigravity CLI (agyv1.5.9) to understand potential client-fingerprinting vectors and 429 behavior on Cloud Code Assist (daily-cloudcode-pa.googleapis.com/v1internal:*).1. Directly Observed Behavior
omp+CLIProxyAPI):agyv1.5.9 embeds and sends its own identity prompt ("You are Antigravity, a powerful agentic AI coding assistant designed by the Google Deepmind team working on Advanced Agentic Coding."or thegeneric-system-promptvariant).CLIProxyAPI(internal/runtime/executor/antigravity_executor.go) has itssystemInstructionconstant commented out and does not inject an Antigravity identity prefix. As a result,omp's own system prompt and tool definitions are forwarded verbatim inrequest.systemInstructionwhileCLIProxyAPIsets"userAgent": "antigravity"andUser-Agent: antigravity/hub/2.29.0 (aidev_client; os_type=darwin; arch=arm64; cl=1013060670).CLIProxyAPIvsagy:requestId:CLIProxyAPIsends"agent-" + uuid.NewString(), whereasagy'scomputeRequestIDuses slash-delimited IDs (%v/%v/%v/%v/%v,%v/%v/%v/%v, or%v/%v).safetySettings:CLIProxyAPIdeletesrequest.safetySettings(antigravity_executor_request.go), whereasagydefinesSafetySettingin its request protos.429handling inCLIProxyAPI: Inantigravity_executor_credits.go(decideAntigravity429), 429s that are notRESOURCE_EXHAUSTEDwithQUOTA_EXHAUSTED/RATE_LIMIT_EXCEEDED(orRATE_LIMIT_EXCEEDEDwithoutretryAfter) fall intoantigravity429DecisionSoftRetry, which skips per-auth cooldown/transport eviction inantigravity_executor_execute.go/antigravity_executor_stream.goand returns 429 to the conductor (conductor_selection.go), allowing immediate retry/rotation across auths.2. Hypothesis (Unverified Server-Side Behavior)
Our hypothesis is that upstream may use positive markers (Antigravity system prompt prefix, slash-delimited
requestId,safetySettings) and negative markers (non-Antigravity harness prompts likeomp's sent under"userAgent": "antigravity", plus immediate retry/auth-rotation on non-quota / firewall 429s) to flag accounts or link credentials.Discussion
Sharing these concrete payload/header observations here so
ompusers routing throughCLIProxyAPI(or similar Antigravity OAuth proxies) are aware of what is currently sent on the wire, and to see if others have observed similar 429 patterns or have thoughts on client-side vs proxy-side mitigation.All reactions