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

tui3: trailing task and done events in turn demote settled assistant answer to raw plain workingProse

Fermée
  • Quelque chose ne va pas ?
#1,565 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
65/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
go
Domaine
cli, frontend

Piste de recherche

Read deriveWorkfolds and workEntry in internal/tui3/workfold.go, then trace assistantRows in internal/tui3/render.go, focusing on entryDone and entryTask near turn boundaries. Confirm the fix preserves intermediate rolling summaries while ensuring the terminal assistant entry reaches settledMarkdown and retains markdown rendering when asynchronous events follow it.

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

Description

area:chat bug sev:serious
Problem

In the TUI chat surface (internal/tui3), settled final assistant answers frequently fail to convert into rendered markdown answers, staying trapped as unformatted plain text with raw markdown syntax (###, **bold**, backticks) indented as step narration under previous disclosure nodes instead of standing as clean rolling answers.

This is especially prominent in manager and team turns, but also occurs in standard chats whenever background tasks, worker notifications, or tool events land near the turn boundary.

Root Cause Analysis in Code

  1. workEntry in internal/tui3/workfold.go (lines 525–533):
    When classifying whether an assistant entry e is working narration (demoted = true) or a settled answer, workEntry falls through to a forward scan:

    for at := i + 1; at < len(es) && es[at].turn == e.turn; at++ {
    if groupBreaks(&es[at]) {
        return false
    }
    ...
    if es[at].kind != entryDivider && es[at].kind != entryNote && !entryWithdrawn(&es[at]) {
        return true
    }
}

    When background task completions (entryDone, e.g. ✖ ◆ manager permissions · incomplete · 34s) or task status entries (entryTask) append to the current turn after the assistant finishes speaking, workEntry treats them as subsequent non-divider/non-note work and sets es[i].demoted = true.

  2. assistantRows in internal/tui3/render.go (lines 1372–1385):

    if e.demoted {
    e.feet = nil
    text := e.text
    if e.capHead && e.capCut > 0 && e.capCut <= len(text) {
        text = text[e.capCut:]
    }
    return append(tags, a.workingProse(text, width)...)
}
if e.settled {
    return append(tags, a.settledMarkdown(at, e, width)...)
}

    Because e.demoted was set to true, the assistant block never enters settledMarkdown. It routes to workingProse, which performs raw plain-text line-wrapping with zero markdown formatting.

  3. Missing workfold certification in deriveWorkfolds (workfold.go:264–316):
    In manager turns or turns where blocked triggers (such as team_send, entrySeam, or asks), no workfold is constructed for the turn (folds map has no entry for the turn). Without a certifying f.answer == i in a workfold, the forward loop in workEntry runs and is tripped by entryDone / entryTask.

Expected Behavior
  • When nothing is clicked in the transcript, intermediate steps collapse into clean rolling summary lines (▸ headline ... duration), and the assistant's terminal answer renders below them through settledMarkdown with full markdown formatting.
  • Asynchronous task completion cards (entryDone), notifications, and background events appended to the turn must not demote the assistant's final response into intermediate working prose.

Drafted with CodeAF

Langage dominant
Go
Étoiles
115
Forks
14
Merge moyen
9 h 44 min
PR mergées (30 j)
775

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.