OpenOmniBot

Introduction: This is community version of OmniMind Xiaowan app || 或者你也可以叫她 OOB!她可以操作终端,也可以完成 Android 世界的广泛任务
More: Author   ReportBugs   
Tags:

OpenOmniBot

Your On-Device AI Assistant

GitHub Repo stars GitHub Release
omnimind-ai%2FOpenOmniBot | Trendshift
OmniMind Linux Do Community WeChat Group

| Demo | Quick Start | Release | Issues | English | 简体中文 |

OpenOmniBot runs directly on your Android device and combines chat, agent tools, local workspaces, and system integrations in one app.

OpenOmniBot is an on-device AI agent built with native Android Kotlin and Flutter. Instead of stopping at chat, it focuses on the full loop of understand -> decide -> execute -> reflect.

Core Capabilities

  • Extensible tool ecosystem: Skills, Alpine environment, browser access, MCP, and Android system-level tools.
  • System-level actions: Supports scheduled tasks, alarms, calendar creation/query/update, and audio playback control.
  • Memory system: Short-term and long-term memory with embedding support.
  • Productivity tools: Read and write files, browse the workspace, use the browser, and access the terminal.

Example

Quick Start

Configure the app

Open the settings page from the left sidebar:

Configure AI capabilities Configure AI providers

Then open the scenario model settings:

Configure AI models

Note: Memory embedding requires an embedding model. For the best overall experience, the other scenarios should use multimodal or vision-capable models whenever possible.

Alpine environment

The app usually initializes the Alpine environment automatically on startup, and you can also manage that environment from the same settings area.

Use Cases

Skills

You can ask OmniBot to install a skill by simply sending it the repository link. Recommended collection: https://github.com/OpenMinis/MinisSkills

Enable or disable skills from the skill repository:

Skill store Skill example

Scheduled tasks

Scheduled task Timing

Scheduled tasks execute subagent flows. Alarms are reminder-only. A subagent can be assigned a complete task and behaves like a full agent.

Browser

Browser

Workspace

Workspace

Remote Codex bridge

To use Codex mode with Codex running on a PC or Mac, start codex-bridge on the computer where the Codex CLI is installed and logged in:

npx @thuocean/codex-bridge

Choose the LAN address and token mode in the terminal setup UI, then scan the printed QR code from OpenOmniBot's Codex settings. For advanced options and troubleshooting, see the codex-bridge README.

Development Guide

Requirements

  • Flutter SDK 3.9.2+
  • JDK 11+
  • Node.js 20.19+ or 22.12+ and pnpm 10.28.0 (for WebUI development)

Get the code

git clone https://github.com/omnimind-ai/OpenOmniBot.git
cd OpenOmniBot

cd ui
flutter pub get

If Flutter reports Could not read script '.../ui/.android/include_flutter.groovy', run:

flutter clean
flutter pub get

Develop the WebUI locally

The WebUI in webchat/ is a standalone React + TypeScript + Vite project. During local development, Vite serves the frontend with hot reload and proxies /webchat/api requests to the Android app's local service.

  1. Install and start OpenOmniBot on an Android device. Keep the computer and device on the same trusted LAN.
  2. In the app, open Settings > Local Service, enable the service, and copy its address and Token. The default port is 8899, but always use the address shown by the app.
  3. Start the WebUI development server from the repository root, replacing the sample address with the Android local-service address (do not append /webchat):
cd webchat
pnpm install --frozen-lockfile

VITE_WEBCHAT_PROXY_TARGET=http://192.168.1.20:8899 pnpm dev

On PowerShell, set the proxy target first:

$env:VITE_WEBCHAT_PROXY_TARGET = "http://192.168.1.20:8899"
pnpm dev

Open the URL printed by Vite (normally http://localhost:5173) and enter the Token copied from the app. Use pnpm dev for end-to-end API/SSE testing; the proxy keeps session cookies, realtime events, workspace access, and browser mirroring on the same local origin.

Before submitting WebUI changes, run:

cd webchat
pnpm run typecheck
pnpm run build

The production files are generated in webchat/dist/. Both dist/ and node_modules/ are local outputs and must not be committed.

Android builds handle the WebUI automatically: Gradle runs the locked pnpm install, executes the Vite production build, clears stale WebChat assets, and copies only dist/ into the APK. To verify this step without building the full app, run:

./gradlew :app:syncWebChatBundle -Ptarget=lib/main_standard.dart

Flutter Web is not part of this workflow.

Build and install

cd ..

./gradlew :app:installDevelopStandardDebug -Ptarget=lib/main_standard.dart

Architecture Overview

OpenOmniBot/
├── app/                        # Android host app: entry point, agent orchestration, system abilities, MCP, services
├── ui/                         # Flutter Android UI: chat, settings, tasks, and memory
├── webchat/                    # React + TypeScript WebUI; Vite builds the static bundle packaged by Android
├── baselib/                    # Shared core libraries: database, storage, networking, model config, permissions
├── assists/                    # Shared task lifecycle and chat/model coordination
├── uikit/                      # Native overlay UI: floating ball, overlay panels, half-screen surfaces
└── ReTerminal/core/            # Embedded terminal experience modules

Community

Thanks to the community ( including linux.do )developers supporting OpenOmniBot.

Special thanks to these open-source projects:

WeChat Group
Join Discord: https://discord.gg/WnBvBXgykD
Apps
About Me
GitHub: Trinea
Facebook: Dev Tools
AI Daily Digest