Agent reads: measure the smaller default page and the many-reads note on the benchmark

Abierto
  • ¿Algo no está bien?
#324 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
developer-experience

Línea de trabajo

Start with src/main/tools/files.ts and the existing shownReads behavior described in the issue. Measure reads per task and input tokens on the agent benchmarks in #49 and #135, including how often the model responds to the note with reread: true. Use those results to decide whether to implement the smaller default page or the soft warning; done means the chosen change is measured and edits still work if the default page changes.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

performance priority: low severity: low

Follow-up to #314, whose first point is done: a repeated read_file of the same lines of an unchanged file in one run now returns a one-line note instead of the text (shownReads in src/main/tools/files.ts, reset when a run starts).

Left from #314's proposal:

  1. Smaller default page. read_file returns up to 2,000 lines (30,000 characters) by default. A smaller default with the total line count in the result could stop whole-file reads of large files when the agent needs one function. Check that edits still work, since edit_file and write_file need the file read first (any page marks it read).
  2. A soft warning after many reads in one turn, for example a note appended to the tool result after N reads without an edit, suggesting grep or find_definition.
  3. Measure. Reads per task and input tokens before and after, on the agent benchmark (#49, #135), including how often the model answers the new note with reread: true.

Measure first (3): if the note already removes most of the cost, 1 and 2 may not be worth it.

Lenguaje dominante
TypeScript
Estrellas
2
Forks
2
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.