What happened
PhoneBox is an open-source project published in the ersinkoc/phonebox GitHub repository. Its README describes a system made up of a full-screen Android app and a small desktop agent. Users configure the phone panel through a browser-based visual editor, choosing among 124 widgets and 30 templates, arranging multiple pages, and previewing layouts with live data. Layouts use a 12-by-6 grid, support portrait and landscape orientations, and can place up to 12 widgets in a Smart Stack slot.
The project targets Windows, Linux, and macOS computers, paired with Android 5.0 or later; Android 6 or later is recommended. The README lists Windows 10/11 x64, Linux x64 and ARM64, and macOS on Apple silicon or Intel. Windows ARM and musl Linux distributions such as Alpine do not have release builds. The Android app is not distributed through an app store, and the README says there is no iOS version.
PhoneBox supports USB and paired Wi-Fi connections. USB setup requires a data cable, USB debugging, and authorization on the phone. Wi-Fi pairing does not require USB or developer options: the user enables the setting in the local desktop settings page, restarts the agent, scans a pairing QR code, and confirms a matching check code. The desktop settings server listens on 127.0.0.1:8765; optional Wi-Fi uses HTTPS on port 8766 with a pinned certificate and paired key. The project says no cloud service, PhoneBox account, or root access is required.
The listed use cases range from CPU, GPU, memory, disk, network, and process monitoring to media controls, shortcuts, macros, webhooks, and Home Assistant actions. For AI coding, the README describes quota and reset-time views for Claude, Codex, and Antigravity; local Claude Code and Codex session views; and GitHub review and CI status. A user can tap a session to inspect its model, timing, and token details. Opt-in Claude Code permission prompts can be answered Allow or Deny from the phone. Optional CodexBar integration adds quota providers and a cost overview.
The repository identifies the project as MIT-licensed and shows 3.5k stars and 467 forks. Its setup scripts download the latest release, check its SHA-256 checksum, offer dependencies and start-at-login, and open local settings. The README warns that Windows release agents are currently unsigned while a SignPath Foundation application is pending; SmartScreen or antivirus software may warn or block them. PhoneBox says it has no telemetry, analytics, or accounts of its own, while optional integrations can contact external services for data such as weather, quotas, and GitHub status.
What the archive adds
New Runtime's earlier coverage of PhoneBot on 2026-10-18 described a different use for commodity phones: sensing and high-level computing inside a small humanoid robot. PhoneBox is a new event, not a new fact about PhoneBot; the shared idea is making existing phone hardware useful in a broader system.
Trend signal
This does not yet fit a pattern New Runtime tracks. PhoneBox makes a phone a local control surface for a computer, but the repository alone does not establish a broader shift in how agent products expose capabilities or how teams orchestrate AI work.
Why now
The README positions PhoneBox for workflows that already involve AI coding sessions: it names Claude Code and Codex, surfaces session details and quotas, and offers phone-based responses to Claude Code permission prompts. That makes an old phone a possible companion display without requiring a new cloud service or dedicated control hardware. The repository does not explain a specific launch date or external trigger for the project.
Why it matters
A dedicated screen can make status and controls easier to glance at than a buried desktop window, particularly when the computer is busy running coding sessions. PhoneBox combines several separate jobs—system monitoring, session visibility, quotas, media, and touch controls—inside one configurable panel, and supports more than one phone or paired computer. For teams experimenting with agent workflows, the permission-prompt option is especially concrete: it creates a way to respond to Claude Code requests from the phone rather than treating the phone as a passive dashboard.
The trade-off is that this is an additional local utility to install, configure, and trust, not an agent runtime or a substitute for reviewing agent work. Builders should check the project’s platform requirements and security notes before pairing devices or enabling integrations. In particular, USB debugging should be authorized only on trusted computers, and Windows users should account for the unsigned release warning. The value is practical when the spare device and the relevant workflow already exist; it is not evidence that a phone-based interface improves coding outcomes by itself.
Limits and uncertainty
The README describes features and supported platforms, but does not report independent testing, reliability measurements, user outcomes, or performance overhead. It does not quantify whether putting session details or permission prompts on a phone changes review speed or error rates. Widget availability depends on host hardware, installed tools, and permissions, and some platform-specific features have their own requirements. The project says it has no telemetry or accounts of its own, but optional integrations may contact external services; builders should consult its privacy policy and verify which integrations they enable. Windows release agents are unsigned at the time described in the README, so installation may be blocked or warned against by security software.
Skill to build now
If you have a spare Android phone and want a companion screen, start with the project’s AI Sessions template rather than building a layout from scratch. Install the desktop agent for your operating system, then use the local editor to inspect the available session and quota widgets and arrange only the information you need. For wireless pairing, enable Wi-Fi in settings, restart the agent, scan its QR code, and verify the matching code. Keep USB debugging limited to trusted computers, and review optional integrations before enabling them.
Reader takeaway
PhoneBox is a configurable, local-first way to reuse an Android phone as a computer control panel, with specific views for Claude Code and Codex workflows. It is worth evaluating as a companion display—not as a new coding agent—and users should weigh setup and platform security caveats against the convenience of a dedicated screen.