[Bug]: Editing and resending a message shows a context handoff from a model to itself
I maintainer di solito rispondono entro 1 giorno
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 25/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Ferma
- Stack tecnologico
- typescript
- Ambito
- frontend, full-stack
Direzione di ricerca
Start with packages/client-runtime/src/handoff.ts and trace how resolveHandoffEndpoints handles the recovery handoff described in the issue. Then inspect the web and mobile handoff rows and the existing behavior requested in #28178. Done means recovery is represented as a fresh session with kept history, without displaying a model-to-itself handoff; issue #39791 already has an open linked pull request.
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/web
Steps to reproduce
With the dev replay agent (Replay (dev)), in the web client:
- Open a thread that has one finished turn.
- Send a second message, for example "Second question", and let the turn finish.
- On that message choose Edit from here, then Revert and keep changes. The message returns to the composer.
- Send it again without changing the model.
Any ACP agent does the same (Antigravity, Grok, Kiro), since none of them can truncate its own conversation. It was first seen on Antigravity with Gemini 4 Neon.
Expected behavior
The timeline says what happened: the provider conversation was restarted in a fresh session and given the kept history. The server already names it that way, since the turn item it writes is titled "Recovered context". No model or provider changed, so the row should not name a source and a target.
#28178 asked for this row so that the thread "shows that the provider conversation couldn't be resumed and a new one was started". docs/user/providers-antigravity.md describes the same event for Edit from here: "the next turn starts a fresh Antigravity session and T3 Code sends it the kept conversation".
Actual behavior
A divider appears above the resent message that reads Context handoff · Multi turn → Multi turn (on Antigravity: Context handoff · 4 Neon → 4 Neon): a handoff from a model to itself.
Root cause: the resume fallback in ProviderTurnStartService writes a handoff turn item whose source and target are the same provider conversation (fromProviderThreadIds is [toProviderThreadId], title "Recovered context"). resolveHandoffEndpoints in packages/client-runtime/src/handoff.ts and the web and mobile rows treat every handoff item alike and draw <from> → <to> under the fixed label "Context handoff", so a recovery reads as a switch that never happened. Since #30188 this path runs on every Edit from here on an ACP agent, not only when a resume fails.
Impact
Cosmetic issue
Version or commit
Nightly v0.1.12-nightly.20261120.4994, and main at 31e31c608d.
Environment
Reproduced with the dev replay agent in the web client (headless Chromium, 1280×800). First seen in the macOS desktop app on an Antigravity thread, Gemini 4 Neon.
Logs or stack traces
Server log for the resent turn on the Antigravity thread:
Recovering provider context in a fresh native session
driver: antigravity
reason: native_session_lacks_kept_turns
errorTag: ProviderAdapterTurnStartError
Screenshots, recordings, or supporting files
After step 4, on main:
Workaround
None needed to keep working: the conversation continues with the kept history. The row cannot be hidden or corrected.
- Lingua principale
- TypeScript
- Stelle
- 24.8k
- Fork
- 6.4k
- Merge medio
- 4h 29m
- PR unite (30g)
- 488
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
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
I maintainer di solito rispondono entro 1 giorno
-
needs more info
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
pingdotgg/t3code#39400 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: Wrapped PR titles lose bottom padding in the thread details panelForse già presa @iamdatvt94 l’ha presa 1 giorno fa. Apertabug needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
bug needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di pingdotgg/t3code
Issue simili
-
area:plugins kind:bug priority:p2 ready
Difficoltà 2/5 1-3 ore Idoneità per principianti 90/100
I maintainer di solito rispondono entro 1 giorno
-
Escaped `*` followed by `*` (`\**`) never matchesForse già presa @bardrop l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 71/100
editorconfig/editorconfig-core-js#172 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
vega/vega-webgpu#40 ·
-
Adjust break point sizingApertatype: bug 🐛
Difficoltà 2/5 1-3 ore Idoneità per principianti 63/100
puckeditor/puck#1929 ·
I maintainer di solito rispondono entro 1 giorno
-
compression() compresses every response at Brotli quality 11Forse già presa @staylor l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno