English · 한국어
Securely drive the code-agent CLIs running on your Mac, from your phone over LTE/5G.
Dual channel (SSH-first + Tor fallback) + a native iOS app. Zero external servers · zero paid infrastructure · a 100% OSS stack (for the two apps). Free, with an optional Pro tier.
You pick which code-agent CLI to use per session from a picker (the daemon spawns the CLI binary installed on your system via node-pty).
- Claude Code (Anthropic)
- Google Antigravity (
agy) (Google) - OpenAI Codex (OpenAI)
- GitHub Copilot CLI (GitHub)
- OpenCode (open source · OpenAI-compatible endpoint)
Model inference itself is sent by each agent CLI directly to its own provider's API — Pocket Sisyphus does not relay that traffic.
The principles below are properties of «the two apps you run yourself — iOS · Mac». The data plane of those two apps (phone ↔ your Mac) never passes through any maintainer infrastructure. The web (
web/) in this repository is just a static intro page (landing) — it ships only as a GitHub Pages build with no backend/DB — so it is not subject to the principles above. There is no separate community feature — questions, sharing, and bug reports all run on the public repo's GitHub Discussions (the same destination the iOS in-app «Community» and the web footer point to). For scope, see Project boundaries below.
- 🎯 A «one-person legion» tool — for solo developers & founders: drive code agents «solo or as a legion» right from your phone, and build and run a service alone — no team, server, or outsourcing. The «zero external infra · zero cost · 100% OSS stack» below is the very foundation of this «self-sufficiency» — the user must be able to keep running it to the end even if the maintainer disappears (so the principles below do not conflict with this goal; rather, they exist for it).
- ⛔ Zero external server dependency: no maintainer infrastructure. Uses only the Tor distributed network + public-IP echo (ipify, etc.).
- ⛔ Zero paid services: no domains/certificates/relays/SaaS whatsoever.
- ⛔ Zero external app dependency: iOS embeds
Tor.frameworkinside the main process; Mac bundlestor+sshdbinaries inside the daemon. - ✅ The data plane is SSH. In an environment where direct SSH reaches (a retail router + IPv6 enabled / UPnP), latency is 10–50ms.
- ✅ Tor fallback in CGNAT/UPnP-blocked environments works automatically — zero-config for the user.
- 🔒 «Same Wi‑Fi only» mode (opt-in, fail-closed): when on, the phone ↔ Mac connect directly only via the private address on the same Wi‑Fi, and Tor / public IP / external outbound are all blocked (explicitly blocked when off-LAN). On first launch you choose the connection mode (Anywhere (Tor) / Same Wi‑Fi only) — you can still pair and use over LAN even on networks where Tor is blocked.
- ✅ Dual cryptographic identity assurance:
.onionv3 (Ed25519 hash) + SSH host-key fingerprint (pinned in the pairing QR). - ✅ 100% OSS stack: BSD/Apache/MIT components only — this means it is built with OSS, not that the project «itself» is OSS (the license is the EULA).
- ⛔ No VPN entitlement: NEPacketTunnelProvider is not used → Apple Guideline 5.4 is not triggered.
This repository contains three projects, and the scope of the «zero external infra» principle above differs across them:
| Project | External-infra dependency | Why |
|---|---|---|
iOS app (ios/) |
⛔ 0 | The «private» data plane from the user's phone → their Mac. Zero maintainer server/SaaS. |
Mac app (mac/) |
⛔ 0 | The user's host/daemon. Self-sufficient with bundled tor+sshd — no external infra needed. |
Web (web/) |
Static hosting only | Just a static intro page (landing). Ships only as a GitHub Pages build, no dynamic backend/DB — a lightweight marketing page, separate from the apps' «zero infra» principle. |
The community feature was deliberately not built — the public repo's GitHub Discussions stands in for it (an external platform outside the repo, unrelated to «zero infra»).
In short, «zero external infra» is a principle that protects the private data path of the two apps the user runs, not one that also binds the public intro site — because an intro page inherently presumes external access.
iPhone (Pocket Sisyphus.app)
├─ Tor.framework (in-process in the main process, lazy)
├─ Citadel SSH client (swift-nio-ssh)
└─ ConnectionManager — happy eyeballs:
direct_ipv6 / direct_ipv4 / tor_onion tried in parallel, fastest wins
│
│ outbound TCP (direct SSH) or outbound TCP (Tor)
▼
┌──────────────────────────────────────┐
│ direct SSH or Tor Network (fallback) │
└────────────────┬─────────────────────┘
│ inbound
▼
Mac (Pocket Sisyphus.app, menu-bar only)
├─ tor process (hidden service — endpoint lookup + SSH-over-Tor 22 exposed)
├─ embedded sshd (OpenSSH portable, listens on 22022 — direct-tcpip only)
└─ daemon (Node + Hono + WS, 127.0.0.1:7777)
└─ PTY spawn → claude / agy / codex / copilot CLI
Zero cloud hops. On a retail router (UPnP enabled) + IPv6 environment it needs zero router config; default KT/LG routers (UPnP OFF) need UPnP enabled just once (or it works via Tor fallback). iPhone ships via the App Store; Mac ships via Developer ID + notarized DMG direct download + Sparkle in-app updates.
Get it on the App Store: Pocket Sisyphus on the App Store. The Mac companion app below must also be installed and running — the iPhone app and the Mac app work as one set (keep their versions matched).
Paste one line into your terminal and the latest version installs automatically into /Applications and launches — zero prerequisites (only curl, which ships with macOS, is needed):
curl -fsSL https://raw.githubusercontent.com/Wayne-Kim/pocket-sisyphus/main/install.sh | bashinstall.sh is a tracked file in this repository (install.sh) — you can read the source before piping it. What it does: read the latest DMG direct link from the latest release's appcast.xml → download → verify the DMG SHA-256 against the published value in appcast.xml (or the release notes) + verify the Apple notarization staple & code signature (aborts on failure) → mount → copy the .app into /Applications → unmount → launch. The DMG is Apple-notarized + stapled, so it passes Gatekeeper with no warning. After install, updates are detected automatically by the app's built-in Sparkle.
For a manual install, grab the DMG from releases/latest and drag the .app into Applications.
- Architecture
- Threat model — assets · trust boundaries · mitigations · accepted residual risk
- Capability-cap guardrails — the spec for blocking the lethal trifecta on the personal-data path
- Security policy · vulnerability reporting — supported versions · reporting process · response SLA (
/.well-known/security.txt)
The Mac desktop app and the iOS app operate as one «set». So that users can identify a «compatible pair» at a glance, the marketing version (MAJOR.MINOR.PATCH) of the two apps is always kept identical.
| Class | When to bump | User impact |
|---|---|---|
| MAJOR | Mac ↔ iOS compatibility is broken. The old app rejects the new one / vice versa. | Both apps must be updated immediately for pairing/sessions to work. Permanently cut off from the old pair. |
| MINOR | One side added a new feature but the old side still runs its existing features. | Updating only one side late is OK for basic use; you just can't use the new feature. |
| PATCH | 100% compatible. Bug fix / internal refactor / text change. | Updating either side late doesn't matter. |
The compatibility handshake itself works via the /api/version route + a set of capability strings — for the detailed model, see the module docstring in mac/daemon/src/version.ts.
The two apps' marketing version is always kept identical. Version bumps and deployment (TestFlight / Developer ID DMG) are a maintainer-only procedure — they are not kept in the public repository.
Where users check their own build at runtime:
- Mac: click the menu-bar icon → in the popover header, to the right of «Pocket Sisyphus»,
vX.Y.Z (build) - iOS: top-left ⚙ on the Sessions screen → at the bottom of the menu,
vX.Y.Z (build)
build is a monotonically increasing integer stamped automatically by the deploy script every deploy via git rev-list --count — it always +1s even without a marketing-version bump. The «marketing version + build number» pair is used to pin down «the exact build at the time of an issue».
iOS and Mac have different distribution channels.
| Platform | Channel | Reason |
|---|---|---|
| iOS | TestFlight (App Store Connect) | iOS has no install path other than the App Store / TestFlight |
| Mac | Developer ID + notarization + direct DMG download + Sparkle | The daemon must access arbitrary repos in the user's home + all of ~/.claude/projects, which inherently conflicts with the sandbox → MAS abandoned |
The deployment procedure (API key/certificate setup, signing/notarization, upload) is maintainer-only and not published. Operational docs live in a maintainer-only
docs/ops/(not included in this repository). For ordinary user installation, see the "Install" section above.
The apps are free to use. Only advanced features are gated behind an optional Pro (subscription or lifetime license), and model-inference cost is billed directly by your chosen AI provider — Pocket Sisyphus does not relay it or add a margin.
| Item | Cost |
|---|---|
| Pocket Sisyphus app (iPhone + Mac) | Free |
| Pro — workflows · scheduling · terminal/local LLM · live preview · monitor mirroring | Optional · subscription or lifetime license (App Store) |
| Code-agent CLI usage fees | Billed directly by each provider (Anthropic / Google / OpenAI) — does not pass through us |
The maintainer «infrastructure» cost is $0/yr for the two apps (→ Core principles). The web (intro site) uses external hosting and the community runs on GitHub Discussions, so they are separate — see Project boundaries.
The source is public, but the license is proprietary — this is not open source. Source being public does NOT grant any commercial-use rights. Full text: LICENSE.md.
- ✅ Anyone may view/clone the source, build it themselves on their own PC for personal, non-commercial use, modify it for personal use, and modify it for the purpose of contributing (PRs).
- ⛔ Redistribution to third parties of the source/builds, or commercial use/sale in any form.
- The rights to use, distribute, and sell commercially are reserved exclusively to the copyright holder (Wayne Kim). Official builds are provided only through the App Store / Mac distribution channels.
- Contributing requires agreeing to
CLA.md— you assign the economic copyright in your contribution to the copyright holder (falling back to an exclusive license in jurisdictions where assignment is not permitted). This is what makes «commercial rights belong solely to the copyright holder» hold airtight, even through contributor code. - New contributor?
CONTRIBUTING.mdis the one place that covers how to build each project, the checks your PR must pass, the SSOT contracts to respect, and the CLA.
The «100% OSS stack» (in Core principles above) means it is built with bundled dependencies/components (BSD/Apache/MIT), not that the project «itself» is open source. The code in this repository is governed by the EULA above.




