sdk方法中 sessions.abort方法不能终止后台服务的任务的运行

[ZYT20001]

Description

我提出问题 session的状态是busy通过sessions.status 然后我用abort方法 session的状态还是busy直到答案生成完成

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• OpenCode version is missing — please provide the version you are using
• Steps to reproduce is empty — please describe how to reproduce the issue (e.g., the SDK code you used to call sessions.abort)
• Operating System and Terminal are missing — please provide your system information

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

---

This issue might be a duplicate of existing issues. Please check:

• abort session with OpenAI(Responses API) models throwing error. #5660: Abort session with OpenAI Responses API models — also involves abort not working as expected

If you believe this was flagged incorrectly, please let a maintainer know.

[ZYT20001]

sdk 1.2.15 opencode 1.2.15 Windows

export async function ABORT(req: Request) {
  try {
    const {sessionId} = await req.json();

    if (sessionId) {
      await opencodeService.abort(sessionId);
      return new Response(JSON.stringify({success: true}), {
        status: 200,
        headers: {"Content-Type": "application/json"}
      });
    }
    return new Response(JSON.stringify({error: "SessionId required"}), {status: 400});
  } catch (error) {
    console.error("Abort Error:", error);
    return new Response(JSON.stringify({error: "Internal Abort Error"}), {status: 500});
  }
}

[ZYT20001]

现在我两个都升级到了1.2.22 但是还是abort失败

[github-actions]

This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

Feel free to open a new issue that follows our issue templates.

[eengad]

Confirming this on current versions with a reproducible case.

Environment

• OpenCode 1.2.22
• OpenChamber 1.8.5
• Ubuntu 24.04.4 LTS
• Linux 6.8.0-101-generic aarch64

Repro

Run this in a session:

bash -lc 'trap "echo INTERRUPTED; exit 130" INT TERM; echo START; while true; do sleep 1; done'

Then trigger Stop/Abort from the frontend.

Expected

• the running shell command is interrupted promptly
• the session becomes usable again

Actual

• the command keeps running
• the session remains blocked/unusable
• the session only recovers after the command exits on its own or is killed externally

In my case the frontend is OpenChamber, but it appears to call OpenCode's session.abort API for stop/abort actions, so this still looks like an OpenCode-side interrupt/abort problem.

If helpful, I can provide diagnostics or a short screen recording. If you'd prefer this tracked separately, I can open a new issue with the same repro and environment details.