Felix Faerber
c8efc17729
ci / lint (pull_request) Successful in 17s
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.
70 lines
4.7 KiB
Bash
Executable File
70 lines
4.7 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
# Install opencode + provider config (+ Playwright MCP for browser agents).
|
|
#
|
|
# Required env (provided by the workflow step): OLLAMA_URL OLLAMA_CLOUD_API_KEY XAI_API_KEY
|
|
# NAME SKILLS GITHUB_PATH HOME
|
|
set -eu
|
|
|
|
# PIN the opencode version: an unpinned `latest` means a breaking release (CLI flags, or the
|
|
# --format json event schema that build-activity-log.sh parses) breaks every agent in every repo
|
|
# at once. Bump deliberately by changing this default (or set OPENCODE_VERSION in the step env).
|
|
OPENCODE_VERSION="${OPENCODE_VERSION:-1.17.13}"
|
|
# Skip the download when a cache hit already restored the pinned binary (see the Cache
|
|
# opencode CLI step in agent.yml). The installer always re-fetches otherwise.
|
|
OC_BIN="$HOME/.opencode/bin/opencode"
|
|
if [ -x "$OC_BIN" ] && "$OC_BIN" --version 2>/dev/null | grep -qF "$OPENCODE_VERSION"; then
|
|
echo "opencode $OPENCODE_VERSION already present (cache hit) — skipping install"
|
|
else
|
|
curl -fsSL https://opencode.ai/install | bash -s -- --version "$OPENCODE_VERSION"
|
|
fi
|
|
echo "$HOME/.opencode/bin" >> "$GITHUB_PATH"
|
|
mkdir -p ~/.config/opencode
|
|
# Playwright browser MCP only for agents that need to drive a web app
|
|
MCP='{}'
|
|
case "$NAME" in
|
|
senior|lead|qa)
|
|
echo "Enabling Playwright MCP for @$NAME"
|
|
MCP='{"playwright":{"type":"local","command":["npx","-y","@playwright/mcp@latest","--headless"],"enabled":true}}'
|
|
npx -y playwright install --with-deps chromium || npx -y playwright install chromium || true
|
|
;;
|
|
esac
|
|
# Per-agent skill scoping. Skills are loaded on-demand by opencode: only a skill's one-line
|
|
# `description` ever appears in an agent's <available_skills> list, and the full SKILL.md body
|
|
# (curl/API how-to) is loaded ONLY when the agent calls the `skill` tool — it is never in any
|
|
# system prompt. To also hide the summary from agents that shouldn't use a skill, we deny all
|
|
# skills by default and allow only the ones in this agent's registry list (passed via $SKILLS).
|
|
# A denied skill is hidden entirely (name + description omitted), so e.g. @junior never sees
|
|
# gitea-api at all; it just knows from the roster that @senior/@lead can, and asks them.
|
|
SKILLS="${SKILLS:-[]}"
|
|
PERM=$(jq -nc --argjson s "$SKILLS" '
|
|
{skill: ( {"*":"deny"} + (reduce $s[] as $k ({}; . + {($k):"allow"})) )}')
|
|
# Three OpenAI-compatible providers: local self-hosted ollama (ornith) + Ollama Cloud
|
|
# (gemma4/kimi-k2.7-code/glm-5.2/minimax-m3) + xAI (grok-4.5). The provider `models:` maps are
|
|
# DERIVED from agents.json (the single source of truth, shared with route.sh) so every model an
|
|
# agent is routed to is always declared in the provider config. `ollama-cloud/` prefix models go to
|
|
# the cloud provider; `ollama/` prefix models go to the local provider; `xai-oc/` prefix models go
|
|
# to our xAI shim (OpenAI-compatible, https://api.x.ai/v1). No other built-in providers remain.
|
|
#
|
|
# The provider key is `xai-oc`, NOT `xai` — opencode ships a built-in `xai` entry in its own model
|
|
# catalog (a real @ai-sdk/xai integration that implements the Responses API). Naming our custom
|
|
# openai-compatible shim `xai` collides with that catalog entry: opencode's --auto permission-check
|
|
# path then assumes the catalog's provider (which has `.responses()`) and crashes with
|
|
# "Z.responses is not a function" on every run once a `permission` block is present (i.e. always in
|
|
# this pipeline). Confirmed by reproducing locally with the production config shape on opencode
|
|
# 1.17.13 — renaming the key to `xai-oc` avoids the collision entirely. See issue #118.
|
|
# See issue #31.
|
|
AGENTS_JSON="${SCRIPTS:-$(dirname -- "$0")}/agents.json"
|
|
CLOUD_MODELS=$(jq -r '[.[] | .model | select(startswith("ollama-cloud/")) | sub("^ollama-cloud/";"")] | map({(.):{}}) | add // {}' "$AGENTS_JSON")
|
|
LOCAL_MODELS=$(jq -r '[.[] | .model | select(startswith("ollama/")) | sub("^ollama/";"")] | map({(.):{}}) | add // {"ornith:35b":{}}' "$AGENTS_JSON")
|
|
XAI_MODELS=$(jq -r '[.[] | .model | select(startswith("xai-oc/")) | sub("^xai-oc/";"")] | map({(.):{}}) | add // {}' "$AGENTS_JSON")
|
|
jq -n --argjson mcp "$MCP" --argjson perm "$PERM" --argjson cloud "$CLOUD_MODELS" --argjson local "$LOCAL_MODELS" --argjson xai "$XAI_MODELS" --arg url "$OLLAMA_URL" --arg ckey "$OLLAMA_CLOUD_API_KEY" --arg xkey "$XAI_API_KEY" '{
|
|
provider: {
|
|
ollama: {npm:"@ai-sdk/openai-compatible", options:{baseURL:($url+"/v1")}, models:$local},
|
|
"ollama-cloud": {npm:"@ai-sdk/openai-compatible", options:{baseURL:"https://ollama.com/v1", apiKey:$ckey}, models:$cloud},
|
|
"xai-oc": {npm:"@ai-sdk/openai-compatible", options:{baseURL:"https://api.x.ai/v1", apiKey:$xkey}, models:$xai}
|
|
},
|
|
permission: $perm,
|
|
mcp: $mcp
|
|
}' > ~/.config/opencode/opencode.json
|
|
echo "opencode config (secrets masked):"; cat ~/.config/opencode/opencode.json
|