3
43
Fork
You've already forked opencode.el
16

Prompt responses not being received #27

Closed
opened 2026年02月19日 01:58:59 +01:00 by bashtobits · 7 comments

Hello, so I tried this exciting package to integrate in my existing emacs (doom/vanilla emacs) but it seems I don't get any response after I send any prompt. The response/chat is updated if I refresh the session by either closing emacs or re-opening the session. For some reason opencode CLI also doesn't receive the response unless I refresh the session there also.

This appears to be related to the SSE (Server-Sent Events) event stream not receiving session-specific events.

Is anyone else also facing this issue?

Environment

  • opencode.el version: Latest from Codeberg (main branch)
  • OpenCode server version: 1.2.6
  • Emacs version: 30.2
  • Operating Systems tested: Linux, macOS (both affected)
  • Installation method: bun install -g opencode

Let me know if anything else is needed to debug this issue.

Thanks.

Hello, so I tried this exciting package to integrate in my existing emacs (**doom/vanilla emacs**) but it seems I don't get any response after I send any prompt. The response/chat is updated if I refresh the session by either **closing** emacs or **re-opening** the session. For some reason **opencode CLI** also doesn't receive the response unless I refresh the session there also. This appears to be related to the SSE (Server-Sent Events) event stream not receiving session-specific events. Is anyone else also facing this issue? Environment - opencode.el version: Latest from Codeberg (main branch) - OpenCode server version: 1.2.6 - Emacs version: 30.2 - Operating Systems tested: Linux, macOS (both affected) - Installation method: bun install -g opencode Let me know if anything else is needed to debug this issue. Thanks.

Same issue here - I need to reopen the session - Same Emacs version, lastest opencode.el - Linux.

But I must say it seems to happen for "simple" responses , that don't involve tools like 'write'
(if I ask for a Python script, I can see the 'write' tool being invoked to write the code to the disk, but I don't see the rest of the conversation)

I'm wondering if this could be related to #25... (I'm using opencode 1.2.6 also)

Same issue here - I need to reopen the session - Same Emacs version, lastest opencode.el - Linux. But I must say it seems to happen for "simple" responses , that don't involve tools like 'write' (if I ask for a Python script, I can see the 'write' tool being invoked to write the code to the disk, but I don't see the rest of the conversation) I'm wondering if this could be related to https://codeberg.org/sczi/opencode.el/pulls/25... (I'm using opencode 1.2.6 also)
Owner
Copy link

yea I think it is related to #25, I'll review and merge it tonight

yea I think it is related to #25, I'll review and merge it tonight
Owner
Copy link

should be fixed now after a788d81

should be fixed now after a788d81

@sczi wrote in #27 (comment):

should be fixed now after a788d81

new sessions work, but opening any existing session doesn't, not sure if this is my specific issue.

@sczi wrote in https://codeberg.org/sczi/opencode.el/issues/27#issuecomment-10924325: > should be fixed now after [`a788d81`](/sczi/opencode.el/commit/a788d81) new sessions work, but opening any existing session doesn't, not sure if this is my specific issue.
Owner
Copy link

opening existing sessions is working for me. do you get an error or what happens?

opening existing sessions is working for me. do you get an error or what happens?

@sczi wrote in #27 (comment):

opening existing sessions is working for me. do you get an error or what happens?

I think it's more related to opencode's db migration, most sessions are working, thanks.

@sczi wrote in https://codeberg.org/sczi/opencode.el/issues/27#issuecomment-10936787: > opening existing sessions is working for me. do you get an error or what happens? I think it's more related to opencode's db migration, most sessions are working, thanks.
Owner
Copy link

I use opencode in a temporary sandbox as described in the security section of the readme. So I don't end up testing it myself on old session formats. We've had issues before with support of older sessions: #2
It's a bug I'd like to fix, if you're still having issues opening some sessions, can you toggle-debug-on-error and open a new issue with the full error backtrace?

I use opencode in a temporary sandbox as described in the security section of the readme. So I don't end up testing it myself on old session formats. We've had issues before with support of older sessions: #2 It's a bug I'd like to fix, if you're still having issues opening some sessions, can you `toggle-debug-on-error` and open a new issue with the full error backtrace?
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sczi/opencode.el#27
Reference in a new issue
sczi/opencode.el
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?