Observability: in-process session.interrupt leaves no log/reason (interrupted turns unattributable), and Session.* typed errors stringify to empty message
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 50/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
调研方向
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 内容生成。
描述
Description
Two observability gaps made a recurring outcome:"interrupted" incident forensically opaque for days (OpenCode v2.3.0, plugin API v2):
- In-process plugin interrupts leave no trace. A plugin calling the host API
context.session.interrupt({sessionID})produces the usualsession.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
reasonis 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.
- Session.* typed errors stringify to
"". Errors built as EffectData.Errorsubclasses without amessagegetter (e.g.Session.SyntheticConflictError {sessionID,inputID},Session.NotFoundError {sessionID}) haveerr.message === "". Plugin/client code loggingerror.messageemits empty strings — e.g. a third-party plugin loggedwake suppressed after SDK error {"error":""}for weeks with no way to identify the rejection. (Contrast:Session.StepFailedError/AgentNotFoundErrordo defineget message().)
Expected behavior
- Log the interrupt API entry point at INFO with sessionID + reason + origin (http vs in-process/plugin), and persist
reasonon the idle record (or expose it onSession.Info), so post-mortems can attribute aninterruptedturn without live instrumentation. (The enum already exists —"user"|"shutdown"|"superseded"|"inactivity"— it just never reaches storage.) - Give the typed error classes a
messagegetter 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 soerror.messageis never empty.
Reproduction
- From a v2 plugin:
await ctx.session.interrupt({sessionID})while the session runs — inspectopencode.log(INFO) and the persisted idle message: no log line, no reason. - From a plugin, admit a
session.syntheticwith 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
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
anomalyco/opencode 的其他 Issue
-
[Site] Active section detection should respect scroll-margin-top可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭area/web reproduced type/bug
难度 2/5 1-3 小时 新手友好度 65/100
anomalyco/opencode#65384 · 1 条评论 ·
维护者通常 1 天内回复
-
area/cli type/feature version/v2
难度 2/5 1-3 小时 新手友好度 68/100
anomalyco/opencode#65379 · 1 条评论 ·
维护者通常 1 天内回复
-
Shell tool: no upper bound on the timeout a model can ask for, so one call can hold a turn for hours未关闭area/core platform/linux type/feature version/v2
难度 2/5 1-3 小时 新手友好度 75/100
anomalyco/opencode#65254 · 1 条评论 ·
维护者通常 1 天内回复
-
inference/go type/feature
难度 1/5 1-3 小时 新手友好度 72/100
anomalyco/opencode#65148 · 1 条评论 ·
维护者通常 1 天内回复
-
area/providers type/feature version/v2
难度 2/5 1-3 小时 新手友好度 68/100
anomalyco/opencode#64845 · 1 条评论 ·
维护者通常 1 天内回复
查看 anomalyco/opencode 的全部 Issue
相似的 Issue
-
[Provider] antigravity-acp catalog omits gemini-4-hydrogen and gemini-4-neon that agy acp offers可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭catalog provider provider-compatibility
难度 2/5 1-3 小时 新手友好度 62/100
lidge-jun/opencodex#9037 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 62/100
slavakurilyak/awesome-ai-agents#1005 ·
-
kind/bug triage/unresolved
难度 2/5 1-3 小时 新手友好度 60/100
维护者通常 1 天内回复
-
effort:S P3 refactor
难度 2/5 1-3 小时 新手友好度 72/100
nightscout/nocturne#3735 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
wpilibsuite/systemcore-blocks-interface#641 ·
维护者通常 2 天内回复