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

未关闭
#65,220 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
50/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript
领域
observability

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
TypeScript
星标
227k
派生
30.7k
平均合并
3 小时 57 分钟
30 天内合并 PR
484

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

anomalyco/opencode 的其他 Issue

查看 anomalyco/opencode 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。