openclaw - 💡(How to fix) Fix Control UI: add Agents tab New Agent MVP [1 pull requests]

Split from #11146.

Problem

The Gateway has lower-level agent creation APIs, but the Control UI Agents tab still has no New Agent/Create Agent flow. Creating an agent remains a CLI/config/filesystem task for users who are already inside the dashboard.

Current source evidence:

• src/gateway/server-methods/agents.ts exposes agents.create and creates configured agent workspace state.
• ui/src/ui/views/agents.ts exposes refresh, selection, files, config, model, tools, skills, channels, cron, and default-agent callbacks, but no create-agent callback/action.
• ui/src/ui/app-render.ts wires agent editing flows, but no UI path calls agents.create.

Scope

Add an Agents tab New Agent MVP that reuses existing Gateway/Control UI contracts instead of creating a parallel setup path.

MVP fields:

• Agent name.
• Workspace path, with a deterministic default derived from the normalized agent id if the existing API requires it.
• Optional emoji/avatar/name identity fields only if they map directly to current agents.create params.
• Optional initial model selection using the existing model catalog flow.

MVP behavior:

• Calls agents.create.
• Refreshes the agents list after success.
• Selects the newly created agent.
• Shows clear validation and failure states for duplicate/reserved names, invalid workspace paths, and Gateway errors.

Out of scope for the first PR unless a maintainer explicitly expands it:

• Template gallery.
• Custom SOUL.md / USER.md editing inside the creation modal.
• Tool allowlist editing during creation.
• Automatic session spawning after creation.
• Marketing/operations-specific preset content.

Those can build on top after the base UI contract is shipped.

Acceptance criteria

• The Agents tab has a discoverable New Agent action.
• Successful creation uses agents.create, refreshes list state, and selects the created agent.
• Error states are visible and do not leave stale optimistic UI.
• The implementation preserves current Agents tab editing behavior.
• Focused tests cover success, duplicate/error handling, and list refresh/selection after create.

Validation expectation

Before merge, run focused Agents UI/controller tests and the repo's changed-file gate in Testbox for user-visible Control UI work.