Skip to content

Config: should store model properties (modalities, context length) separately from which models are main / fallback #1127

@Aaronontheweb

Description

@Aaronontheweb
 "Models": {
    "Main": {
      "Provider": "spark-362c",
      "ModelId": "Qwen/Qwen3.6-35B-A3B-FP8",
      "Provenance": "Live"
    },
    "Fallback": {
      "Provider": "spark-362c",
      "ModelId": "Qwen/Qwen3.6-35B-A3B-FP8",
      "Provenance": "Live"
    }
  },

Currently, due to #987, I have to edit these fields to specify the modalities in order to enable image support. Changing my active model can wipe those hand-edited values out.

A better model here would be to:

  1. Store model information in Models
  2. Store Main / Fallback are pointers to specific records (provider/model)

Metadata

Metadata

Assignees

No one assigned

    Labels

    configConfiguration issues, netclaw doctor, schema validation.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions