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

[FEATURE]:Official - OpenCode VS Code extension #7976

New Issue
Open
opened 2026-02-16 18:08:49 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 18:08:49 -05:00
Owner
Copy Link
Copy Source

Originally created by @c2b247 on GitHub (Jan 29, 2026).

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

Summary

I’d like OpenCode to be available as an official Visual Studio Code extension, so it can run as a native panel/side view within VS Code instead of only as a standalone terminal UI.

Problem

Right now, the typical way to use OpenCode is through a terminal. This works, but it has a few practical limitations for developers who live inside VS Code:

  • Switching back and forth between the terminal and the editor breaks flow.
  • The TUI doesn’t behave like a first‑class VS Code panel (e.g. resizing, layout persistence, focus, keyboard shortcuts).
  • It’s harder to integrate OpenCode workflows with other VS Code features (source control, problems view, outline, etc).

For those of us using OpenCode as a central coding agent, having it only in the terminal makes the experience feel more like a separate tool than a tightly integrated part of the IDE.

Proposal

Create an official Opensource OpenCode VS Code extension that:

  • Renders OpenCode in a dedicated view/panel (e.g. a sidebar or main panel) instead of just a terminal.
  • Uses VS Code’s Webview / custom view / panel APIs (or similar) so:
    • The OpenCode interface can be docked, resized, and positioned like other panels.
    • Layout is remembered between sessions.
    • Focus, keybindings, and navigation feel native to VS Code.

Possible features for the extension

  • Integrated agent panel: A persistent OpenCode panel where the agent UI lives, rather than a transient terminal.
  • Project‑aware context: Automatically picks up the current workspace, repo, and open files, using VS Code APIs instead of shell heuristics.
  • Commands & keybindings:
    • “Open OpenCode panel” command.
    • Quick commands to send the current file/selection to OpenCode.
    • Customizable hotkeys for common agent actions.
  • Status bar integration: Simple status indicator (e.g. agent running, thinking, idle, error).
  • Configuration UI: VS Code settings page for OpenCode config, keys, backends, etc., instead of editing config only via files/CLI.

Benefits

  • Better UX inside VS Code: OpenCode feels like a first‑class citizen, similar to other popular AI/code tools that ship as VS Code extensions.
  • Less context switching: Developers can keep OpenCode visible alongside editor, terminal, and source control.
  • More discoverable and approachable: Installing from the VS Code marketplace greatly lowers the barrier to trying OpenCode for new users.
  • Easier integration with other tools: Extension can hook into VS Code’s APIs to provide richer workflows (e.g. running specific tasks, opening files suggested by the agent, etc.).

Additional Context

My main use case is running OpenCode as a primary coding agent while staying entirely inside VS Code. Having an official extension that opens properly in a VS Code pane (instead of just a terminal window) would make OpenCode much easier to adopt and use as a daily driver for development.

Originally created by @c2b247 on GitHub (Jan 29, 2026). 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 ## Summary I’d like **OpenCode to be available as an official Visual Studio Code extension**, so it can run as a native panel/side view within VS Code instead of only as a standalone terminal UI. ## Problem Right now, the typical way to use OpenCode is through a terminal. This works, but it has a few practical limitations for developers who live inside VS Code: - Switching back and forth between the terminal and the editor breaks flow. - The TUI doesn’t behave like a first‑class VS Code panel (e.g. resizing, layout persistence, focus, keyboard shortcuts). - It’s harder to integrate OpenCode workflows with other VS Code features (source control, problems view, outline, etc). For those of us using OpenCode as a central coding agent, having it only in the terminal makes the experience feel more like a separate tool than a tightly integrated part of the IDE. ## Proposal Create an **official Opensource OpenCode VS Code extension** that: - Renders OpenCode in a **dedicated view/panel** (e.g. a sidebar or main panel) instead of just a terminal. - Uses VS Code’s **Webview / custom view / panel APIs** (or similar) so: - The OpenCode interface can be docked, resized, and positioned like other panels. - Layout is remembered between sessions. - Focus, keybindings, and navigation feel native to VS Code. ### Possible features for the extension - **Integrated agent panel**: A persistent OpenCode panel where the agent UI lives, rather than a transient terminal. - **Project‑aware context**: Automatically picks up the current workspace, repo, and open files, using VS Code APIs instead of shell heuristics. - **Commands & keybindings**: - “Open OpenCode panel” command. - Quick commands to send the current file/selection to OpenCode. - Customizable hotkeys for common agent actions. - **Status bar integration**: Simple status indicator (e.g. agent running, thinking, idle, error). - **Configuration UI**: VS Code settings page for OpenCode config, keys, backends, etc., instead of editing config only via files/CLI. ## Benefits - **Better UX inside VS Code**: OpenCode feels like a first‑class citizen, similar to other popular AI/code tools that ship as VS Code extensions. - **Less context switching**: Developers can keep OpenCode visible alongside editor, terminal, and source control. - **More discoverable and approachable**: Installing from the VS Code marketplace greatly lowers the barrier to trying OpenCode for new users. - **Easier integration with other tools**: Extension can hook into VS Code’s APIs to provide richer workflows (e.g. running specific tasks, opening files suggested by the agent, etc.). ## Additional Context My main use case is running OpenCode as a **primary coding agent** while staying entirely inside VS Code. Having an official extension that opens properly in a VS Code pane (instead of just a terminal window) would make OpenCode much easier to adopt and use as a daily driver for development.
yindo added the discussion label 2026-02-16 18:08:49 -05:00
yindo commented 2026-02-16 18:08:49 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 29, 2026):

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

  • #9960: vscode extension of opencode
  • #8794: When will the official OpenCode plugins for IntelliJ IDEA, PyCharm, and VS Code be released?
  • #7275: cleaner and more aware extensions integration with vscode
  • #216: Editor integrations

Additionally, related feature requests that address IDE integration challenges:

  • #9578: IDE-native Diff Review & Accept/Reject Workflow for Code Changes Made by opencode
  • #8003: VS Code Integration for Reviewing OpenCode Code Changes (Diff Preview)

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

@github-actions[bot] commented on GitHub (Jan 29, 2026): This issue might be a duplicate of existing issues. Please check: - #9960: vscode extension of opencode - #8794: When will the official OpenCode plugins for IntelliJ IDEA, PyCharm, and VS Code be released? - #7275: cleaner and more aware extensions integration with vscode - #216: Editor integrations Additionally, related feature requests that address IDE integration challenges: - #9578: IDE-native Diff Review & Accept/Reject Workflow for Code Changes Made by opencode - #8003: VS Code Integration for Reviewing OpenCode Code Changes (Diff Preview) Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 18:08:49 -05:00
Author
Owner
Copy Link
Copy Source

@altendky commented on GitHub (Jan 30, 2026):

https://marketplace.visualstudio.com/items?itemName=sst-dev.opencode
https://marketplace.visualstudio.com/items?itemName=sst-dev.opencode-v2

i think these are official extensions. though yes, plenty of room for improvement. i started https://github.com/anomalyco/opencode/issues/7275 but haven't gotten any traction here yet with even just the bug fixes i made along the way. they are busy here... 1.2k PRs and all.

@altendky commented on GitHub (Jan 30, 2026): https://marketplace.visualstudio.com/items?itemName=sst-dev.opencode https://marketplace.visualstudio.com/items?itemName=sst-dev.opencode-v2 i think these are official extensions. though yes, plenty of room for improvement. i started https://github.com/anomalyco/opencode/issues/7275 but haven't gotten any traction here yet with even just the bug fixes i made along the way. they are _busy_ here... 1.2k PRs and all.
yindo commented 2026-02-16 18:08:49 -05:00
Author
Owner
Copy Link
Copy Source

@Pl8tinium commented on GitHub (Jan 30, 2026):

this is a great proposal

@Pl8tinium commented on GitHub (Jan 30, 2026): this is a great proposal
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#7976
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?