Bug Description
When initializing a project with noskills init and selecting OpenCode as a coding tool, the generated opencode.json file causes a strict configuration validation error when running opencode.
The generated configuration uses a string for the command field and an array for args (which is a common pattern in other MCP clients like Claude Desktop), and it omits the enabled key. However, opencode's schema strictly expects command to be an array of strings and requires the enabled boolean flag to be present.
Steps to Reproduce
- Run the initialization command in a project directory:
npx eser@latest noskills init
- Follow the interactive prompts and ensure
OpenCode is selected as a coding tool:
┌ noskills init
│
◇ Config: .eser/
◇ Project scanned
◇ go
│
◇ 0 coding tool(s) detected
│
◇ No coding tools detected. Which tools do you use? (space to toggle) · Claude Code, OpenCode, Codex CLI
│
◇ 3 provider(s) detected
│
◇ What kind of project is this? (space to toggle, enter to confirm) · Beautiful Product, Long-Lived, Compliance, Well-Engineered
✓ Concerns: beautiful-product, long-lived, compliance, well-engineered
│
◇ Synced 4 tool(s)
◇ claude-code
◇ opencode
◇ codex
◇ hooks
│
└ Done. 3 tool(s), 3 provider(s), 4 concern(s).
- Check the generated
opencode.json file. It will have command as a string ("npx") and args as an array.
- Run the
opencode command in the terminal.
- Observe the validation error preventing the command from executing.
Expected Behavior
Either noskills should generate the opencode.json file strictly conforming to the current OpenCode schema (using a command array and including "enabled": true), OR opencode should relax its schema to support the command (string) + args (array) format for better compatibility with standard MCP configurations.
Actual Behavior
The opencode command execution halts with the following output:
Configuration is invalid at /Users/ssi/projects/vesta/zenith/opencode.json
↳ Expected array, got "npx" mcp.noskills.command
↳ Missing key mcp.noskills.enabled
Runtime
Node.js
Package Version
@eserstack/noskills latest
Runtime Version
Node 24
Additional Context
No response
Bug Description
When initializing a project with
noskills initand selecting OpenCode as a coding tool, the generatedopencode.jsonfile causes a strict configuration validation error when runningopencode.The generated configuration uses a string for the
commandfield and an array forargs(which is a common pattern in other MCP clients like Claude Desktop), and it omits theenabledkey. However,opencode's schema strictly expectscommandto be an array of strings and requires theenabledboolean flag to be present.Steps to Reproduce
OpenCodeis selected as a coding tool:opencode.jsonfile. It will havecommandas a string ("npx") andargsas an array.opencodecommand in the terminal.Expected Behavior
Either
noskillsshould generate theopencode.jsonfile strictly conforming to the current OpenCode schema (using acommandarray and including"enabled": true), ORopencodeshould relax its schema to support thecommand(string) +args(array) format for better compatibility with standard MCP configurations.Actual Behavior
The
opencodecommand execution halts with the following output:Configuration is invalid at /Users/ssi/projects/vesta/zenith/opencode.json
↳ Expected array, got "npx" mcp.noskills.command
↳ Missing key mcp.noskills.enabled
Runtime
Node.js
Package Version
@eserstack/noskills latest
Runtime Version
Node 24
Additional Context
No response