2026-10-11 16:37 UTC

Phonebox launched a cloud Android phone service billed by the second with full device control (screen, apps, touch, keyboard), parking when idle, and MCP/API/CLI interfaces for coding agents like Claude Code, Codex, and Cursor.

state: seedheat: mediumuncertainty: mediumconvergesscott: highagent-infrastructure mobile-agents cloud-android phoneboxPhoneboxBenoujo

What is this?

Phonebox (phonebox.dev) is an agent-first cloud Android phone service launched by the team behind combined-ai. It provides real Android devices in the cloud billed per second ($0.06/min, free when parked), giving AI agents full device control — screen reading, touch, typing, app installation — via MCP, CLI, TypeScript SDK, and REST API. Agents like Claude Code, Codex, and Cursor can drive the phone directly; humans can take over in-browser for sign-ins. The service explicitly does not provide phone numbers, SMS, or calling. The GitHub repo (combined-ai/phonebox-android-mcp) hosts the MCP server implementation.

Why it matters to Scott

Phonebox ships a V4 agent-addressable service: it exposes a delegation surface (state, actions, delegated authority, consequences, subscriptions) via MCP/CLI/SDK so coding agents (Claude Code, Codex, Cursor) operate real Android devices directly — exactly the code-first, agent-native, sandboxed cloud infrastructure Scott's frameworks argue for. Per-second billing with parking implements durable external state and session isolation for agent workloads. This is a dated-receipts moment for agent addressability, code-first architecture (MCP as transport beneath code-facing agents), and cloud agent infrastructure.
ip:framework.agent-addressabilityip:concept.delegation-surfaceip:framework.code-first-architectureip:framework.agent-native-computingip:concept.agent-hands-and-eyesip:source.mcp-as-the-tool-belt-standard-giving-ai-agents-hands-and-eyes-ebookip:concept.capability-scope-separationip:concept.sandboxed-executionip:framework.siloosip:concept.durable-external-stateip:concept.session-isolationip:concept.checkpoint-disciplinedev:concept.single-tenant-ai-appliancedev:concept.resumable-agent-job-control-planedev:concept.padded-cell-agent-architecturedev:technology.mcpdev:project.mcpdev:project.openclawdev:concept.state-managementdev:technology.claude-codedev:technology.codex-clidev:technology.opencodedev:technology.goosedev:concept.agentic-tool-loopdev:concept.deterministic-agent-control-planeradar:mobile-harness-cross-platform-controlradar:opposable-mobile-computer-useradar:android-mcp-on-device-pii-redactionradar:android-editable-graph-agentradar:aiope-android-agent-runtimeradar:fountain-resumable-agent-computersradar:machine0-persistent-agent-vmsradar:docker-cloud-sandboxes-releaseradar:blast-sandbox-as-a-serviceradar:cua-lite-local-computer-use-stackradar:opencyvis-self-hosted-phone-agentradar:cloudflare-kitesurf-agent-browserradar:tama-low-cost-gpu-sandboxesradar:manzanas-ios-agent-simulator-fleetradar:physiclaw-iphone-control-agent
queries asked of Scott's wikis
  • agent-computer interface patterns: MCP vs direct device control for mobile agents
  • cloud device infrastructure for agents: per-second billing, parking, cold-start latency
  • mobile agent autonomy: Android automation vs API-based app integration
  • local-first vs cloud agent runtimes: device sovereignty and self-hosted alternatives
  • agent memory and session persistence across parked cloud devices
  • coding agents (Claude Code, Codex, Cursor) as operators of external environments

Measured heat

now 0 pts/hpeak 2 pts/hcomments 0/hpeers p37momentum: steady2 platformsage 51h
points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion

How the heat travelled

10-09 13:00⭐ origin echo-reconstructedPhonebox provides cloud Android devices billed by the second for AI agents, with full device control (screen, apps, touch, keyboard), parkin
Phonebox team on blog (echo) · attributed from hn.story.50035912
—
10-10 18:51first on hacker news · published · +29.9hPhonebox – Cloud Android phones for AI agents
Benoujo
—
10-10 18:51amplified on hacker news 👑hn.story.50035912
Benoujo
peak 5 · 2 comments · 99% of case engagement
10-10 21:31our radar first saw it · +32.5hdiscovery anchor: hn.story.50035912—
pace: p49 vs 1204 stories at the 48h mark (now 51h old) — ahead of apimatic-agent-context-registry (1.2x), behind agent-iap-credential-brokering (0.9x)

Evidence (2) — ⭐ canonical anchor

sourceobjectauthorscorecomments
🟧 hnPhonebox – Cloud Android phones for AI agents
Retrieved article excerpt

Open article · Retrieved 2026-10-10T21:38:23.791445+00:00

01Cloud Android devices, billed by the second

# Give agents Android

AgentTerminal

`Read https://phonebox.dev/setup.md and set me up with Phonebox from here: get me signed in and ready, then find out what I want to use phones for and help me with that.`

CopyC[Try for free A](https://phonebox.dev/sign-up)

### Full device control for AI agents

02What your agent gets

## An Android device your agent can see and control

Phonebox doesn't give your agent a phone number, an SMS inbox or calling. It gives it the device itself: the screen, the installed apps, touch input and the keyboard.

One API call starts an Android phone in the cloud, and our CLI and SDK wait until it's ready to use. Your agent reads the screen as a short numbered list of what's on it, then taps by label, types, swipes and opens apps. It can also install apps, move files, and change the location or language.

**When your agent stops using a phone, it parks itself.** A parked phone costs nothing and keeps its apps and signed-in accounts for next time.

[Try for free S](https://phonebox.dev/sign-up)

Loading Android playground…

Try here

03Products

03.1

## Phonebox for coding agents

[Get the setup prompt 1](https://phonebox.dev/app)

123

Claude Code, Codex and Cursor can run Phonebox from the terminal. Give your agent our skill file and it can open your app on a phone, click through the new screens and tell you what it saw.

03.2

## Phonebox API

[Read the API reference 2](https://phonebox.dev/docs/api-reference)

Plenty of apps have no API. Through our REST API or TypeScript SDK, your agent can sign in to them, move between screens and finish tasks the way a person would with the phone in hand.

03.3

## Phonebox MCP

[Connect a client 3](https://phonebox.dev/docs/interfaces/mcp)

Add one URL and an API key to any MCP client. The model gets tools to start an Android phone, look at its screen, act on it and park it when the work is done.

[S Try for free](https://phonebox.dev/sign-up)

04Why Phonebox

## We keep the devices running so your agent can use them

### Built for agents

Agents are already good at reading a screen and choosing what to tap. The hard part is everything around the device: getting one, knowing when it's actually ready, turning it off afterwards, and not paying for hours nobody used.

Phonebox takes care of that. Phones park after ten idle minutes unless you choose otherwise, and never run past the limit you set. You pay per second while a phone runs and nothing while it's parked.

Every action is logged, every charge points to the session that caused it, and a monthly spending limit stops new sessions before a bill surprises you.

**Your agent decides what to do on the phone, and Phonebox makes sure there's a phone ready for it.**

### Start with your agent

AgentTerminal

`Read https://phonebox.dev/setup.md and set me up with Phonebox from here: get me signed in and ready, then find out what I want to use phones for and help me with that.`Copy

[Try the API A](https://phonebox.dev/sign-up)

[S Try for free](https://phonebox.dev/sign-up)

## Talk to us

Planning to run many phones at once, or need something we don't offer yet? Tell us what you're building and we'll reply by email.
Benoujo52
🟧 echo.blog ⭐Phonebox provides cloud Android devices billed by the second for AI agents, with full device control (screen, apps, touch, keyboard), parkinPhonebox team——

Interpretation history

Decision trace