Skip to content

fix: default to deepseek/deepseek-v4-flash-0731 (drop invalid openrouter/ prefix) - #74

Merged
AbirAbbas merged 1 commit into
mainfrom
fix/default-model-drop-openrouter-prefix
Aug 21, 2026
Merged

fix: default to deepseek/deepseek-v4-flash-0731 (drop invalid openrouter/ prefix)#74
AbirAbbas merged 1 commit into
mainfrom
fix/default-model-drop-openrouter-prefix

Conversation

@AbirAbbas

Copy link
Copy Markdown
Contributor

Problem

The manifest defaults for the harness model (materialized into a node's
environment by the control plane when the user has stored no value) were
openrouter/moonshotai/kimi-k2.5. With the default harness now aforge, the
model id is passed to OpenRouter verbatim, and OpenRouter rejects the
openrouter/ routing prefix:

API error (400): openrouter/moonshotai/kimi-k2.5 is not a valid model ID

Every LLM-backed reasoner then fails with turns=0 / "output file was NOT
created" / schema-parse failures, so an af install-ed node does no real work
(a scan/audit "succeeds" with zero findings and $0 cost).

Reproduced directly against the bundled aforge binary + this repo's key:

model passed result
openrouter/moonshotai/kimi-k2.5 (old default) 400 … not a valid model ID, turns=0
deepseek/deepseek-v4-flash-0731 (new default) ok, turns=1

Fix

Set the default model to the bare, valid OpenRouter slug
deepseek/deepseek-v4-flash-0731 across the manifest (root + go/),
.env.example, compose files, Dockerfile ENV defaults, and docs.

Left unchanged on purpose: opencode-config JSON blocks (opencode consumes/strips
the openrouter/ prefix itself) and test fixtures that set the env explicitly.

🤖 Generated with Claude Code

…ter/ prefix)

The aforge harness passes the model id to OpenRouter verbatim; OpenRouter
rejects 'openrouter/...' as an invalid model ID (400), so every reasoner failed
with turns=0. Use the bare slug the user intends.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@AbirAbbas
AbirAbbas merged commit 48ae7ee into main Aug 21, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant