Post

Remote GTM Manager
@remotegtmmanager.com

OpenCode Not Working, stopped my CLI and my Desktop app in the exact same second — two completely separate apps, different installers, different version numbers, both dead at once, zero warning. The cause was one file. The fix was one line. Full thread below 🧵

0 reposts0 likes

Remote GTM Manager
@remotegtmmanager.com

I'd added five custom subagents to #OpenCode, copied straight from a different AI coding tool I already use daily. Same surface shape: Markdown, YAML frontmatter, a tools: field. Looked identical. Wasn't. Closed my terminal, reopened it minutes later — nothing. Instant refusal, every attempt.

Remote GTM Manager
@remotegtmmanager.com

Opened OpenCode Desktop next, assuming the terminal was glitching. Same failure — a genuinely separate app, its own installer, its own version number. Two apps, same instant, same failure. The CLI's error was excellent though: exact file, exact field, exactly what it expected vs. what it got.

Remote GTM Manager
@remotegtmmanager.com

Desktop's own log told me almost nothing — a bare "ConfigInvalidError," repeated five times, no file or field named. This is the real shape of OpenCode Not Working: both apps share one config folder and one local server at startup. Break the config anywhere, both go down.

Remote GTM Manager
@remotegtmmanager.com

The actual bug - tools: written as a YAML list, when OpenCode's schema wants a map instead — tool name to boolean. Both are valid YAML on their own, just different shapes. All five files I'd added carried the identical mistake, not a stray typo, a whole batch copied wrong from the wrong source.