Skip to content

Commit 54d2128

Browse files
committed
Document known limits and unverified risks
1 parent c2f8840 commit 54d2128

1 file changed

Lines changed: 10 additions & 0 deletions

File tree

README.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,16 @@ This toolkit fixes that by adding a local retry proxy and a lightweight status b
3535
- Multi-window per-conversation status isolation: verified locally
3636
- Automatic extension reload after external VSIX install: verified locally
3737

38+
## Known limits and unverified risks
39+
40+
- Verified on local macOS setups only. This repository has not been validated on Windows or Linux.
41+
- Verified against real transient `503` and quota-style `429` flows locally, but not against a broad matrix of upstream failure modes or long-running production traffic.
42+
- Multi-window conversation isolation has been verified locally, but not stress-tested under sustained high parallel request load.
43+
- The proxy currently has no separate max-concurrency control. Very high local parallelism may still increase upstream throttling rather than improve recovery.
44+
- Retry status lives in memory. If the proxy process restarts, in-flight retry history and current UI state are lost.
45+
- The setup depends on Antigravity internals such as `jetski.cloudCodeUrl`, local extension installation behavior, and current window/context signals. Future Antigravity builds could change those integration points.
46+
- Automatic window reload after external VSIX install has been verified locally, but there is no full headless end-to-end UI test suite yet.
47+
3848
## Screenshots
3949

4050
Before: Antigravity can stop on a transient upstream error and leave you with a manual retry loop.

0 commit comments

Comments
 (0)