romtuck/openclaw
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
92697edb7c
openclaw/docs/experiments/proposals/model-config.md
Jon Shapiro 92697edb7c fix(venice): add compat settings to prevent HTTP 400 errors 
Venice's API doesn't support certain OpenAI-compatible parameters that
Clawdbot sends by default:

- `store`: Venice returns HTTP 400 with no body when this is present
- `developer` role: Not supported by Venice's API

This adds VENICE_COMPAT settings (supportsStore: false,
supportsDeveloperRole: false) to all Venice model definitions, both
from the static catalog and dynamically discovered models.

Fixes issues reported in PR #1666 where users experienced silent
failures (HTTP 400, no body) when using Venice models.

Co-authored-by: jonisjongithub <jonisjongithub@users.noreply.github.com>
Co-authored-by: Clawdbot <bot@clawd.bot>
2026-01-26 17:56:01 -08:00

1.1 KiB
Raw Blame History

summary read_when
Exploration: model config, auth profiles, and fallback behavior
Exploring future model selection + auth profile ideas

Model Config (Exploration)

This document captures ideas for future model configuration. It is not a shipping spec. For current behavior, see:

Motivation

Operators want:

  • Multiple auth profiles per provider (personal vs work).
  • Simple /model selection with predictable fallbacks.
  • Clear separation between text models and image-capable models.

Possible direction (high level)

  • Keep model selection simple: provider/model with optional aliases.
  • Let providers have multiple auth profiles, with an explicit order.
  • Use a global fallback list so all sessions fail over consistently.
  • Only override image routing when explicitly configured.

Open questions

  • Should profile rotation be per-provider or per-model?
  • How should the UI surface profile selection for a session?
  • What is the safest migration path from legacy config keys?