[Feature] Autosave model configuration changes

[Y1fe1Zh0u]

Pre-checks

• I have searched existing issues and this is not a duplicate.

What problem does this solve?

Model configuration changes are easy to forget to save manually.

When users configure model providers, default models, model routing, fallback models, or related model settings, they may assume the selection has already taken effect after changing a dropdown, toggle, or input. If the page requires an additional Save click, the configuration can be lost or remain inconsistent with what the user just selected.

This causes confusion because model configuration is often changed during setup/debugging, where users frequently move between pages to test behavior.

Proposed solution

Support autosave or immediate persistence for model configuration changes.

Expected behavior:

• Persist simple model configuration changes immediately after selection, or autosave them with a short debounce.
• Show per-section save state so users know whether the latest configuration is active.
• Keep explicit Save/Apply controls only where batching is necessary, and clearly mark unsaved changes in those cases.
• Prevent partial updates from creating ambiguous state when multiple fields are related.
• Provide a clear error and retry path when a model configuration save fails.

Suggested acceptance criteria:

• Changing a default model or model provider setting persists without relying on a remembered Save click.
• Returning to the configuration page shows the latest selected values.
• Failed saves are visible and do not make the UI look successfully saved.
• Related settings are applied atomically or clearly staged together.

Willing to contribute?

• I'd be interested in working on this.