[Bug]: Antigravity adapter claims manual compaction support although ACP 1.3.0 treats /compact as model input
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 75/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
Línea de trabajo
Empieza por apps/server/src/orchestration-v2/Adapters/AntigravityAdapterV2.ts, en la configuración supportsCompaction; después, sigue cómo el adaptador ACP compartido gestiona la compactación y revisa las pruebas existentes de sesiones de proveedores. Añade cobertura de regresión que demuestre que Antigravity no informa de la finalización normal de un prompt como una compactación correcta; la tarea estará terminada cuando la capacidad no compatible esté deshabilitada y la prueba verifique ese comportamiento.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/server — Antigravity adapter's manual-compaction capability.
Summary
Antigravity's CLI has /compact, but the Antigravity ACP 1.3.0 runtime used by T3 does not handle it as a native compaction command. T3's Antigravity adapter nevertheless sets supportsCompaction: true.
The missing Compact context button is consistent with the runtime's advertised capabilities. Adding compact to the command catalog would expose an action that does not perform native compaction. The bug is the adapter's unsupported compaction capability and the resulting possibility of reporting successful compaction for an ordinary model response.
Steps to reproduce
The runtime behavior was verified directly over ACP in a disposable workspace and profile, using a copied credential file and no existing conversations:
- Start the managed Antigravity ACP 1.3.0 executable.
- Send
initialize,authenticatewithoauth-personal, andsession/newwith an empty MCP server list. - Send a
session/promptcontaining synthetic records and a marker to remember; wait for completion and recordusage_update. - Send a standalone
/compacttext block throughsession/prompt. - Inspect the response and subsequent usage updates.
Expected behavior
T3 should expose manual compaction only when its provider runtime can perform it. Unsupported compaction requests should fail clearly, without being sent to the model or recorded as successful compaction. The context-meter action should remain unavailable until Antigravity exposes a working manual-compaction path through ACP.
Actual behavior and runtime evidence
In the isolated ACP test:
- Agent version:
1.3.0. - Advertised commands:
planandlogout. - Initial prompt: assistant replied
READY; context usage was 15,393 / 1,048,576 tokens. /compact: assistant generated an ordinary summary of the synthetic records; context usage increased to 15,697 tokens. No compaction update was emitted.- Follow-up asking for the marker succeeded; context usage increased again to 15,881 tokens.
Inspection of the Python source bundled in the installed ACP runtime confirms that its command parser recognizes the advertised built-in plan command, with logout handled separately. /compact is passed through as ordinary model input. No manual-compaction handler was found in that source.
T3 source diagnosis
AntigravityAdapterV2setssupportsCompaction: true.- The shared ACP adapter consequently exposes
compactThread, forwarding/compactas a prompt. - Its turn-finalization path emits a completed
Context compacteditem when that prompt completes successfully and the flavor enables compaction. Ordinary prompt completion does not prove native compaction occurred. - The UI visibility check requires
compactin the advertised command catalog, which correctly keeps the button hidden for this runtime.
The false-success path above is traced from T3 source; the live reproduction exercised the native ACP runtime directly, not the complete T3 UI path.
Suggested fix
Disable Antigravity's unsupported manual-compaction capability and add regression coverage at the provider-session boundary. Document the ACP limitation. Do not inject a synthetic compact catalog entry unless a working native compaction path is implemented and verified.
Impact
Minor bug or occasional failure — T3 can treat an ordinary assistant summary as successful context compaction even though context usage has not decreased.
Version or commit
Source investigated: main at 069e63b11758. Installed T3 Code version: 0.1.1-nightly.20261020.3386.
Environment
- Antigravity ACP: 1.3.0
- OS: macOS 27.0.1
Related issues
- #15291 concerns missing Antigravity context usage and is closed.
- #16663 concerns ACP registry agents advertising native compaction while their adapter cannot dispatch it; this is a different capability mismatch.
Workaround
Start a new thread when a fresh context is needed. Do not rely on /compact sent through Antigravity ACP 1.3.0 to reduce context usage.
- Lenguaje dominante
- TypeScript
- Estrellas
- 24.8k
- Forks
- 6.4k
- Merge medio
- 3 h 39 min
- PR fusionados (30 d)
- 301
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de pingdotgg/t3code
-
bug needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
pingdotgg/t3code#22819 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
Los mantenedores suelen responder en 1 día
Todos los issues de pingdotgg/t3code
Issues similares
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
endora-commerce/endora-commerce#397 ·
Los mantenedores suelen responder en 1 día
-
level/task
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
wazuh/wazuh-dashboard-plugins#9472 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 63/100
Los mantenedores suelen responder en 1 día
-
ready-for-agent
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
xavxyz/bei-shan-lin-shui#57 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
opennextjs/opennextjs-cloudflare#1461 ·
Los mantenedores suelen responder en 1 día