anomalyco / anomalyco/opencode
[FEATURE]: Desktop Environment panel — skills, plugins, MCPs, loaded instructions + per-session context cost
@Hona is already working on this.
Since Sep 10, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Problem
As an OpenCode Desktop user, I cannot see what is loaded into my sessions without reading opencode.json or asking the model (and hoping the answer is accurate). That breaks the Desktop promise: config-file spelunking for something the app already knows.
My own setup as a concrete example: 12 custom skills, 4 MCP servers (41 tools: codebase-memory 14, playwright 24, context7 2, grep.app 1), 4 plugins, ~12 KB of global instructions across 9 files. I only discovered half of this was actually loading by digging through opencode debug config and the server log — e.g. my skills lived in a directory OpenCode never reads, and nothing in the UI hinted at it.
What already exists / is in flight (not asking for that again)
- TUI
/skillsdialog; Web/Desktop parity tracked in #26297. - Desktop MCP setup + connection testing: #40335 → PR #43719.
- Plugins/LSP GUI + visible load failures: #41037.
- TUI skills in status/sidebar: #7533 / #6154.
What's missing: one read-only "Environment" view for Desktop
- Skills — available (with source path) vs loaded in this session. Today: invisible unless you run
opencode debug skill. - Plugins — loaded / failed + the error inline. Today: failures are log-only (
background dependency install failedcost me a week of sluggish sessions before I found it in a 51 MB log). - Instructions actually injected — resolved list (global
AGENTS.md+instructions[]+ project overrides) with byte sizes. Today: no way to confirm which files won. - Per-session context cost breakdown — how much each of the above contributes per turn. Update: the bot pointed me to #6152, #41908 and #34900, which already cover this angle — conceding point 4 to those. This issue is now scoped to the inventory side (points 1–3), which none of them requests: what is loaded, from where, and whether it failed.
Proposing read-only v1 (a panel/tab next to the existing Server view). Editing/management can ride on #43719-style flows later. Happy to test early builds against a skill/MCP-heavy setup like mine.
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.