Every @lead/@ops run has been crashing (Z.responses is not a function) since the xAI migration. Root cause: opencode has a built-inxai provider in its own model catalog, and our custom OpenAI-compatible shim was also named xai — the collision makes opencode's --auto permission-check path call .responses() on the wrong provider object once a permission block exists (always, here).
Reproduced locally with the exact production opencode.json shape on opencode 1.17.13: 100% failure with provider key xai, 100% success after renaming to xai-oc. This PR renames the provider key + model ids (xai/grok-4.5 → xai-oc/grok-4.5) throughout install-opencode.sh, agents.json, and README.md.
Fixes #118.
Every `@lead`/`@ops` run has been crashing (`Z.responses is not a function`) since the xAI migration. Root cause: opencode has a *built-in* `xai` provider in its own model catalog, and our custom OpenAI-compatible shim was also named `xai` — the collision makes opencode's `--auto` permission-check path call `.responses()` on the wrong provider object once a `permission` block exists (always, here).
Reproduced locally with the exact production `opencode.json` shape on opencode 1.17.13: 100% failure with provider key `xai`, 100% success after renaming to `xai-oc`. This PR renames the provider key + model ids (`xai/grok-4.5` → `xai-oc/grok-4.5`) throughout `install-opencode.sh`, `agents.json`, and `README.md`.
opencode ships a built-in `xai` model-catalog entry (a real @ai-sdk/xai
integration with Responses-API support). Naming our custom OpenAI-compatible
shim `xai` too made opencode's --auto permission-check path assume the
catalog's provider object once a `permission` block is present (always, in
this pipeline) and call .responses(), which our shim doesn't implement —
crashing every @lead/@ops run with "Z.responses is not a function".
Reproduced locally with the production config shape on opencode 1.17.13;
renaming the provider key to xai-oc (model id xai-oc/grok-4.5) fixes it
reliably across repeated fresh-state runs.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes #118.
Every
@lead/@opsrun has been crashing (Z.responses is not a function) since the xAI migration. Root cause: opencode has a built-inxaiprovider in its own model catalog, and our custom OpenAI-compatible shim was also namedxai— the collision makes opencode's--autopermission-check path call.responses()on the wrong provider object once apermissionblock exists (always, here).Reproduced locally with the exact production
opencode.jsonshape on opencode 1.17.13: 100% failure with provider keyxai, 100% success after renaming toxai-oc. This PR renames the provider key + model ids (xai/grok-4.5→xai-oc/grok-4.5) throughoutinstall-opencode.sh,agents.json, andREADME.md.