pockebot / openpocket

OpenPocket An Intelligent Phone That Never Sleeps Let AI handle your phone-use tasks — locally, privately, autonomously. Website · Documentation · Quickstart · Discord · Reddit · Contributing = 20" /> --- What is OpenPocket? Imagine having a second phone that works for you around the clock — replying to messages, handling payments, playing games, posting on social media — all while your real phone stays safely in your pocket, untouched. **OpenPocket** is an open-source framework that lets AI agents operate an Android phone on your behalf. Tell it what you want in plain language, and it figures out the rest — tapping, scrolling, typing, navigating between apps — just like a real person would. • **Local-first** — everything runs on your machine; your data never leaves your computer. • **Privacy by default** — the agent phone and your personal phone are completely isolated. Sensitive actions require explicit human approval. • **Emulator + real device** — connect to Android emulators or physical phones over ADB. Run multiple agents against multiple targets to build your own local phone farm. • **Extensible** — add new capabilities through a single file, or build your own agent workflows. Demos Social Auto-manage social media Gaming Play mobile games autonomously Utility Payment Handle bills and payments Studying Assist with learning tasks Social Autopilot your X Utility Find best price/travel option Highlights • **Multi-model** — works with OpenAI GPT-5.x, Claude 4.6, Gemini 3.x, DeepSeek, Qwen, GLM, Kimi, MiniMax, Doubao, and more. • **Multi-agent** — run multiple isolated agents, each with its own config, workspace, target device, and session state. • **Scheduled jobs** — create cron tasks from chat or CLI in natural language (e.g. *"Every day at 8am open Slack and check in"*). • **Human-auth relay** — sensitive actions (camera, payments, location) escalate to you for approval through a private local relay. • **Channel integrations** — receive tasks and results through Telegram, Discord, WhatsApp, or CLI. • **Skills framework** — extend agent capabilities by dropping a into the skills directory — no code changes needed. Quick Start Option A — npm (recommended) Option B — from source (for contributors) Then start the agent gateway: Or run a one-off task directly: For full setup details see the Quickstart guide, Device targets, and Configuration. Usage Multi-agent management Target a specific agent with : Scheduled jobs From chat or CLI, describe a schedule in natural language. OpenPocket confirms before persisting. Jobs run in isolated sessions. Manager dashboard and shared relay • — overview of all agents, targets, channels, and gateway status. • — shared relay hub for human-auth approval flows, with optional ngrok public URL. Device targets Model profiles Model configuration is per-agent. New agents inherit from the onboard template; each can diverge independently. Gateway logging Tune log level, payload redaction, and per-module output in your agent config: Full CLI reference: CLI and Gateway | Filesystem layout Architecture Components | # | Component | What it does | Docs | |---|-----------|-------------|------| | 1 | **Multi-agent manager** | Registry, port allocation, and target locks for one default + N managed agents | Multi-agent, Filesystem | | 2 | **Gateway orchestration** | Per-agent gateway, dashboard, session store, channel credentials, task queue | CLI & Gateway, Runbook | | 3 | **Prompting & model loop** | System/user prompt composition, context budgeting, model-driven step execution | Prompting, Prompt templates | | 4 | **Tool execution** | ADB phone actions, coding tools, memory tools, and user-defined scripts | Action schema, Scripts, Skills | | 5 | **Human authorization** | Capability probe + escalation for sensitive actions, shared relay hub with per-agent state | Remote human auth | | 6 | **Device target abstraction** | One target per agent, mutual exclusion enforced by the manager | Device targets | | 7 | **Persistence & audit** | Sessions, memory, screenshots, relay state, artifacts — all inside the agent workspace | Filesystem, Session & memory | | 8 | **Runtime operations** | Manager dashboard, per-agent dashboards, keep-awake heartbeat, troubleshooting playbooks | Runbook, Troubleshooting, Screen awake | Contributing We'd love your help making OpenPocket better. Whether it's fixing a typo, improving docs, adding a new skill, or building a major feature — every contribution matters. Getting started • Fork the repo and create a feature branch. • Install dependencies and run the dev checks: • Keep changes focused — one concern per PR. • Add or update tests for any behavioral change. • Open a PR with context on **what** changed, **why**, and how you verified it. Where to help • **Good first issues** — look for issues labeled in the issue tracker. • **Skills** — write a new to teach the agent a new phone workflow. See the Skills guide. • **Model adapters** — add or improve support for new LLM providers. • **Channel integrations** — improve Telegram, Discord, or WhatsApp support, or add new channels. • **Docs** — fix gaps, add examples, or translate content. Read the full guidelines before opening a PR: CONTRIBUTING.md | contribution.md License This project is licensed under the **MIT License** — see LICENSE for details. Acknowledgments Special thanks to the open-source projects that make OpenPocket possible: • **pi-mono ecosystem** by Mario Zechner — , , • **Messaging SDKs** — , , • **Core runtime** — , , , , , • **Docs & tooling** — , , , And thanks to all contributors and community members who report issues, share real-world scenarios, and help shape the project. We're building this together.