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

[FEATURE]: VSCode extension can connect to any opencodes running in CWD #9042

New Issue
Closed
opened 2026-02-16 18:11:30 -05:00 by yindo · 2 comments
yindo commented 2026-02-16 18:11:30 -05:00
Owner
Copy Link
Copy Source

Originally created by @l3aro on GitHub (Feb 11, 2026).

Originally assigned to: @adamdotdevin 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

Currently, this extension cannot detect an existing opencode instance running in the same current working directory. It keeps spawning a new opencode instance alongside the text editor, even though I already have one running in tmux.
Inspired by https://github.com/nickjvandyke/opencode.nvim/

Originally created by @l3aro on GitHub (Feb 11, 2026). Originally assigned to: @adamdotdevin 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 Currently, this extension cannot detect an existing opencode instance running in the same current working directory. It keeps spawning a new opencode instance alongside the text editor, even though I already have one running in tmux. Inspired by https://github.com/nickjvandyke/opencode.nvim/
yindo added the discussionweb labels 2026-02-16 18:11:30 -05:00
yindo closed this issue 2026-02-16 18:11:30 -05:00
yindo commented 2026-02-16 18:11:30 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Feb 11, 2026):

This issue might be a duplicate of an existing feature request. Please check:

  • #8948: Server Registry & Auto-Discovery for Persistent Sessions

That issue proposes a comprehensive solution for exactly this problem—automatically detecting and connecting to existing opencode servers in the same working directory instead of spawning new instances. The VSCode extension would benefit from this implementation.

@github-actions[bot] commented on GitHub (Feb 11, 2026): --- This issue might be a duplicate of an existing feature request. Please check: - #8948: Server Registry & Auto-Discovery for Persistent Sessions That issue proposes a comprehensive solution for exactly this problem—automatically detecting and connecting to existing opencode servers in the same working directory instead of spawning new instances. The VSCode extension would benefit from this implementation.
yindo commented 2026-02-16 18:11:30 -05:00
Author
Owner
Copy Link
Copy Source

@l3aro commented on GitHub (Feb 11, 2026):

This issue might be a duplicate of an existing feature request. Please check:

That issue proposes a comprehensive solution for exactly this problem—automatically detecting and connecting to existing opencode servers in the same working directory instead of spawning new instances. The VSCode extension would benefit from this implementation.

I disagree that this is a duplicate. opencode is designed to spawn new instances by default. our concern here is strictly with the VS Code extension's behavior, which should be addressed independently of the server registry proposed in #8948.

@l3aro commented on GitHub (Feb 11, 2026): > This issue might be a duplicate of an existing feature request. Please check: > > * [[FEATURE]: Server Registry & Auto-Discovery for Persistent Sessions #8948](https://github.com/anomalyco/opencode/issues/8948): Server Registry & Auto-Discovery for Persistent Sessions > > That issue proposes a comprehensive solution for exactly this problem—automatically detecting and connecting to existing opencode servers in the same working directory instead of spawning new instances. The VSCode extension would benefit from this implementation. I disagree that this is a duplicate. opencode is designed to spawn new instances by default. our concern here is strictly with the VS Code extension's behavior, which should be addressed independently of the server registry proposed in #8948.
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 web
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#9042
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?