[BUG]: plugin-recorded compaction result renders an unlabeled compaction row in the TUI

Offen
#65,251 2 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
58/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
typescript
Bereich
cli

Rechercherichtung

Start by locating the TUI transcript renderer for the compaction divider and tracing where it subscribes to session.compaction.delta. Compare that path with the plugin-result path, where session.compaction.ended carries text and the durable compaction message carries summary; the row must read from one of those when no deltas arrive. Reproduce with the minimal plugin plus /compact, then confirm the row shows a label and the recorded summary while omitting tokens/cost when absent.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

area/tui platform/linux type/bug version/v2
Description

Description

When a compaction hook returns result — the documented way for a plugin to supply the
compaction itself and skip the summarizer call — the compaction divider is drawn in the TUI
transcript, but the row is empty: no label, no summary content, no usage. A standard
(summarizer-run) compaction renders a labeled row with the streamed summary.

The text that belongs in the row is not lost: it is recorded in the durable compaction
message (summary) and delivered on session.compaction.ended (text). It simply never
renders. The row appears to source its content only from the session.compaction.delta
stream — the result path emits no deltas at all, and ended.text is ignored, so the row
stays bare.

Captured live on v2.2.7 by recording /api/event on a second server around the same
/compact:

plugin returns result standard compaction
session.compaction.started emitted emitted
session.compaction.delta none ~84 (the streamed summary)
session.compaction.ended reason, model, text = recorded summary; no tokens/cost reason, model, text, tokens, cost
durable compaction message summary, reason, model, status; no cost/tokens same, plus cost/tokens

Expected: the row renders like a standard one — label plus the recorded summary (from
ended.text / the durable summary) — and simply omits usage stats when tokens/cost
are absent. Core already holds everything needed; only the presentation is missing.

Related

  • #62360 — TUI plugin slot for the compaction row (complementary: a slot would let plugins
    fill the row, but core should label plugin-recorded compactions by default).
  • #50862 — compaction hook can only return a summary string; #63365 — auto/manual reason
    for plugin-triggered compaction. Adjacent; neither covers the unlabeled row.
Plugins

The minimal local plugin below (first noticed with my own compaction plugin; the minimal plugin reproduces on its own).

OpenCode version

v2.2.7

Steps to reproduce
  1. A local plugin that records the compaction result instead of letting the summarizer run:

    // minimal-compaction-result/index.ts  (package.json exports "." to this file)
    import { Plugin } from "@opencode/plugin";
    
    export default Plugin.define({
      id: "minimal-compaction-result",
      async setup(ctx) {
        await ctx.session.hook("compaction", async (event) => {
          event.result = {
            summary: "# Recorded compaction summary\n\nThis summary was recorded by a plugin.",
          };
        });
      },
    });
    
    // opencode.jsonc
    { "plugins": [{ "package": "./minimal-compaction-result" }] }
    
  2. Open a TUI session in that project, send a short prompt, run /compact.

  3. The compaction divider renders with no label and no content.

  4. Remove the plugin, /compact again: the row is labeled and shows the summary content.

Screenshot

No response

Operating System

Linux Mint 22.3 (Cinnamon)

Terminal

GNOME Terminal

Vorherrschende Sprache
TypeScript
Sterne
227k
Forks
30.7k
Ø Merge
3 Std. 57 Min.
Gemergte PRs (30 T.)
484

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus anomalyco/opencode

Alle Issues in anomalyco/opencode

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.