Existing issues
What happened?
When the Antigravity desktop app and agy are both closed, the Antigravity provider falls back to an informational Offline · N conversations snapshot even if the signed-in agy CLI is installed.
The macOS CodexBar provider already covers this case by launching a short-lived agy session, waiting for its loopback quota service, reading usage, and stopping only the process it owns. Win-CodexBar should offer the same fallback so Gemini usage remains available without keeping Antigravity open.
Affected area
Steps to reproduce
- Install and sign in to
agy.
- Enable the Antigravity provider in Win-CodexBar.
- Close Antigravity and ensure no
agy process is running.
- Refresh Antigravity usage or run
codexbar usage --provider antigravity --source auto --brief.
- Observe an offline conversation count instead of live quota usage.
- Start
agy manually and refresh again; live Session/Weekly quota usage appears.
Logs, screenshots, or recordings
Before: Antigravity Offline · 37 conversations
After manually starting agy: live Session and Weekly quota windows
No credentials, account identifiers, or terminal output are required to reproduce the issue.
App version
v0.56.8
Windows version
Windows 11
Additional context
Upstream behavior is documented in docs/antigravity.md: CodexBar launches agy in a PTY when the desktop app is closed, waits for API/keyring readiness, and tears down only its owned child for a one-shot fetch.
A Windows implementation can reuse the existing portable-pty dependency and should:
- prefer an existing Antigravity or user-owned
agy process;
- launch
agy in a hidden ConPTY only when no runtime exists;
- bound readiness polling and never scrape or log TUI output;
- stop and reap only the task-owned child;
- preserve the current offline-history fallback when neither runtime nor CLI is installed.
Existing issues
What happened?
When the Antigravity desktop app and
agyare both closed, the Antigravity provider falls back to an informationalOffline · N conversationssnapshot even if the signed-inagyCLI is installed.The macOS CodexBar provider already covers this case by launching a short-lived
agysession, waiting for its loopback quota service, reading usage, and stopping only the process it owns. Win-CodexBar should offer the same fallback so Gemini usage remains available without keeping Antigravity open.Affected area
Steps to reproduce
agy.agyprocess is running.codexbar usage --provider antigravity --source auto --brief.agymanually and refresh again; live Session/Weekly quota usage appears.Logs, screenshots, or recordings
No credentials, account identifiers, or terminal output are required to reproduce the issue.
App version
v0.56.8
Windows version
Windows 11
Additional context
Upstream behavior is documented in
docs/antigravity.md: CodexBar launchesagyin a PTY when the desktop app is closed, waits for API/keyring readiness, and tears down only its owned child for a one-shot fetch.A Windows implementation can reuse the existing
portable-ptydependency and should:agyprocess;agyin a hidden ConPTY only when no runtime exists;