OpenPocket Documentation
This documentation is organized in documentation hubs (inspired by OpenClaw docs information architecture):
- Start with task-oriented onboarding.
- Move to concepts and execution model.
- Use tools/reference pages for exact schemas and defaults.
- Keep operations and troubleshooting separated.
All pages in this folder document implemented behavior in the current TypeScript runtime (src/). For the native macOS menu bar app, see:
Direction
OpenPocket is a local emulator-first phone-use agent aimed at real consumer scenarios, not only developer workflows.
- local emulator execution instead of cloud-hosted phone runtime
- no resource usage on the user’s main phone during agent runs
- local data and permission boundary by default
- dual control model: direct human control + agent control
- upcoming remote phone control for human-in-the-loop interaction
Doc Hubs
| Hub | Purpose | Entry |
|---|---|---|
| Get Started | Install, initialize, and configure quickly | Quickstart |
| Concepts | Understand blueprint, architecture, and core agent mechanics | Project Blueprint |
| Tools | Skill and script authoring and runtime behavior | Skills |
| Reference | Precise schemas, defaults, formats, and commands | Config Defaults |
| Ops | Day-2 runbook and troubleshooting | Runbook |
Popular Specs
- Product blueprint: Project Blueprint
- Prompt templates: Prompt Templates
- Default values: Config Defaults
- Session and memory formats: Session and Memory Formats
- Skill format and loading rules: Skills
- Script format and execution rules: Scripts
- CLI and Telegram commands: CLI and Gateway
Scope Policy
- Document implemented behavior first, and clearly mark roadmap items as planned.
- Mark fallback behavior and normalization rules explicitly.
- Keep examples executable with current CLI.
Legacy Pages
Older planning pages are still available: