This is an early release preview. You may encounter bugs.
OpenGUI logo
Unclaimed

Tool interface research

OpenGUI

OpenGUI is an Android GUI agent framework for phone-use AI that can see, plan, and operate real mobile apps through the GUI.

A 82/100 GitHub score ? This grade is derived from GitHub signals, not user votes. Open for the full breakdown.
Discussion

01 / Summary

About OpenGUI.

OpenGUI is an agent framework for operating Android apps through their graphical interface on real phones and emulators. It reads the current screen, plans the next step, performs taps and other mobile actions, and returns a structured result. Example tasks include collecting posts on X, summarizing Reddit or Hacker News threads, UI regression testing, and repetitive in-app workflows, with human confirmation recommended before publishing, messaging, or account changes.

The full stack has a backend and an Android client. In the backend, a main graph handles planning, a Plan Supervisor keeps task state and continuation, an executor subgraph runs screenshot, vision, action, and call-user loops against the live device, and a Summarizer closes each run with a report of what happened and what still needs attention. The Android client uses the standard AccessibilityService APIs for screenshots and actions, so no root access or unlocked bootloader is needed. Phones can stay on standby and receive work through Feishu, Telegram, Discord, or a REST API.

Planning and visual execution can use different model providers. The recommended order for visual GUI execution is Doubao, then Qwen, then OpenAI vision models, with Grok experimental, and any chosen model must accept image input and tool calls. A cost-saving profile pairs Qwen for planning with Doubao for vision, and a higher-cost profile uses Claude Opus throughout.

OpenGUI also ships as a plugin for DeepSeek Harness and a connector for WorkBuddy, both of which add phone operation without running the full backend. Coding agents such as Claude Code, Codex, and OpenCode can bootstrap the full stack from a bundled skill and then dispatch Android tasks through a local CLI.

  • Android GUI control: sees, plans, and operates real Android app interfaces on phones or emulators
  • Long-running tasks: a supervisor keeps task state and continuation for workflows that may run for hours, with review and recovery
  • Structured results: each run ends with a summary of what happened, what worked, and what still needs attention
  • Role-based model routing: planning and visual execution can use different providers
  • No root required: actions and screenshots go through Android AccessibilityService
  • Remote dispatch: standby phones take tasks from Feishu, Telegram, Discord, or a REST API
  • DeepSeek Harness plugin: adds phone and browser operation to DeepSeek Harness without the full backend
  • WorkBuddy connector: an MCP server, skill, and hooks that let WorkBuddy's visual model operate Android phones
  • Coding-agent control: skills let Claude Code, Codex, or OpenCode bootstrap the stack and dispatch phone tasks

02 / Discussion CREDIBILITY-GATED

Discussion

Reading is open to everyone. Posting and voting need a verified identity or a GitHub grade of B or higher.

  • No discussions yet.

04 / Build

Build with OpenGUI.

Browse the catalog for frameworks, tools, and harnesses, each scored on real GitHub credibility.

Get OpenGUI →

Browse the catalog