Adapted community discussion: Paraphrased and condensed from an anonymized public OpenClaw Discord support conversation from September 2026. Technical guidance was reviewed for OpenClaw 2026.9.3.
After updating, running openclaw says the TUI cannot choose an owner because multiple agents are configured. I also think the Gateway is not starting. Are those the same failure?
They are separate. An ownerless multi-agent roster makes an unscoped TUI session ambiguous, while the Gateway can be healthy or unhealthy independently. Use an explicit session for the TUI, then inspect the service separately:
openclaw agents list --bindings
openclaw tui --session agent:AGENT_ID:main
openclaw gateway status --deep
In this case, the Gateway logs also show an unset system-agent owner and an installed provider plugin blocked on capability consent. Set the intended owner, inspect that exact installed plugin, and approve its reviewed capabilities or disable it. Then run Doctor and check the Gateway again.
The system-agent owner saved successfully, but the named provider plugin is not installed or discoverable, so there are no capabilities to approve.
Then do not install a guessed package. Inspect the actual registry and let the supported repair path reconcile stale plugin state:
openclaw plugins list --verbose
openclaw plugins doctor
openclaw doctor --fix
openclaw gateway restart
openclaw gateway status --deep
I decided to preserve the existing state directory under another name and reinstall because there is little work to keep. The npm package reinstalled successfully and the old state remains available.
The package reinstall succeeded and the renamed state remains untouched. Run fresh onboarding to create a new ~/.openclaw, then copy only reviewed workspace instructions, skills, and project files. Do not restore old credentials, device state, session databases, or the entire prior configuration.
Fresh onboarding completed, but the TUI still cannot reach a Gateway. The configured roster now shows only the default agent, while a second agent directory appears to be leftover state. The Gateway service is disabled, and openclaw gateway install refuses because it cannot safely inspect the user service definition.
That last error is a systemd user-manager inspection problem, not another package or roster failure. Keep the leftover state directory for now. Inspect XDG_RUNTIME_DIR, the user-manager state, and permissions under ~/.config/systemd/user; reload the user manager only after those checks are clean, then retry the supported Gateway installer. Do not force or hand-replace service files.