Workspace search index: post-turn rescans still walk large non-git project roots for 15 minutes after a search
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
Línea de trabajo
Start with RunFinalizationService.refresh, WorkspaceEntries.refresh, and WorkspaceSearchIndex.refresh in apps/server, then trace how finder.scanFilesAsync() and watchAsync interact with WORKSPACE_INDEX_IDLE_TTL and WORKSPACE_INDEX_SCAN_TIMEOUT. Reproduce with a large non-git project and observe scans after searches and completed turns. Done means post-turn refreshes avoid repeated overlapping full scans while keeping the index updated.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
[!NOTE]
Written by Claude Opus 5.5 (Claude Code) on behalf of the account owner. Numbers are from one Windows install; the code references are from the bundled server of0.1.11-nightly.20261119.4941.
Before submitting
- I searched existing issues and did not find a duplicate of the remaining disk activity.
- I included enough detail to investigate the problem.
Area
apps/server (workspace search index)
Steps to reproduce
- Open a large non-git folder as a project on Windows.
- Search for a file from the composer, then run multiple agent threads in that project.
- Observe filesystem activity after turns finish, during the 15 minutes following the search.
What happens
After a file search in a project, every finished turn in that project triggers a full rescan of the whole project folder for the next 15 minutes:
RunFinalizationService.refreshcallsworkspaceEntries.refresh(cwd)after each run.WorkspaceEntries.refreshcallsWorkspaceSearchIndex.refresh(), which callsfinder.scanFilesAsync(), whenever an index exists for that cwd and was searched withinWORKSPACE_INDEX_IDLE_TTL(15 minutes).
For a project whose root is a large folder that is not a git repository (so no .gitignore applies), each scan walks hundreds of thousands of files. The scan hits WORKSPACE_INDEX_SCAN_TIMEOUT (15 s), so the index stays incomplete, and the next turn starts another full scan. With many agent threads in one project, the rescans overlap.
What we measured on Windows 11 (32 cores, NVMe), with about 50 agent sessions:
- A file search from the composer at 00:07 (about 30
projects.searchEntriesrequests in 30 s, several at 15.5 s). - At 00:10 the server process was doing 25,642 file-system operations a second, by our walker probe.
- From 00:10 to 00:25, every new process on the machine took 1.4-3.4 s to start, against 0.03-0.1 s normally. Short-lived hook processes (Claude Code hooks with a 10 s limit) timed out, and agents' tool calls were refused.
- Back to normal by 00:30, about 15 minutes after the last search.
Expected behavior
One of these, any of which would avoid repeated full walks:
- Update an existing index from the file watcher (
watchAsyncis already set up) instead ofscanFilesAsync()after each turn. - Or, after a turn, rescan at most once per interval per index, and never while a scan is running.
- Or skip post-turn refreshes for an index whose last scan did not complete (timed out).
A setting to turn post-turn index refresh off would also help.
Impact
Major degradation or frequent failure.
Related reports
Issue #22586 reported the same rescan trigger and server event-loop blocking. PR #35460 moved the calls off the event loop; PR #38585 stops refreshes after the index has been unused for 15 minutes. This report concerns the remaining filesystem load during that 15-minute window on the newer release.
Version or commit
0.1.11-nightly.20261119.4941.
Environment
- T3 Code (Nightly)
0.1.11-nightly.20261119.4941, desktop app with the bundled server, Windows 11 Pro. - Project root: a non-git folder with several hundred thousand files, most of them in nested folders with their own data.
- Lenguaje dominante
- TypeScript
- Estrellas
- 24.8k
- Forks
- 6.4k
- Merge medio
- 4 h 29 min
- PR fusionados (30 d)
- 488
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
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
needs more info
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
pingdotgg/t3code#39400 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
[Bug]: Wrapped PR titles lose bottom padding in the thread details panelPosiblemente ocupada @iamdatvt94 la tomó hace 1 día. Abiertobug needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
bug needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
Los mantenedores suelen responder en 1 día
Todos los issues de pingdotgg/t3code
Issues similares
-
area:plugins kind:bug priority:p2 ready
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
Los mantenedores suelen responder en 1 día
-
Escaped `*` followed by `*` (`\**`) never matchesPosiblemente ocupada @bardrop la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 71/100
editorconfig/editorconfig-core-js#172 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
vega/vega-webgpu#40 ·
-
Adjust break point sizingAbiertotype: bug 🐛
Dificultad 2/5 1-3 horas Aptitud para principiantes 63/100
puckeditor/puck#1929 ·
Los mantenedores suelen responder en 1 día
-
compression() compresses every response at Brotli quality 11Posiblemente ocupada @staylor la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día