Antigravity (agy CLI): not working on macOS — wrong log path and process detection

Aperta
  • Qualcosa non va?
#237 1 commento 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@EzequielKoulaksezian ci sta già lavorando.

Dal 2/11/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

status:approved type:bug

Summary

Antigravity is listed as a supported provider in Quorb, but the README notes it is "Verified on Windows only for now". On macOS the provider always shows a warning because two assumptions in the code are correct for the Windows desktop IDE but wrong for the macOS agy CLI.

Root cause 1 — Wrong log path

log_path() builds:

~/Library/Application Support/Antigravity/logs/language_server.log

This path does not exist on macOS. The agy CLI writes its logs to:

~/.gemini/antigravity-cli/log/cli-YYYYMMDD_HHMMSS.log

Multiple files are created, one per session, with the naming pattern cli-<date>_<time>.log. The log format is identical — it contains the same lines Quorb looks for:

Starting language server process with pid 96831
Language server listening on random port at 57615 for HTTP

Root cause 2 — Process detection fails

find_server() filters processes by --app_data_dir antigravity and --csrf_token. On Windows the desktop IDE launches the language server with those flags. On macOS the agy CLI manages the language server internally and does not expose those arguments in the process list visible via ps. pick_server() therefore never finds a matching process and the provider returns NOT_RUNNING.

Environment confirmed

  • macOS (Apple Silicon)
  • agy CLI v1.2.13
  • Log directory verified: ~/.gemini/antigravity-cli/log/
  • Log lines are identical in format to what http_port() already parses correctly

Expected behaviour

With agy open on macOS, Quorb should read the most recent cli-*.log, extract the PID of the running language server, and query http://127.0.0.1:<port>/exa.language_server_pb.LanguageServerService/GetUserStatus.

Note on CSRF token

On macOS the language server process does not expose --csrf_token via ps. Whether the local HTTP endpoint requires the X-Codeium-Csrf-Token header from loopback needs to be confirmed. A fix can proceed in two phases:

  1. Phase 1 (this issue): fix log path and PID-based process detection on macOS.
  2. Phase 2: handle CSRF if the endpoint requires it.

Proposed fix

See the linked PR.

Lingua principale
TypeScript
Stelle
10
Fork
2
Merge medio
5h 55m
PR unite (30g)
123

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di egdev6/quorb

Tutte le issue di egdev6/quorb

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.