Typing corrupts streaming edits
Los mantenedores suelen responder en 8 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 22/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
Línea de trabajo
Start in the core tool-call streaming path where edit_existing_file / single_find_and_replace arguments are accumulated and applied, and in the VS Code extension code that writes those edits into the active buffer. Reproduce with a focused file and a distinctive typed phrase to see whether keystrokes land in the streamed arguments or in the applied file content. Done means typing during an active stream never alters generated content or tool-call arguments.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Before submitting your bug report
- I've tried finding an answer on the Continue docs site
- I'm not able to find an open issue that reports the same bug
- I've seen the troubleshooting guide on the Continue Docs
Relevant environment info
- OS: Windows: 11
- Continue version: 2.0.0
- IDE version: {
Version: 1.131.0 (system setup)
Commit: e4c7e7b1d6d060162f4aa7f8225271b67ce1df75
Date: 2026-07-28T10:51:25Z
Electron: 42.7.0
ElectronBuildId: 14710161
Chromium: 148.0.7778.280
Node.js: 24.18.0
V8: 14.8.178.38-electron.0
OS: Windows_NT x64 10.0.26200
}
- Model: Deepseek
- config:
name: Main Config
version: 1.0.0
schema: v1
disableAutocomplete: true
models:
- name: DeepSeek Coder
provider: deepseek
model: deepseek-coder
apiKey:
contextLength: 128000
shell: powershell.exe
OR link to agent in Continue hub:
Description
When a tool call (e.g. edit_existing_file, single_find_and_replace) is still streaming and the target file is open and focused in the editor, keystrokes typed by the user are injected into the content being generated — both into the file written to disk and into the tool-call arguments themselves. This produces stray, out-of-place text fragments that belong to neither the existing file nor the intended edit.
This happens only when the user types during an active streaming tool call; it does not occur when the user is idle. It is distinct from the spontaneous argument corruption (Issue A), which occurs with no user input.
Suspected mechanism: during generation, focus/cursor is placed in the open file buffer, so keyboard input is delivered to that buffer and/or desynchronizes the tool-call stream, causing typed text to land inside generated content.
To reproduce
To reproduce
Open a source file in the editor and focus it.
Ask the agent to modify that file (e.g. "add a comment at the top of this file") — a task that emits an edit tool call.
While the tool call is still streaming, type a short distinctive phrase into the editor (e.g. ZZZTEST123).
Observe: the typed phrase (or fragments of it) appears inside the written file content and/or inside the tool-call arguments, at positions unrelated to where you typed.
Expected: user keystrokes affect only the editor as normal editing and never appear inside agent-generated file content or tool-call arguments.
Actual: typed text bleeds into the generated file content / tool-call arguments, corrupting them.
Confirm scope: repeat the same steps without typing — the contamination does not occur. This isolates the bug from Issue A.
Log output
- Lenguaje dominante
- TypeScript
- Estrellas
- 36.5k
- Forks
- 5.6k
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- 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 continuedev/continue
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
continuedev/continue#13486 ·
Los mantenedores suelen responder en 8 días
-
Chat panel overflows horizontally when VS Code zoom level is increased (Cmd/Ctrl + +)Posiblemente ocupada @tang-ontheway la tomó hace 1 día. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
continuedev/continue#13483 ·
Los mantenedores suelen responder en 8 días
-
Docs: show tool selection for a shared remote MCP endpointPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
continuedev/continue#13464 · 1 comentario ·
Los mantenedores suelen responder en 8 días
-
Inline code becomes unreadable in VS Code high-contrast themesPosiblemente ocupada @aminesayagh la tomó hace 21 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 63/100
continuedev/continue#13424 ·
Los mantenedores suelen responder en 8 días
-
create_new_file writes a JSON file on one line when the model sends its contents as a JSON valuePosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
continuedev/continue#13363 ·
Los mantenedores suelen responder en 8 días
Todos los issues de continuedev/continue
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
oxc-project/tsrs#1010 ·
Los mantenedores suelen responder en 1 día
-
area:infra area:storage bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
THU-MAIC/OpenMAIC#2311 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
docs documentation need-triage SaaS
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
enhancement from-app needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
nightly-labs/openbot#10973 ·
Los mantenedores suelen responder en 1 día
-
status/need-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
google-gemini/gemini-cli#30328 · 1 comentario ·
Los mantenedores suelen responder en 1 día