Observability: in-process session.interrupt leaves no log/reason (interrupted turns unattributable), and Session.* typed errors stringify to empty message

Abierto
#65,220 2 comentarios 0 reacciones 0 asignados Ver en GitHub

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
50/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript

Línea de trabajo

Start from the plugin host API implementation of context.session.interrupt and trace where session.execution.interrupted is emitted and where the idle record {type:"idle",outcome:"interrupted"} is persisted — that is where the reason is dropped and where an INFO log belongs, next to the HTTP route. For part two, find the Session.SyntheticConflictError and Session.NotFoundError definitions (compare with Session.StepFailedError, which already has get message()). Done looks like: an INFO line carrying sessionID, reason and origin, a persisted reason on the idle record, non-empty message getters, plus tests covering both paths.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area/plugins platform/windows type/feature version/v2
Description

Two observability gaps made a recurring outcome:"interrupted" incident forensically opaque for days (OpenCode v2.3.0, plugin API v2):

  1. In-process plugin interrupts leave no trace. A plugin calling the host API context.session.interrupt({sessionID}) produces the usual session.execution.interrupted → idle record {"type":"idle","outcome":"interrupted"}, but:
    • nothing is logged at INFO (the HTTP route would at least appear in the access log; the in-process call does not),
    • the interrupt reason is not persisted on the idle record, and only "user" is ever producible via the interrupt API, so a plugin-initiated, client-initiated, and UI-stop interrupt are indistinguishable after the fact. We chased a phantom "UI/stop-button" hypothesis for hours; the real emitter was an in-proc plugin refusal (reported to that plugin separately). Related: #64013, #63632.
  2. Session.* typed errors stringify to "". Errors built as Effect Data.Error subclasses without a message getter (e.g. Session.SyntheticConflictError {sessionID,inputID}, Session.NotFoundError {sessionID}) have err.message === "". Plugin/client code logging error.message emits empty strings — e.g. a third-party plugin logged wake suppressed after SDK error {"error":""} for weeks with no way to identify the rejection. (Contrast: Session.StepFailedError/AgentNotFoundError do define get message().)
Expected behavior
  1. Log the interrupt API entry point at INFO with sessionID + reason + origin (http vs in-process/plugin), and persist reason on the idle record (or expose it on Session.Info), so post-mortems can attribute an interrupted turn without live instrumentation. (The enum already exists — "user"|"shutdown"|"superseded"|"inactivity" — it just never reaches storage.)
  2. Give the typed error classes a message getter rendering their fields (e.g. Session.SyntheticConflictError: synthetic input ID <inputID> conflicts for session <sessionID>), or normalize them at the plugin/API boundary before rejection so error.message is never empty.
Reproduction
  1. From a v2 plugin: await ctx.session.interrupt({sessionID}) while the session runs — inspect opencode.log (INFO) and the persisted idle message: no log line, no reason.
  2. From a plugin, admit a session.synthetic with an id that already exists for another session and catch: err instanceof Error && err.message === "".
Environment

OpenCode v2.3.0 (server bundled in OpenChamber Electron 2.7.2 resources), Windows 11; observed across many sessions 2026-11-14 → 2026-11-20.

Lenguaje dominante
TypeScript
Estrellas
227k
Forks
30.7k
Merge medio
3 h 57 min
PR fusionados (30 d)
484

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de anomalyco/opencode

Todos los issues de anomalyco/opencode

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.