Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
  • 何か問題がありますか？
#1,565 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
65/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
go
領域
cli, frontend

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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

主要言語
Go
スター
115
フォーク
14
平均マージ
9時間 35分
マージ済み PR（30日）
752

環境構築

このプロジェクトの環境構築ファイルはまだ確認していません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Agent-Field/CodeAF のほかの issue

Agent-Field/CodeAF の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。