92697edb7c
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>
33 lines
1.1 KiB
Markdown
33 lines
1.1 KiB
Markdown
---
|
|
summary: "Exploration: model config, auth profiles, and fallback behavior"
|
|
read_when:
|
|
- 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:
|
|
- [Models](/concepts/models)
|
|
- [Model failover](/concepts/model-failover)
|
|
- [OAuth + profiles](/concepts/oauth)
|
|
|
|
## 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?
|