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

[Bug]: Agents panel opens at the oldest subagent on every thread switch, never the newest

Cerrado Apto para principiantes
  • ¿Algo no está bien?
#22,414 0 comentarios 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
66/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
react, typescript
Área
frontend

Línea de trabajo

Empieza por apps/web/src/components/AgentsPanel.tsx e inspecciona cómo se monta ScrollArea cuando cambian los hilos o las pestañas. Consulta packages/client-runtime/src/state/subagentRuntime.ts para confirmar el orden de la lista. Implementa el comportamiento acordado para la posición inicial, de modo que un panel Agents recién abierto muestre el agente más reciente. Después, verifícalo con un hilo que contenga muchos subagents y captura las capturas de pantalla del antes y el después, tal como exige CONTRIBUTING.md.

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

Descripción

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
  1. Open a thread that has spawned many subagents. 20+ makes it obvious; I routinely have tens per thread.
  2. Open the right panel's Agents tab. The roster renders oldest-first, so the newest agent is at the very bottom.
  3. Scroll to the bottom to see the agent that is actually running.
  4. Switch to another thread and switch back. The same thing happens when switching the right panel to Files and back, or hiding and showing the right panel.
  5. Look at the Agents roster.
Expected behavior

Opening the Agents panel should land on the newest subagent, at the bottom of the list, because that is the one doing work right now. The oldest agent in a 30-agent roster finished twenty minutes ago and is the least useful thing to show.

A per-thread restored position would be an acceptable alternative for threads I have already visited, but a thread opened for the first time should still start at the newest agent rather than the oldest.

Actual behavior

The roster always mounts at the top, showing the oldest subagent. Every thread switch costs a manual scroll to the bottom to find the live agent. With tens of agents per thread this is constant friction.

Two things combine to produce it on current main:

  • The roster is sorted oldest-first. packages/client-runtime/src/state/subagentRuntime.ts:853 sorts directAgents by ascending firstSeenAt; workflow members sort by phase index then agentIndex (same file, lines 784-824). The newest agent is always last.
  • The panel has no scroll handling at all. apps/web/src/components/AgentsPanel.tsx:548 renders a bare ScrollArea with no initial offset, no bottom anchoring, and no restoration across remounts, so it mounts at scrollTop: 0 every time.
Impact

Minor bug or occasional failure

Version or commit

main @ e67abcf798f8

Environment

macOS

Logs or stack traces
Workaround

Scroll to the bottom of the Agents panel by hand after every thread switch.

Prior art, please read before marking this a duplicate

Three PRs have attempted the neighbouring problem, all closed unmerged:

  • #9637 and #14512 were closed for incomplete UI verification, specifically a missing before capture.
  • #14525 was closed as part of the orchestrator V2 transition (#2829), with the explicit note: "We're closing the current implementation without assuming the underlying request is resolved." That closure also said V2 removed AgentsPanel.tsx; the file is present on current main, so whatever V2 did, the panel is back and still has no scroll handling.

All three solved scroll preservation, restoring the offset you last had on that thread. This issue is a different ask: land on the newest agent, including on a thread opened for the first time, where there is no saved offset to restore. The two could ship together, but preservation alone would not fix this.

Related but distinct: #8759 (right tabs should persist state and scroll position, generic, filed against the diff tab), #11571 (diff tab loses scroll position on thread switch), #17751 (Agents panel horizontal overflow, different axis).

Happy to contribute

I'm glad to pick this up and open the PR if a maintainer confirms the direction, in particular whether you want plain bottom-anchoring on mount or bottom-anchoring plus per-thread position restore. Given that two of the three prior PRs died on verification evidence rather than on the code, I'd rather agree the behavior first and then come with before/after captures that match CONTRIBUTING.md.

Lenguaje dominante
TypeScript
Estrellas
24.8k
Forks
6.4k
Merge medio
1 h 22 min
PR fusionados (30 d)
18

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.