OpenClaw rebuilds web and native apps around goal visualizations
OpenClaw says it redesigned its web interface and native apps around visualizations for goals, compaction events, and team identities. The project says the web UI is nearing a stable release and supports local hardware and Ollama.

TL;DR
- The rebuild centers the web and native interfaces on goal visualizations, compaction events, and team identities, as steipete's channel comparison describes.
- OpenClaw says its native app lineup spans macOS, Windows, Linux, iOS, and Android in steipete's platform reply.
- Team sessions can move across machines and into cloud runs when busy or selected, according to steipete's infrastructure description.
- Local-model support now includes automatic Ollama detection, steipete's Ollama update says.
OpenClaw's Web docs put the browser Control UI on the same port as the Gateway WebSocket. Its macOS guide describes a menu-bar client that can bootstrap a local Gateway, while the feature list places the dashboard alongside multi-agent routing and mobile nodes.
Goals, compaction, and identities
Goals, compaction events, and team identities are the three interface elements that steipete says Telegram cannot fully carry in steipete's channel comparison. The development preview frames them as a shared session workspace, with a sidebar for named projects and people.
The restart-recovery treatment in steipete's development preview lays out four behaviors:
- Retry an explicitly retryable gateway rejection after 100 ms to 30 seconds.
- Queue a reply sent before a disconnection, then deliver it after reconnecting.
- Check history twice after an ambiguous delivery, then stop to avoid duplicates.
- Show
Not sent · Retryonly after a hard failure.
Native clients
The Mac beta installation is deliberately plain: “install the Mac app and everything works,” as steipete's beta setup reply puts it; that reply also says settings were rebuilt. The wider platform claim covers five operating systems and mobile platforms.
OpenClaw already had a web UI in December, steipete says in steipete's web UI reply. The current work is a polish pass on that existing surface rather than a first browser release.
Chat handoffs
The team workflow starts inside chat and continues in a session link.
- Discord: In steipete's Discord workflow, the agent follows a discussion, starts work in a new cloud or node session, returns a link, and lets the team continue there.
- Slack: OpenClaw added interactive cards, according to steipete's Slack reply.
- Permissions: Maintainers can view and edit other users' sessions, while guests can view all sessions but edit only their own, steipete says in steipete's permissions reply.
Gateway and workers
The underlying setup is a team server that distributes sessions across machines and sends work to cloud runs when capacity is tight or the user chooses it. For OpenAI models, steipete says in steipete's infrastructure description that OpenClaw uses the Codex harness, retaining existing connectors.
Self-hosting can include the project's “cloud” workers on a user's own hardware, steipete's hosting reply says. The project also auto-detects Ollama, bringing local models into that same worker setup.
Stable tag
The build remains on a development track. steipete says in steipete's stability update that performance and smaller papercuts are the current focus before it earns a stable tag.
Asked about timing, he answered “coming week” and described the remaining work as papercuts in steipete's timing reply.