Your memory.
Your agents.
In your pocket.

A native iPhone app for the phren store you already keep on GitHub — and for the coding agents running on your own computers. Nothing goes through a Phren server, because there isn't one.

Status: direct install and private TestFlight-style delivery from the repo. Not yet on the App Store.

What you need

1. A phren store on GitHub. The repo that holds your ~/.phren store (phren team init or phren store add --remote <url> from your computer). The app signs in with a fine-grained GitHub token scoped to that repo — see Support for the exact permissions.
2. Phren Hook on each computer that runs your agents: npx --yes @phren/cli@0.2.14 bridge install. It is a local helper, not a service in the cloud. Setup and troubleshooting live on the Phren Hook page.
3. SSH, and Tailscale away from home. The phone authenticates with a per-computer SSH key it generates itself and verifies the computer's host-key fingerprint the first time. No public port, Funnel or relay.

Agents and terminals work without a GitHub sign-in. Memory needs one; you can dismiss that setup and come back to it.

Projects and memory

Projects lists every project in every attached store, with counts, claim badges from stores.yaml, and a read-only marker on tiers like global. Inside a project: findings grouped by date (journal entries from team stores included), notes by day, pinned truths, the summary, skills and agent instructions, and the archive of consolidated topics — fetched only when you open one.

Tasks is the workload view: Backlog, Active and Done with search, filters (age, priority, project, store) and sorting; swipe to Start, Backlog or Done; select several and move them across stores at once. Search runs across every store. The memory graph is the same 3D viewer as the web UI and VS Code, focused on one store at a time.

Edits — add, edit, promote, review decisions, skill toggles and moves — apply instantly on the phone, queue offline, and flush to GitHub as commits authored by you, one commit per file. Team stores get journal-append semantics exactly as the CLI does. Anything that can't be pushed shows under Settings → Needs attention for retry or discard.

Sessions and chat

Agents opens with the sessions from every saved computer — working and waiting first, then idle, done and other open tabs — each row naming its computer, project, agent and state. The chat header shows the agent's glyph with its connection state, the pane's title, and the project · model · branch. From there: repository changes, Herdr workspaces, project memory, skills and the graph.

• Chat streams the agent's own transcript: progressive text, tool calls as compact rows that expand to the full command and a terminal-style output block, patches drawn as diffs, what each shell command changed on disk listed under it as Updated file (+n −m) with the diff inline (Phren Hook snapshots the working tree — and the phren store — around every shell call), images, real usage counters, Stop, and approval prompts you can answer from the phone.
• Queue while it works. A message typed while the agent is busy waits above the composer with Send now, Edit and remove; the first one goes out when the turn ends. Slash commands go straight through.
• Repository changes follow VS Code's Source Control view: staged and unstaged files with status letters, then a diff editor with line numbers, tinted rows, changed-character highlights, next/previous change, and inline or side-by-side layout. From a tool card, See repository changes also covers the paths that command named — a file in another repository such as the phren store, or one a hook already committed — each shown under its own repository with the commit.
• Terminals open the exact Herdr pane, with a compact key dock, Ctrl-hold shortcut panels you can customise, pinch to resize, hold to select, and image uploads into the running agent.
• Web servers preview the development servers a computer is running, tunnelled over SSH so loopback-only apps work from the phone.
• Simulators lists every iOS simulator booted on a computer with its live screen (Phren Hook on macOS); open one and tap its screen to tap the device, press Home or Lock, type, launch an installed app, open a URL, or shut it down. Touches use a small helper the Hook builds with Xcode's swiftc; macOS asks once for Accessibility on it. Files puts any file on a computer through Phren Hook and copies its path for an agent.
• Settings follow a terminal app's shape: Theme, Fonts & Size (curated fonts on demand or your own from Files), Chat, Advanced (cursor, keep screen on, autocorrection); Toolbar, Shortcuts, Keyboard (⌘K ⌘V ⌘J ⌘⇧M, Option as Meta), Gestures, Speech (language, word replacements); Phren Hook, Notifications, Show on Agents.
• Account usage shows Claude and Codex account limits and reset times per computer.

Capture from anywhere

"Hey Siri, add a task to phren" works from a locked phone. Add Task and Add Note appear in Shortcuts and can sit on the Action Button. In the app, a voice sheet dictates notes and tasks with on-device recognition where the device supports it. Settings → Recent captures shows where every capture landed and whether it has synced.

Home Screen and Lock Screen widgets show your memory count and top active task without opening the app. Permission requests from an agent can appear as a Live Activity with Deny and Approve.

Themes and settings

Charcoal (default), Amethyst, Graphite and Slate, plus custom named themes. The chat transcript reads in plain white and grey in every theme, with the accent kept for Send and Stop. The terminal toolbar and Ctrl-hold panels are yours to arrange. Attach several stores — personal and team — and the tabs show a merged view with a store filter.

Install

The app is built from apps/ios in the repo. Today it installs directly on a paired iPhone (python3 apps/ios/scripts/deploy-phone.py) or over a private Tailscale link from your own Mac; the README covers signing, XcodeGen and the OTA installer. An App Store submission is in progress. When it ships, this page and the Support page will say so.

Where your data goes

Store data is read from and written to GitHub with your token. Session data is read from your own computers over SSH. The developer receives nothing — no analytics, no crash reports, no telemetry. The privacy policy lists, item by item, what the app keeps on the device and what leaves it.