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

Aperta
#65,220 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
50/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
observability

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
TypeScript
Stelle
227k
Fork
30.7k
Merge medio
3h 57m
PR unite (30g)
484

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di anomalyco/opencode

Tutte le issue di anomalyco/opencode

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.