Take your agents for a walk.
Paceman brings Codex and Claude Code activity from your Mac or Omarchy computer to your iPhone Lock Screen and Apple Watch, so you can step away while your agents build.
You can also respond to supported questions and approval requests on iPhone and Apple Watch. Unsupported requests continue in the agent’s app; see coverage and limits.
Your phone and Apple Watch are just the start. Paceman is an open personal gear system for agentic engineering on the go, which you can extend to hardware you choose, hack, or build.
Paceman is in alpha. macOS and Omarchy installers are available via GitHub releases, and Paceman iOS is available through TestFlight.
- Get Paceman for iPhone on TestFlight.
- Download the desktop client and follow the Mac setup or Omarchy setup guide.
- iPhone: iOS 18+.
- Computer: Apple Silicon Mac with macOS 15+, or Omarchy 4.0+ with Python 3.11+ and user systemd.
- Agent: Codex or Claude Code 2.1.196+ installed and running on a computer with Paceman set up and paired to your iPhone.
- Claude Code responses: an eligible claude.ai account with Remote Control enabled and active for the session. API-key-only and alternative-provider setups do not qualify; see Anthropic’s requirements.
- Connection: Tailscale on your computer and iPhone.
- Apple Watch (optional): watchOS 26+. Session browsing, request review and answers require a live connection to the paired iPhone. Codex usage can update directly for complications; see Watch connections.
Reviewed hooks provide activity monitoring separately; they do not enable responses.
Each computer runs a local service. The iPhone reads activity and usage snapshots and exchanges supported requests and answers over authenticated HTTPS through Tailscale, so the service remains reachable away from the local network without exposing its API to the public internet.
The service listens on loopback. Paceman configures Tailscale Serve and issues a separate credential for each paired phone. Notifications, Live Activities and Apple Watch activity updates use Paceman's relay and Apple Push Notification service.
- Cloud-only sessions are unsupported.
- Sessions started remotely but running in Codex desktop on a Mac can show activity while approvals are inaccessible. Try opening the thread in Codex on that Mac, then check Paceman again. An assistant with access to your Mac may be able to do this for you.
- Mac: Build and install from source.
- Omarchy: Install from a Git checkout.
- iPhone: Build with Xcode.
Paceman can extend to gear you choose or build:
- Pebble Time 2 running modified PebbleOS firmware to work as a Paceman accessory.
- ESP32-S3 watch with custom firmware focused on agent activity.
To connect an accessory, follow the setup guide. To adapt or build your own, start with the accessory protocol and the firmware above.
- Activity snapshots and notification payloads contain status, Codex usage and limited metadata, including optional session titles. They exclude prompts, agent replies and tool arguments. Optional project labels can appear on your Lock Screen.
- Supported request content and your answers travel privately between your computer and paired iPhone, and through the iPhone to Apple Watch. They are excluded from activity snapshots and Paceman’s relay/APNs payloads.
- Claude Code requests and responses also use its existing Remote Control connection through Anthropic.
See data and lifecycle for data flow, and the privacy policy for service providers, diagnostics, retention and privacy requests.
- Architecture: how the system fits together.
- Data and lifecycle: privacy, storage and recovery.
- Push delivery: notifications and background updates.
- Protocol: source and accessory interfaces.
| Path | Purpose |
|---|---|
service/ |
Source service and notification relay |
macos/ |
Mac client and agent hooks |
omarchy/ |
Omarchy client and agent hooks |
ios/ |
iPhone and Apple Watch apps |
firmware/pebble-time-2/ |
PebbleOS integration |
firmware/esp32-watch/ |
ESP32-S3 firmware and simulator |
tests/, scripts/ |
Checks and development tools |
- GitHub Issues for bugs and suggestions.
- Private security reports for vulnerabilities.
- Development guide for builds and tests.
- Apache 2.0 for original Paceman code, documentation and artwork.
- Third-party notices for imported code and assets.

