[BUG]: plugin-recorded compaction result renders an unlabeled compaction row in the TUI
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 58/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
- Área
- cli
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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
-
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" }] } -
Open a TUI session in that project, send a short prompt, run
/compact. -
The compaction divider renders with no label and no content.
-
Remove the plugin,
/compactagain: the row is labeled and shows the summary content.
Screenshot
No response
Operating System
Linux Mint 22.3 (Cinnamon)
Terminal
GNOME Terminal
- Lenguaje dominante
- TypeScript
- Estrellas
- 227k
- Forks
- 30.7k
- Merge medio
- 3 h 57 min
- PR fusionados (30 d)
- 484
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de anomalyco/opencode
-
[Site] Active section detection should respect scroll-margin-topPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertoarea/web reproduced type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
anomalyco/opencode#65384 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area/cli type/feature version/v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
anomalyco/opencode#65379 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Shell tool: no upper bound on the timeout a model can ask for, so one call can hold a turn for hoursAbiertoarea/core platform/linux type/feature version/v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
anomalyco/opencode#65254 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
inference/go type/feature
Dificultad 1/5 1-3 horas Aptitud para principiantes 72/100
anomalyco/opencode#65148 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area/providers type/feature version/v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
anomalyco/opencode#64845 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de anomalyco/opencode
Issues similares
-
[Provider] antigravity-acp catalog omits gemini-4-hydrogen and gemini-4-neon that agy acp offersPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertocatalog provider provider-compatibility
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
lidge-jun/opencodex#9037 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
Project submission: xmcp DocsAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 62/100
slavakurilyak/awesome-ai-agents#1005 ·
-
kind/bug triage/unresolved
Dificultad 2/5 1-3 horas Aptitud para principiantes 60/100
Los mantenedores suelen responder en 1 día
-
effort:S P3 refactor
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
nightscout/nocturne#3735 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
wpilibsuite/systemcore-blocks-interface#641 ·
Los mantenedores suelen responder en 2 días