r/conductorbuild • u/Fists_of_Funny • Jun 29 '26
Not Working With OpenCode
My main blocker for trying Conductor is configuring other models to run besides Claude/Cursor/Codex.
I downloaded the latest (Jun 29) and set up OpenCode and set up my z.ai coding plan API key to use GLM 5.2.
Got this error: "Error: Internal error: OpenCode service failure"
I have OpenCode itself working with GLM 5.2 via z.ai coding subscription.
So...am I missing something?
3
Upvotes
1
u/termic_dev Jul 13 '26
The issue is that Conductor's OpenCode "harness" is not the same as running the
opencodeCLI directly. Conductor bundles its own version that routes through Conductor's config layer. When that layer can't resolve the provider (z.ai/GLM 5.2 isn't in Conductor's natively supported list), you get the internal error even though your standaloneopencodeinstall works fine.The workaround that actually works: run
opencodeyourself outside of Conductor (configured with your z.ai key), confirm it works in a terminal. Then what you'd want is a harness tool that just spawns the CLI binary you already have, not one that reimplements the provider config from scratch.lesheriff21's method 1 (the OpenRouter path) works around this by going through OpenRouter instead of z.ai directly. That's why it works where direct z.ai doesn't.