anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[FEATURE]: Allow optionally _not_ to display session list on API session delete #3627

New Issue
Closed
opened 2026-02-16 17:40:55 -05:00 by yindo · 4 comments
yindo commented 2026-02-16 17:40:55 -05:00
Owner
Copy Link
Copy Source

Originally created by @Nindaleth on GitHub (Dec 17, 2025).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

I'm experimenting with an "auto-continue" plugin for OpenCode that works when session.idle event is emitted. An LLM judge is used to decide whether the work is finished or the model just stalls, waiting for a token (heh) user input such as "go".

Since the plugin is triggered on every message, I have some simple heuristics in place to make sure the judge isn't started for new or chat-only (tool-less) conversations. But still, I found it clean to start a separate session for each decision and then delete it once the verdict is given. However, deleting a session triggers session list pop-over to appear unconditionally.

This code seems to drive it. I see these options:

  • extend the API to optionally allow not to display the session list
  • reuse the one judge session
  • something different

Would it be viable to do this API extension?

Originally created by @Nindaleth on GitHub (Dec 17, 2025). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request I'm experimenting with an "auto-continue" plugin for OpenCode that works when session.idle event is emitted. An LLM judge is used to decide whether the work is finished or the model just stalls, waiting for a token (heh) user input such as "go". Since the plugin is triggered on every message, I have some simple heuristics in place to make sure the judge isn't started for new or chat-only (tool-less) conversations. But still, I found it clean to start a separate session for each decision and then delete it once the verdict is given. However, deleting a session triggers session list pop-over to appear unconditionally. [This code](https://github.com/sst/opencode/blob/dev/packages/opencode/src/server/server.ts#L783) seems to drive it. I see these options: * extend the API to optionally allow _not_ to display the session list * reuse the one judge session * something different Would it be viable to do this API extension?
yindo added the discussion label 2026-02-16 17:40:55 -05:00
yindo closed this issue 2026-02-16 17:40:55 -05:00
yindo commented 2026-02-16 17:40:55 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Dec 17, 2025):

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

  • #5517: OpenCode API Race Condition in Concurrent Session Deletion - discusses API session deletion behavior and reliability
  • #5466: Session list jumps to active session when confirming delete on non-current session - related to the session list popover display behavior on deletion

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Dec 17, 2025): This issue might be a duplicate of existing issues. Please check: - #5517: OpenCode API Race Condition in Concurrent Session Deletion - discusses API session deletion behavior and reliability - #5466: Session list jumps to active session when confirming delete on non-current session - related to the session list popover display behavior on deletion Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 17:40:56 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 17, 2025):

yeah that feels weird to me too, I msged dax about it

@rekram1-node commented on GitHub (Dec 17, 2025): yeah that feels weird to me too, I msged dax about it
yindo commented 2026-02-16 17:40:56 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 17, 2025):

Fixed in next release, that shouldn't have been happening on api side anyway

@rekram1-node commented on GitHub (Dec 17, 2025): Fixed in next release, that shouldn't have been happening on api side anyway
yindo commented 2026-02-16 17:40:56 -05:00
Author
Owner
Copy Link
Copy Source

@Nindaleth commented on GitHub (Dec 17, 2025):

Thank you for the quick fix @rekram1-node !

For readers from the future, the session list is no longer displayed after API session delete. This has been fixed in 16e6941495, released in v1.0.165

@Nindaleth commented on GitHub (Dec 17, 2025): Thank you for the quick fix @rekram1-node ! For readers from the future, the session list is no longer displayed after API session delete. This has been fixed in 16e69414952ad90be2e8526bac0a519f336005ae, released in v1.0.165
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label discussion
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#3627
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?