[Bug]: Antigravity adapter claims manual compaction support although ACP 1.3.0 treats /compact as model input
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Idoneità per principianti
- 75/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- typescript
Direzione di ricerca
Inizia da apps/server/src/orchestration-v2/Adapters/AntigravityAdapterV2.ts, alla voce supportsCompaction; poi segui come l’adattatore ACP condiviso gestisce la compattazione ed esamina i test esistenti delle sessioni dei provider. Aggiungi una copertura di regressione che dimostri che Antigravity non segnala il normale completamento di un prompt come una compattazione riuscita; il lavoro è terminato quando la funzionalità non supportata è disabilitata e il test verifica questo comportamento.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- TypeScript
- Stelle
- 24.8k
- Fork
- 6.4k
- Merge medio
- 1h 22m
- PR unite (30g)
- 18
Preparare l'ambiente
Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di pingdotgg/t3code
-
MCP endpoint matches the Authorization scheme case-sensitively and logs the same reason for "absent" and "wrong scheme" (ChatGPT connector gets missing_bearer_token)Forse già presa Una pull request collegata a questa issue è aperta o già unita. Apertabug needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: OpenCode steer drops the thread's `agent` (and `variant`), so steered messages run on opencode's default_agentForse già presa Una pull request collegata a questa issue è aperta o già unita. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
bug needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
pingdotgg/t3code#23175 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di pingdotgg/t3code
Issue simili
-
bug skills
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
equinor/fusion-framework#5846 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 74/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
Eyevinn/open-videocore#1256 ·
I maintainer di solito rispondono entro 1 giorno
-
Frontend build fails with Frappe version-16: DataImport is no longer exported by @framework/uiApertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: Theme preset geist points at undefined --font-geistForse già presa @claude l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
I maintainer di solito rispondono entro 1 giorno