Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte
  • Quelque chose ne va pas ?
#1,482 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
68/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
go
Domaine
cli, documentation, testing

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.
Langage dominant
Go
Étoiles
115
Forks
14
Merge moyen
12 h 24 min
PR mergées (30 j)
310

Préparer son environnement

Nous n'avons pas encore vérifié les fichiers d'installation de ce projet. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de Agent-Field/CodeAF

Toutes les issues de Agent-Field/CodeAF

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.