Summary

In /agents, editing Primary model (default) or Fallbacks for the default/main agent does not mark config dirty, so Save never enables.

Steps to reproduce

1. Start with config that has agents.defaults but no agents.list (only implicit main agent).
2. Open Control UI at /agents.
3. Select the default/main agent.
4. In Overview, change "Primary model (default)" and/or edit "Fallbacks (comma-separated)".
5. Observe Save button state in the panel.

Expected behavior

Changing model/fallback fields should set config dirty and enable Save so the updated defaults can be persisted.

Actual behavior

Save remains disabled. Changes in those controls are not persisted from /agents. (Config tab editing works as a workaround.)

OpenClaw version

2026.2.17

Operating system

Linux (WSL2: 6.6.87.2-microsoft-standard-WSL2, x64)

Install method

npm global install

Logs, screenshots, and evidence

Observed in local run with runtime agent=main and agents_list returning only "main" configured=false. Gateway config has agents.defaults.model populated, but no agents.list entries.

Impact and severity

Affected: users with minimal/single-agent configs (defaults-only).
Severity: Medium (prevents saving model changes from /agents UI path).
Frequency: 100% with defaults-only config.
Consequence: Confusing UX; users think edits are broken unless they switch to Config tab manually.

Additional information

No response