launch-*: default tier go + glm-5.3-flash (zen model ids dead on this host) #20

2026-09-14T14:20:30Z

autonomic-bot commented

2026-09-14 14:20:30 +00:00

What

Hardcode the OpenCode Go tier + opencode-go/glm-5.3-flash as the defaults in launch-upgrader.py, launch-report.py, launch-supervisor.py (was: ZEN opencode/glm-5.2). ZEN stays an explicit LOOP_TIER=zen opt-in for a host that has a key.

Why

The host holds no ZEN key and the ZEN model ids (opencode/glm-5.2) vanished from the provider catalogue (2026-09-14) — every launch that bypassed the systemd EnvironmentFile died instantly with ProviderModelNotFoundError. That is what killed the 2026-09-11 report agent at launch and all manual retries; timer-driven runs were unaffected (upgrader.env already sets LOOP_TIER=go).

Evidence

env -i bare invocation now resolves tier=go, model=opencode-go/glm-5.3-flash on all three launchers.
The missing weekly report is published: https://report.ci.commoninternet.net/week-2026-09-11.html (HTTP 200, produced by a fresh glm-5.3-flash report run) with index regenerated.

## What Hardcode the OpenCode **Go** tier + `opencode-go/glm-5.3-flash` as the defaults in `launch-upgrader.py`, `launch-report.py`, `launch-supervisor.py` (was: ZEN `opencode/glm-5.2`). ZEN stays an explicit `LOOP_TIER=zen` opt-in for a host that has a key. ## Why The host holds no ZEN key and the ZEN model ids (`opencode/glm-5.2`) vanished from the provider catalogue (2026-09-14) — every launch that bypassed the systemd `EnvironmentFile` died instantly with `ProviderModelNotFoundError`. That is what killed the 2026-09-11 report agent at launch and all manual retries; timer-driven runs were unaffected (upgrader.env already sets `LOOP_TIER=go`). ## Evidence - `env -i` bare invocation now resolves tier=go, model=`opencode-go/glm-5.3-flash` on all three launchers. - The missing weekly report is published: https://report.ci.commoninternet.net/week-2026-09-11.html (HTTP 200, produced by a fresh glm-5.3-flash report run) with index regenerated.

autonomic-bot added 1 commit 2026-09-14 14:20:30 +00:00

launch-*: hardcode the default tier to go + glm-5.3-flash (zen model ids are dead on this host) ed6e70928f

Every manual launch of launch-report/launch-upgrader bypasses the systemd EnvironmentFile (/srv/cc-ci/upgrader.env sets LOOP_TIER=go + the go models) and fell back to hardcoded zen defaults, which die instantly here (ProviderModelNotFoundError: opencode/glm-5.2 — the host holds no ZEN key and zen models vanished from the provider catalogue, 2026-09-14). This crashed the 2026-09-11 report agent at launch and again on every manual retry.

- launch-upgrader.py + launch-report.py: default TIER go, go-tier model default glm-5.3-flash (mirrors the 2026-09-08 operator choice in upgrader.env); zen stays an explicit opt-in on a host with a key.
- launch-supervisor.py: default SUPERVISOR_MODEL glm-5.3-flash.
- docstrings updated to match.

Verified with env -i: bare invocation resolves tier=go, model=opencode-go/glm-5.3-flash on all three. The 2026-09-11 weekly report is published live (report.ci.commoninternet.net/week-2026-09-11.html) after a fresh glm-5.3-flash report run.

autonomic-bot merged commit 4454fe49ef into main

2026-09-14 14:20:35 +00:00

autonomic-bot referenced this pull request

2026-09-14 14:20:56 +00:00

memory: zen-tier dead on this host; go+glm-5.3-flash defaults documented #21

autonomic-bot referenced this issue from a commit

2026-09-14 14:20:58 +00:00

memory: weekly upgrader — go tier + glm-5.3-flash defaults, ZEN dead on this host (PR #20 context)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: recipe-maintainers/cc-ci-orchestrator#20