Skip to content

Comments

fix: respect chibi's configured default model#45

Merged
emesal merged 3 commits intomainfrom
fix/chibi-model-default
Feb 21, 2026
Merged

fix: respect chibi's configured default model#45
emesal merged 3 commits intomainfrom
fix/chibi-model-default

Conversation

@emesal
Copy link
Owner

@emesal emesal commented Feb 21, 2026

Summary

  • buildInput in chibi-harness.ts never passed model to chibi-json, so AgentConfig.model was silently ignored for all chibi invocations
  • Now passes config: { model } per chibi's JSON protocol when a model is explicitly set
  • When no model is specified, config is omitted entirely so chibi falls back to the user's ~/.chibi/config.toml default
  • Updated NavigatorAdapterOptions.model JSDoc to accurately describe the per-harness default behaviour

Test plan

  • autonav query my-nav "question" --harness chibi with no model override — chibi uses its configured default
  • autonav query my-nav "question" --harness chibi with model set in nav's config.json — that model is forwarded to chibi

Previously buildInput never passed a model to chibi-json, so any model
set via AgentConfig (including the hardcoded adapter default) was silently
ignored. Now model flows through via config.model per chibi's protocol,
and when no model is specified chibi falls back to the user's config.toml
default rather than receiving an override.
@emesal emesal force-pushed the fix/chibi-model-default branch from 54f0c05 to f06fd02 Compare February 21, 2026 20:20
@emesal emesal merged commit 24ee387 into main Feb 21, 2026
5 checks passed
@emesal emesal deleted the fix/chibi-model-default branch February 21, 2026 20:28
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