Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Bug]: Mobile shows a mid-turn progress note below "Worked for …", next to the final answer

Abierto Apto para principiantes
  • ¿Algo no está bien?
#15,380 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
76/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
mobile-dev

Línea de trabajo

Empieza en apps/mobile/src/lib/threadActivity.ts, en deriveThreadFeedRunFolds, y compara después el comportamiento de mobile con el cambio de web de #8828. Reproduce el orden de las filas prompt → Worked for → nota de progreso → respuesta final y usa la prueba de regresión descrita en el issue; se considera terminado cuando mobile y web pliegan el thread asentado de forma consistente.

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

Descripción

bug via-triage
Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/mobile

Steps to reproduce
  1. On the mobile app, ask an agent for something that makes it run a tool, write a short progress note, run more tools, then reply.
  2. Wait for the run to settle.
Expected behavior

The same as web since #8828: prompt → Worked for … → final answer, with the progress note inside the fold.

Actual behavior

Mobile shows prompt → Worked for … → progress note → final answer. The note sits under the fold as if it came after all the work, and reads as the first paragraph of the final answer, while most of the work happened between the two.

Cause: deriveThreadFeedRunFolds in apps/mobile/src/lib/threadActivity.ts still exempts the run's first assistant message from the fold (the rule #7723 added for both clients). #8828 removed that rule from web only, so web and mobile now fold the same thread differently.

Impact

Minor, but misleading: on the phone the order of what the agent did and said is misrepresented in every settled run that starts with a tool call and narrates once.

Version or commit

main at 00eb8f6183.

Environment

Android phone app connected to a Windows desktop server, Claude provider.

Workaround

Expand the fold.

Note: the open draft #14698 proposes the opposite direction for both clients (keep every assistant message visible). I'd argue for keeping the fold: a settled turn that reads prompt → Worked for → answer is much easier to scan than a transcript with every interim note in it. Anything an interim note says that matters belongs in the final message, and that is the agent's job to restate there. Either way, web and mobile should agree. I have a two-file fix ready that ports #8828 to mobile, with a test that reproduces the row order above (red on main, green with the fix), and can open it if this direction is the one you want.

Lenguaje dominante
TypeScript
Estrellas
24.8k
Forks
6.4k
Merge medio
13 h 9 min
PR fusionados (30 d)
271

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

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.

Más de pingdotgg/t3code

Todos los issues de pingdotgg/t3code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.