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

A conversation begun with only a task disappears while its task runs

Abierto
#1,482 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
68/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
go

Línea de trabajo

Start with internal/tui3/home.go:5242 and internal/tui3/place_sessions.go:550, then inspect internal/session/task_index.go to find when a running task receives its index entry. Use the deterministic blocked-worker reproduction and the named unit and e2e acceptance checks. Done means a first-action task remains visible and reopenable in Home and Sessions until it settles, with the Sessions manual and invalidates updated.

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

Descripción

area:chat area:session bug sev:serious

Seen on dev@debffabf6. Surfaced while verifying #1426; not introduced by it.

What happened

A conversation whose first and only action is /task can vanish from both Home and Sessions after /new moves away, even though its task continues running. It has no title or ordinary user-message row yet, and the project task index receives no entry until the task lands. The running work has no visible route back through either place.

Replication

Deterministic (no model). In a fresh home and temporary Git repository, start a scripted /task whose worker blocks, then invoke /new before it settles. Read Home and Sessions while the worker remains blocked. The conversation is absent from both. Release the worker and observe it appear only after landing.

Field (real models). With OPENROUTER_API_KEY and deepseek/deepseek-v4-flash, start /task as the first action, immediately use /new, and inspect Home and Sessions during a long worker command. Allow several minutes and a few cents.

Where

internal/tui3/home.go:5242 at dev@debffabf6 derives a row name from title and transcript; internal/tui3/place_sessions.go:550, taskSheetOwnRows, relies on the project task index and current-window row. Search internal/session/task_index.go for when a running task first receives an index entry.

The fix

Persist and index a conversation as soon as its task starts, with a placeholder title if necessary, so Home and Sessions can show and reopen it while work is live.

Acceptance

  • e2e: through codeaf chat in tmux, /task followed by /new leaves a visible working row in both Home and Sessions until the task settles.
  • Unit: first-action task admission writes a discoverable index row before landing.
  • Update the Sessions manual and invalidates.
Lenguaje dominante
Go
Estrellas
115
Forks
14
Merge medio
9 h 38 min
PR fusionados (30 d)
730

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

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 Agent-Field/CodeAF

Todos los issues de Agent-Field/CodeAF

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.