by Core-Mate
OpenGUI is an Android GUI agent framework for phone-use AI that can see, plan, and operate real mobile apps through the GUI.
# Add to your Claude Code skills
git clone https://github.com/Core-Mate/OpenGUILast scanned: 5/30/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-05-30T16:18:49.321Z",
"npmAuditRan": true,
"pipAuditRan": true
}OpenGUI is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by Core-Mate. OpenGUI is an Android GUI agent framework for phone-use AI that can see, plan, and operate real mobile apps through the GUI. It has 1,586 GitHub stars.
Yes. OpenGUI passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/Core-Mate/OpenGUI" and add it to your Claude Code skills directory (see the Installation section above).
OpenGUI is primarily written in Kotlin. It is open-source under Core-Mate on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh OpenGUI against similar tools.
No comments yet. Be the first to share your thoughts!
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
OpenGUI reads a real Android app UI, plans the next step, takes mobile actions, and returns structured results.
The shortest path on macOS is to let Codex run the pinned installer Skill. It requires Node.js 22.19+ or 24+ and installs the compatible DSH version automatically. Paste this as one prompt:
Install and run the OpenGUI installer Skill from https://github.com/Core-Mate/OpenGUI/tree/dsh-coremate-mobile-v0.1.5/deepseek-harness-plugin/skills/opengui-coremate-install for my DSH web profile. Only ask me for phone-side authorization and model credentials.
The Skill downloads the public release package and checksum, verifies SHA-256, installs only the OpenGUI plugin, starts DSH when needed, and opens DSH. It preserves unrelated DSH plugins and settings. If DSH was already running, restart it once to load the plugin. For Linux or Windows, use the manual package guide.
After installation, add or select a DSH workspace, connect and select an authorized Android phone, then send:
@OpenGUI Open Settings and report the Android version
The plugin adds phone and browser operation to DSH without requiring the full OpenGUI backend stack. See more use cases or download the v0.1.5 release package.
Good fits include:
For GUI execution, our current recommendation order is:
| Priority | Model family | Guidance |
|---|---|---|
| 1 | Doubao VLM | Recommended first for visual GUI execution. |
| 2 | Qwen VLM | A practical alternative, but some social media prompts may be more sensitive to model safety policies. |
| 3 | OpenAI vision-capable models | Capable, but generally the higher-cost option for screenshot-heavy tasks. |
| 4 | Grok vision-capable models | Experimental for this workflow; tool use and action reliability still need more validation. |
Model availability, pricing, and policy behavior vary by version and region. Whichever provider you choose, the model must support both image input and tool calling.
To run the full OpenGUI backend and Android client, let Claude Code or Codex bootstrap it for you.
Read ./skills/open-gui-bootstrap/SKILL.md and help me run OpenGUI. Only ask me for phone-side actions.
You will need:
OpenGUI will use the repository scripts to start the backend and install the Android client:
cd server
./start.sh
cd client
./start.sh
After the backend and Android client are running, send a first task:
cd server
pnpm opengui -- devices --json
pnpm opengui -- do "Observe the current Android screen and summarize what you see" --json
The task response includes an executionId. Keep it so you can stop the active task:
pnpm opengui -- cancel <executionId> --json
Manual setup guide: docs/get-started.md.
[2026.5.16] Added Codex / Claude Code remote control with a local REST API, pnpm opengui -- ... CLI, and the open-gui-remote-control Skill for dispatching Android app tasks from coding agents.[2026.5.9] Added a Discord IM channel for remote Android task dispatch, including prefix commands, slash commands, allowlists, and guild-scoped command registration.[2026.5.7] Hardened local startup to avoid common PostgreSQL and Redis port conflicts during Docker-based backend setup.[2026.5.1] Improved backend onboarding with .env.example, startup checks, and graph-agent VLM environment configuration.OpenGUI provides an Android GUI agent stack for screen understanding, task planning, action execution, review, and recovery.
You can use the same repository in four practical ways:
Operate mainstream Android apps: let AI handle mobile tasks inside X, Reddit, Hacker News, Telegram, WeChat, Weibo, Xiaohongshu, and other Android apps on a real phone.
Run shipped workflows: the repository already includes a runnable backend, Android client, standby dispatch path, and a set of built-in task capabilities.
Let Claude or Codex bootstrap it for you: point the model at skills/open-gui-bootstrap/SKILL.md, describe the goal in plain language, and let it handle setup, build, install, and local debugging.
Let Codex control Android apps: after OpenGUI is running, point Codex or Claude Code at skills/open-gui-remote-control/SKILL.md to list devices, dispatch tasks, and track executions through the local CLI.
Operate phones as remote workers: dispatch tasks through Feishu, Telegram, Discord, or REST API, keep devices on standby, and get structured results back from the backend.
Plan Supervisor maintains task state and continuation, Executor Graph runs screenshot, vision, action, and call-user loops on top of live device state, and Summarizer closes the run with a structured result.OpenGUI is built as a mobile operator system with explicit orchestration layers.
The source code currently exposes these pieces:
server/apps/backend/src/modules/graph-agent/graph/mobile-agent.graph.ts for the main graphserver/apps/backend/src/modules/graph-agent/graph/executor.graph.ts for the device-side execution loopserver/apps/backend/src/common/ws/standby.gateway.ts for standby device dispatchclient/core_network/.../StandbySocketManager.kt for persistent device standby connectionsclient/core_accessibility/.../GestureService.kt for Android-side action execution| Dimension | Typical phone-agent demo | OpenGUI |
|---|---|---|
| Execution model | Short interactive loop | Main graph plus executor subgraph |
| Task state | Usually local and session-bound | Task state managed in the backend graph |
| Device path | Often laptop-driven control | Android client with standby and execution sockets |
| Model usage | One model does most of the work | Planning and VLM paths can be split across providers |
| Remote operation | Optional add-on | Feishu, Telegram, Discord, REST API, and standby dispatch are built into the backend |