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

Abierto
  • ¿Algo no está bien?
#237 1 comentario 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@EzequielKoulaksezian ya está trabajando en esto.

Desde el 2/11/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
10
Forks
2
Merge medio
4 h 57 min
PR fusionados (30 d)
121

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de egdev6/quorb

Todos los issues de egdev6/quorb

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.