anomalyco / anomalyco/opencode
opencode doesn't work well in ubuntu 26.04 at vscode terminal
@kommander is already working on this.
Since Aug 9, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- Avg merge
- 7h 2m
- Merged PRs (30d)
- 384
Description
Description
When I use VS Code, neither its built-in terminal nor the terminal popped up by the extension "opencode" can properly open the slash‑type command pop‑up (i.e., the autocomplete/suggestion window triggered by typing a slash). There is no response. However, the default terminal in the Ubuntu system works fine.
Plugins
No response
OpenCode version
1.18.15
Steps to reproduce
Step 1 – Verify the normal environment (system terminal)
Open the default Ubuntu terminal (e.g., GNOME Terminal).
Ensure the shell used is the same as the one in VS Code (typically bash or zsh).
Type /skill and press Enter.
Observe whether a skill list (interactive menu or completion pop‑up) appears immediately. Record this normal behavior as your baseline.
Step 2 – Test in the VS Code built‑in terminal
Launch VS Code and open any project or an empty workspace.
Press Ctrl+` to open the built‑in terminal.
At the prompt, type /skill and press Enter.
Observe the result:
Does any dropdown menu, completion list, or selection prompt appear?
Does the cursor remain, or does the command line clear or execute something else?
If no skill list appears and the terminal only echoes /skill or shows a “command not found” message, then the issue is reproduced in this terminal.
Step 3 – Test in the opencode extension’s terminal
Make sure the opencode extension is installed and enabled.
Open its separate terminal window via the extension’s entry point (e.g., sidebar icon or Command Palette command “OpenCode: Open Terminal”).
Again type /skill and press Enter.
Check whether the behavior matches the VS Code built‑in terminal (no list appears). If it does, the issue is reproduced in that terminal as well.
Screenshot and/or share link
Operating System
ubuntu 26.04
Terminal
vscode terinal
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.