Productivity & Collaboration ioson-device-inferenceliterthealthkitcalendar-automationmobile-skillsollamavoice-interaction

PhoneClaw Mobile Runtime

Turn an iPhone into a local AI runtime with native mobile actions.

FollowAgents review · FARS-2.0
Not yet reviewed
See the full review method →

What does this agent do, and when should you use it?

PhoneClaw is a local AI agent runtime for iPhone that combines on-device inference with native mobile Skills. It runs Gemma 4 E2B/E4B through LiteRT and offers MiniCPM-V 4.6 for image Q&A and LIVE camera recognition. Requests can enter through text, voice, images, LIVE, or LiveLand, then use calendar, reminders, contacts, clipboard, and HealthKit capabilities. Skills are defined as SKILL.md files, with device tools registered through ToolRegistry.swift and Tools/Handlers. For heavier inference, a paired Mac can run PhoneClaw Gateway and expose Ollama, Codex CLI, or Antigravity CLI as a LAN inference source.

A user submits a request through chat, voice, an image, LIVE, or LiveLand; PhoneClaw processes it with local Gemma 4 or MiniCPM-V 4.6 and follows the Skill type. For a device Skill, the model emits <tool_call> and invokes an iOS tool registered in Tools/ToolRegistry.swift and Tools/Handlers/<Name>.swift; documented operations include creating and reading calendar events, availability analysis, creating reminders, managing contacts, reading and writing the clipboard, and reading HealthKit metrics. A content Skill such as translate produces a response from its SKILL.md instructions, while a network Skill such as web-search invokes network tools only for an explicit request for live information, search, or URL reading. Results are returned in the app interface, while LiveLand also shows task stages such as understanding, executing, and completion. In remote mode, the current inference request is sent to the paired Mac gateway, which listens on port 18080 by default and advertises _phoneclaw-llm._tcp through Bonjour.

  1. An iPhone user organizing a personal schedule can create events in natural language, inspect today's or this week's calendar, and ask for busy-time analysis.
  2. A person who wants an on-device health summary can authorize HealthKit and query steps, distance, active energy, heart rate, sleep, workouts, weight, or heart-rate variability.
  3. Someone updating personal contacts can ask the app to find, save, change, or delete contacts, with phone-number deduplication.
  4. A user who needs visual assistance can ask questions about a camera or photo-library image, or use LIVE mode for real-time camera recognition.
  5. A user with a Mac on the same LAN can move inference off the phone by pairing PhoneClaw Gateway and selecting an Ollama, Codex CLI, or Antigravity CLI source.

What are this agent's strengths and limitations?

Pros
  • Combines LiteRT local models with iOS-native calendar, contacts, reminders, clipboard, and HealthKit actions in one mobile runtime.
  • Uses file-based SKILL.md definitions and validates allowed-tools against ToolRegistry registrations.
  • Supports text, voice, image, LIVE, and LiveLand interaction modes; MiniCPM-V 4.6 covers image Q&A and live camera recognition.
  • The optional Mac Gateway uses Bonjour discovery and pairing while retaining the iPhone Skill experience and offering several documented runtime sources.
  • Model management includes cancellation, resumable downloads, retries, model switching, cache clearing, and history trimming for mobile constraints.
Limitations
  • Its core deployment target is an iOS 17+ physical device; source builds additionally require macOS, Xcode 16, CocoaPods, and an Apple ID, with no documented runtime for other desktop or mobile platforms.
  • E2B is about 2.4 GB and E4B about 3.4 GB; E4B and complex multi-turn tasks are recommended for newer iPhones, so memory and hardware affect adoption.
  • Calendar, reminders, contacts, and HealthKit depend on user permissions; previously denied access must be re-enabled in iOS Settings.
  • Web search, URL reading, and Mac inference are not fully local paths; when the Mac uses a CLI or another upstream provider, its data handling governs that request.
  • Licensing evidence is inconsistent: the repository metadata says NOASSERTION while the README claims Apache 2.0, so adopters should verify licensing before use.

How do you install or deploy this agent?

The recommended route is TestFlight: https://testflight.apple.com/join/YuUSwq78 . After installation, download a model in Model Settings and enable the permissions needed by Skills. Building from source requires macOS, Xcode 16, iOS 17+, CocoaPods, a physical device, and an Apple ID: run git clone https://github.com/kellyvv/phoneclaw.git, cd phoneclaw, and pod install, then open the workspace with open PhoneClaw.xcworkspace. In the PhoneClaw target, select a Team and replace the Bundle Identifier with your own unique value before running on the connected iPhone. With a shell install, download E2B or E4B in Model Settings; alternatively, package a .litertlm model as an app resource.

How do you use this agent?

Download or select a model in Model Settings, then grant the calendar, reminders, contacts, or health permissions your intended Skills need. Use the puzzle icon to manage Skills and the slider icon for model settings, system prompts, and permissions; then issue a request such as “Remind me to send the file at 8 tonight” or “What is on my calendar today?” For Mac inference, launch PhoneClawGateway.app, allow macOS local-network access, and choose Ollama, Codex CLI, or Antigravity CLI in Gateway. Put the iPhone and Mac on the same LAN, pair the Mac under “Mac Remote Inference,” and choose the remote model.

How does this agent compare with similar options?

Remote inference is not tied to a single backend: PhoneClaw Gateway can select Ollama, Codex CLI, or Antigravity CLI. The documented Ollama path keeps inference on the Mac; CLI and other upstream-provider paths follow the selected provider's data practices.

FAQ

Does it require the internet or cloud inference?
No. The README describes local inference and on-device Skill calls as the default path. Web search, URL reading, and Mac remote inference are explicitly triggered capabilities.
Are there per-use fees or token limits for local operation?
The README specifically says LiveLand runs on a local model by default, without cloud inference, per-use billing, or token limits. It does not document costs for downloads or third-party providers.
Why did no permission dialog appear after installation?
A prompt normally appears only when the relevant Skill reaches the system API. If access was previously denied, it must be enabled again in iOS Settings.
Why can a model fail to load after switching?
Confirm that the filename matches `allModels` in LLM/Models/PredefinedModels.swift, that a shell-installed model finished downloading or a bundled model is in the app package, and that the device has sufficient memory.
Why can't the iPhone discover the Mac Gateway?
Verify that PhoneClawGateway.app is running, macOS local-network permission is allowed, both devices are on the same Wi-Fi network, and the macOS firewall permits the app to receive LAN connections.

Related agents