opencode-backed seats get a bare model id the agent does not advertise

Open
#76 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
shell
Domain
backend

Research direction

Start with invoke-acpx.sh, where MODEL is resolved, and inspect how select-panel.py --agents assigns models. The report says registry model_id must remain bare for refresh matching and DeepSeek proxy routing, while an opencode agent needs an advertised provider-prefixed id. Add a regression test that a seat given glm-5.3-flash launches with opencode-go/glm-5.3-flash.

Written by the indexing model from the issue text.

Description

The deepseek seat in the tight preset fails every run: the selector hands it a bare registry model_id, and the opencode-backed agent only accepts provider-prefixed ids.

[acpx] error: RUNTIME Cannot apply --model "glm-5.3-flash": the ACP agent did not advertise that model.
Available models: ... opencode-go/glm-5.3, opencode-go/glm-5.3-flash, ... opencode/glm-5.3-flash-free, ...

Seen 2026-10-29 on /debate:run tight in STRML/autodream: select-panel.py assigned deepseek -> glm-5.3-flash (glm53flash, provider zai, no transport), and the seat exited 1, so the panel ran 3 of 4 seats.

Rewriting model_id in ~/.claude/debate-models.json is not the fix. refresh-models.py matches registry entries by model_id, so a prefixed id would stop matching Artificial Analysis rows and the next refresh would add a duplicate. The DeepSeek entries carry transport: proxy and route through the cc-ds4 proxy, where the bare id is correct.

What would fix it, one of:

Option Where
Translate at dispatch: for an opencode-backed agent, map a bare id to the advertised one (<provider prefix>/<id>), preferring the opencode-go/ route invoke-acpx.sh, where MODEL is resolved
Teach the selector which ids an agent advertises, and only assign those select-panel.py --agents feasibility

A regression test: a seat on an opencode agent, given glm-5.3-flash, launches with opencode-go/glm-5.3-flash.

Dominant language
Shell
Stars
10
Forks
4
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from STRML/cc-debate

All issues in STRML/cc-debate

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.