# Poki: Open-Source iPhone Agent That Taps and Types in Real Apps

> Source: <https://explainx.ai/blog/poki-open-source-iphone-gui-agent-claude-code-install-2026?utm_source=rss&utm_medium=feed&utm_campaign=blog>
> Published: 2026-11-21 00:00:00+00:00

**Key takeaway:** Poki runs an on-device iPhone agent under AGPL-3.0 that reads the screen and taps, types and swipes in real apps using your own model keys, with payments always gated and a Notes-based "Poki Demo" task as the closed-loop install test.

**Poki is an open-source iPhone agent that operates real apps on the phone itself**, not a cloud browser session. The [JosssphZhou/poki](https://github.com/JosssphZhou/poki?ref=explainx) repository showed **about 1,700 GitHub stars** when explainx.ai checked on November 21, 2026, after trending the prior week. The project site is [poki.bot](https://poki.bot/?ref=explainx) — unrelated to the **poki.com** casual games portal searchers often mean.

If you are hunting **phone-use agents** after [OpenAI computer-use APIs](https://explainx.ai/blog/openai-computer-use-healthcare-gpt-6-astra-cvs-november-2026) and [Anthropic tool-use patterns](https://explainx.ai/blog/what-are-agent-skills-complete-guide), Poki is the **on-device, consumer-shaped** entry in that stack: **AGPL-3.0**, **your model keys**, and **hard stops** before money moves.

## What Poki does on an iPhone

The README headline is blunt: **Poki uses your iPhone like you do.** The app **runs on the device**, **reads the screen**, and **taps, types, and swipes** inside **real installed apps**, using **your** ChatGPT, Claude, Gemini, DeepSeek, OpenRouter, or compatible server credentials.

Three positioning points matter for builders:

| Feature | README claim | Why it matters | 
|---|---|---|
| On-device execution | No PC required after install | Unlike remote Mac relays in some MCP demos | 
| Permission tiers | User-chosen ask mode; payments always gated | Reduces runaway purchase stories | 
| Skills and voice | Saved skills, Action Button, Siri, Talk to Poki | Product UX beyond one-shot chat | 

**iPhone Duo Split View** lets one agent work across **two apps side by side** — closer to how humans context-switch than single-app demos.

On-device agent stack on a handheld device, illustrating local phone GUI automation

Joseph Zhou (周瑟夫) and contributors copyright the project **AGPL-3.0-only**; brand assets follow separate [BRAND.md](https://github.com/JosssphZhou/poki/blob/main/BRAND.md?ref=explainx) rules on the repo.

## Install path developers actually use

Poki's README optimizes for **coding agents as installers**:

```
Install Poki on my iPhone from https://github.com/JosssphZhou/poki
```

Prerequisites from [INSTALL-IPHONE.md](https://github.com/JosssphZhou/poki/blob/main/INSTALL-IPHONE.md?ref=explainx) summarized on the README:

- **iPhone** on**iOS 18+** (README also mentions testing on**iOS 27** builds).
- **Mac macOS 14+** with**Node.js 24+** for agent-driven install, or**Windows x64** with Apple Devices or iTunes.
- **USB data cable** and a**free Apple Account** ;**Poki Setup** can renew**7-day signatures** while open, or you sign in inside Poki for longer installs.
- **Developer Mode** and**Automation Mode** when iOS prompts.
- **VPN-style tunnel** so traffic to**10.7.0.1** routes back to the phone (LocalDevVPN, Karing, or Shadowrocket named in README).

The canonical first task in README: create a **Notes** entry titled **Poki Demo** with three grocery lines, then **open Notes** to verify — a minimal **closed-loop** test builders can script in eval harnesses.

Compare install friction to [agentes.chat self-hosted chat](https://explainx.ai/blog/agentes-chat-open-source-self-hosted-slack-alternative-ai-agents-mcp-agpl-github-trending-2026): Poki targets **one user, one phone**; agentes targets **team channels**. Both are AGPL-shaped and ask you to bring **model spend**.

## Models, skills, and triggers

Supported providers per README include **Anthropic, OpenAI, Gemini, DeepSeek, OpenRouter, OpenCode Go**, and **OpenAI-compatible servers**, plus **ChatGPT Plus/Pro** sign-in.

**Skills** live in repo folders the agent can launch by tap or voice — same cultural move as [AWS Quick skills](https://explainx.ai/blog/aws-quick-skills-agents-catalog-build-guide-2026) and [Jane Street socratic-tutor](https://explainx.ai/blog/janestreet-agent-skills-socratic-tutor-github-2026), but on a **phone shell** with **Action Button** and **Siri** hooks.

**Talk to Poki** runs a **spoken chat** with **Dynamic Island** step tracking, which is the UX pattern Apple platform reviewers watch closely when agents act outside Safari.

## Safety and compliance considerations

Phone agents sit at the intersection of **accessibility APIs**, **enterprise MDM policies**, and **fraud**. Before dogfooding:

1. **Read SECURITY.md** on the repo and file issues through GitHub if you find privilege leaks.
2. **Use a non-production Apple ID** until you trust automation on Wallet and Mail.
3. **Keep payment and delete confirmations on** — README says those classes always halt; do not patch that away in forks you ship to customers.
4. **Mind AGPL-3.0** if you embed Poki in a commercial mobility product; network use triggers copyleft obligations unless you negotiate a separate license with maintainers.

For agent-security architecture patterns — **policy before tool call** — see how explainx.ai approaches [coding-agent guardrails](https://explainx.ai/blog/cognition-acquires-corridor-devin-security-ex-cisa-founders-stamos-agent-written-code-guardrails-2026). Poki is consumer-facing, but the **approval gate** design is the same lesson.

## How Poki differs from remote computer-use stacks

| Approach | Control plane | Typical latency | Best for | 
|---|---|---|---|
| Poki on iPhone | On-device screen + input | Local UI loop | Personal errands in native apps | 
| Cloud CUA / Operator | Hosted VM or browser | Network round trips | Web-first workflows | 
| Mac MCP relay | Desktop tether | USB or LAN | Dev machines with full filesystem | 

Poki's bet is **offline-from-PC daily use** after a one-time install — interesting for markets where **Android desktop agents** already ship but **iOS automation** stayed sandboxed.

## What developers on Hacker News are watching

The GitHub trending entry drew builders comparing Poki to **Apple's own agentic hiring** stories explainx.ai covered in [Apple agentic assistant job listings](https://explainx.ai/blog/apple-agentic-ai-assistant-job-listing-siri-ui-frameworks-foundation-models-bloomberg-verge-2026). Expect threads to focus on **VPN tunnel requirements**, **7-day signing**, and whether **Split View** generalizes to **banking apps** with attestation.

None of that replaces **your** device test: star counts move faster than security review.

## iPhone requirements and release channels

The README's hardware table is worth copying into your internal runbook before a team pilot:

| Requirement | README detail | 
|---|---|
| Devices | iPhone XS, XR, SE 2nd gen or newer; iPadOS 18+ on iPad | 
| OS | iOS 18 minimum; project mentions physical testing on newer iOS builds | 
| Desktop | macOS 14+ with Node 24+ for agent install, or Windows with Apple device tooling | 
| Signing | Free Apple Account works; Poki Setup can refresh **7-day** signatures while open | 
| Networking | Tunnel routing **10.7.0.1** to the handset for API reachability | 

Poki documents **release channels** and verification steps in [INSTALL-IPHONE.md](https://github.com/JosssphZhou/poki/blob/main/INSTALL-IPHONE.md?ref=explainx) and the main [Poki iPhone App Guide](https://github.com/JosssphZhou/poki/blob/main/docs/guide.md?ref=explainx) linked from the README. Treat **changelog entries** as the source of truth when a demo video on social media shows a feature your build lacks — mobile agent projects ship weekly during hype cycles.

## Everyday tasks the README highlights

Beyond the Notes demo, Poki markets **practical errands**:

- **Built-in browser lookups** and**weather checks** from chat, Action Button, or Siri.
- **Saved skills** launched by tap or voice so repeat workflows do not need re-prompting.
- **Talk to Poki** hands-free sessions with**Dynamic Island** progress for multi-step chores.

Those flows matter for product managers comparing Poki to **Shortcuts automations**. Shortcuts are deterministic; Poki is **model-steered** with **visual grounding**. The failure mode is different: Shortcuts break when UI IDs shift; Poki may **mis-tap** when layouts change but can sometimes **recover** if the model reasons about the new screen.

## Split View and Duo scenarios

On **iPhone Duo**, Poki can operate **two apps in Split View** simultaneously. That is the architecture teams want when a workflow copies numbers from Mail into Numbers, or checks Maps while editing a Reminders list. Cloud browser agents typically **serialize** context across tabs; on-device Split View keeps **both pixel buffers** in scope for the same agent session — at the cost of **smaller tap targets** and **higher mis-click risk**.

Document **eval scenarios** per Duo pair you care about; do not assume one successful Notes test generalizes to banking plus authenticator apps.

## Licensing, contributions, and forks

Poki ships **AGPL-3.0-only** with a **Contributor Agreement** and brand guidelines. Forking for internal labs is fine; **shipping a rebranded store build** without complying with AGPL network copyleft triggers legal review.

The README points contributors to **GitHub Discussions** for ideas and **Issues** for bugs. If you integrate Poki lessons into an Android stack, compare openly with [Google Gemini robotics and assistant investments](https://explainx.ai/blog/google-duplex-tasks-gemini-business-phone-calls-november-2026) — different OS policy envelopes.

## Enterprise MDM and privacy posture

Corporate security teams should ask:

1. Does **Developer Mode** on employee phones violate policy?
2. Can the **VPN tunnel** exfiltrate traffic outside corporate DNS inspection?
3. Do **screen-reading agents** violate**app confidentiality** rules for healthcare or finance installs?

Apple's platform controls and Poki's **user confirmation** gates reduce but do not eliminate **insider misuse**. Pair technical controls with **logging exports** if the project adds them; at publish time the README emphasizes **local execution**, not centralized audit SaaS.

For screenshot and agent surveillance context on other messengers, see [Signal's screenshot block for AI agents](https://explainx.ai/blog/signal-blocks-screenshots-by-default-ai-agents-siri-gemini-recall-android-ios-macos-2026).

## When to choose Poki versus a cloud agent

Choose **Poki** when:

- The workflow is **native-app heavy** (Wallet, Health, proprietary enterprise apps).
- You need **offline-from-desktop** daily use after one USB install.
- You already pay for **ChatGPT Plus** or**Claude API** and want to reuse those accounts.

Choose **cloud computer-use** or **desktop MCP** when:

- The workflow is **browser-only** and you can sandbox a VM.
- You must **centralize** secrets and forbid on-device Developer Mode.
- You need **team observability** out of the box — Poki is single-user shaped today.

## Maintenance, updates, and support expectations

Open-source phone agents move quickly. Before you rely on Poki for daily automation, read **CHANGELOG.md** on the repo for breaking changes to **Automation Mode** prompts, **VPN requirements**, or **model provider auth**. The README explicitly marks **Poki MCP** and **Poki Agent** as **no longer updated** — do not copy their install docs.

Community support runs through **GitHub Discussions** and **Issues**; there is no enterprise SLA. Plan an internal owner who can rebuild signatures when Apple rotates provisioning profiles, especially if you use the free **7-day** developer certificate path.
