Skip to content

Comments

fix(chat): don't override chibi's model with invalid openrouter name#47

Merged
terraboops merged 1 commit intomainfrom
fix/chibi-chat-model-only
Feb 22, 2026
Merged

fix(chat): don't override chibi's model with invalid openrouter name#47
terraboops merged 1 commit intomainfrom
fix/chibi-chat-model-only

Conversation

@emesal
Copy link
Owner

@emesal emesal commented Feb 22, 2026

Summary

  • Fixes autonav chat --harness chibi producing no response
  • Root cause: TUI hardcoded model: "claude-sonnet-4-5" which is not a valid OpenRouter model ID (needs anthropic/ prefix), causing chibi-json to fail with HTTP 400 before making any LLM call
  • Fix: only pass DEFAULT_MODEL for non-chibi harnesses; chibi falls back to its own config.toml default
  • Also threads config.harness?.model from nav-chat.ts so navigator config can provide an explicit model override (same pattern as nav-query.ts)

Test plan

  • autonav chat <navigator> --harness chibi — produces a response
  • autonav chat <navigator> (claude-code, default) — still uses claude-sonnet-4-5
  • Navigator with harness.model set in config.json — model override respected

the TUI hardcoded model to "claude-sonnet-4-5" which is not a valid
openrouter model ID (needs "anthropic/" prefix). this caused chibi-json
to fail with a 400 error before making any LLM call — the root cause of
the "no visible response" bug in autonav chat with chibi harness.

fix: only pass DEFAULT_MODEL for non-chibi harnesses. chibi uses its
own config.toml default. navigator config.harness.model is threaded
through as an explicit override when set.
@terraboops terraboops merged commit 408e3bb into main Feb 22, 2026
5 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.

2 participants