This page is built specifically for brand-intent queries. It explains product definition, core capabilities, native app roles, the local-first Gateway architecture, and the extension system instead of centering download flow.
Message entry points
22+
The README currently lists public WhatsApp, Telegram, Slack, Discord, Signal, iMessage, and other channel entry points.
Native apps
3
The current `apps/` tree contains real macOS, iOS, and Android targets plus shared code.
Extension packages
76
The current `extensions/` tree ships 76 packages across channels, tools, voice, memory, and model integration.
Core platforms
3
One personal assistant product spanning a desktop control plane, an iPhone node, and an Android voice node.
Product definition
Because the core repository is not just a chat surface. It also ships gateway, agents, sessions, browser control, canvas-host, media, memory, plugins, and node-host layers.
The current README shows OmniClaw routing 22 public messaging and chat entry points through a single Gateway control plane instead of a single chat box.
The README, VISION, and the `src/gateway`, `src/agents`, and `src/sessions` modules show a local-first Gateway at the center of the product.
The repository already ships native macOS, iOS, and Android targets, and the README explicitly calls out Voice Wake, Talk Mode, Live Canvas, and node capabilities.
The `extensions/`, `src/plugins`, `src/plugin-sdk`, and VISION docs make it clear that capability grows through extensions, skills, and the dedicated memory slot.
Architecture
These descriptions come directly from the main README, the VISION doc, and the real structure of `src/gateway`, `src/agents`, `src/browser`, `src/canvas-host`, `src/media`, `src/memory`, and `src/node-host`.
`src/gateway` owns sessions, events, config, webhooks, cron, and the control surface, and the README explicitly says the Gateway is the control plane.
`src/agents`, `src/sessions`, `src/context-engine`, and `src/memory` show a runtime with sessions, context, memory, and multi-agent routing rather than a static chat UI.
`src/browser`, `src/canvas-host`, `src/media`, and `src/node-host` connect browser control, Live Canvas, media understanding, and device execution into one product.
The VISION doc and iOS README emphasize pairing, TLS trust prompts, DM pairing, push relay, and App Attest, which is the shape of a real assistant running on real devices.
Native endpoints
macOS behaves like the desktop control plane, iPhone behaves like a secure node and mobile control surface, and Android emphasizes continuous voice and action-heavy execution.
OmniClaw
The desktop control plane for menu bar access, Gateway lifecycle, Voice Wake, Talk Mode, and Live Canvas.
The macOS app is where OmniClaw feels most complete: local-first gateway management, channel setup, cron, Canvas, browser-driven workflows, and native device tools on one desktop surface.
Public traction
28.6K
Completion
4.9
Version
2026.3.25
OmniClaw
A secure iPhone node for pairing, voice, Canvas, sharing, push wake, and mobile device tools.
The iPhone app combines setup-code pairing, gateway discovery, TLS trust prompts, Voice Wake, Talk Mode, share extension forwarding, and a real set of node-side device actions.
Public traction
16.4K
Completion
4.8
Version
2026.3.25
OmniClaw
The continuous-voice mobile node with chat, wake, notifications, and deeper device execution on Android.
The Android endpoint extends the same OmniClaw assistant model into a device that is optimized for continuous voice and action-heavy mobile automation.
Public traction
14.3K
Completion
4.7
Version
2026.3.25
Brand FAQ
This FAQ covers product definition, platform scope, architecture, and the cross-language brand mapping.
OmniClaw is a personal AI assistant you run on your own devices. It combines a local-first Gateway control plane, 22 messaging entry points, native macOS/iPhone/Android apps, Voice Wake, Talk Mode, Live Canvas, browser control, media pipelines, and an extension system into one runtime.
Because the repository includes agents, sessions, gateway, browser, canvas-host, media, memory, node-host, plugins, cron, and channel integrations. It is built to route, remember, act, and execute across real devices.
The public codebase already ships native macOS, iOS, and Android targets. macOS behaves like the desktop control plane, iPhone behaves like a secure node and mobile control surface, and Android emphasizes continuous voice and device actions.
万擎 is the Chinese name of OmniClaw. Visible page names switch by locale, while structured data keeps the alternate name for entity mapping across languages.