Capability map

Everything it does. And the edges it keeps.

A compact reference for the product as it ships today. Dependencies sit beside the features that need them; limits get the same weight as capabilities.

01

Pairing, hosts, and access

Pair by QR or manual code, then manage each device from either surface.

  • Short-lived, single-use pairing code
  • Phone pins the stable Mac public key
  • Mac stores only a hash of the bearer token
  • Several Macs in one filterable project list
  • Immediate device revocation and live-stream drop
  • Face ID, Touch ID, or passcode app lock
02

Projects

A project points to one local git repository on one Mac.

  • Node, Rust, Go, Flutter, Python, and Ruby detection
  • Workspace-aware monorepo package roots
  • Editable setup, run, and archive scripts
  • Command buttons with working directories and ports
  • Per-project agent and notification defaults
  • Guarded detach with a preservation receipt
03

Workspaces

Each unit of work owns a worktree, branch, snapshotted base, processes, and git state.

  • Chat-first, terminal-first, or GitHub issue-backed
  • Several chats and terminals in one tab strip
  • Persisted drafts, unread state, and closed transcripts
  • Merge & Close or confirmed Discard & Close
  • Failed merges preserve the worktree and branch
preparingThe setup script is running
activeNormal work and review
needs attentionSetup failed; inspect or retry
needs mergeClose hit a conflict; worktree preserved
closedMerged or explicitly discarded; history readable
04

Agents

Claude Code, Codex, and Grok use one normalized control surface.

  • Ready, needs login, and not installed states
  • Model catalog advertised by each backend
  • Backend-specific reasoning effort rungs
  • Plan mode or Work mode
  • Attach files, mention paths, and pin context
  • Stop, steer, context meter, and compaction where supported
Model, effort, Plan and Work controls sourced from the selected backend
05

Review

The Mac renders live file and diff views from the workspace you are actually changing.

  • Combined and per-file diffs
  • Fork-point and last-commit anchors
  • Whole files, commit history, and commit-scoped diffs
  • Mac-rendered syntax highlighting in both palettes
  • Markdown preview and source mode
  • Span selection with a note for the agent
  • Stale-safe single-file revert
Host-rendered diff with selected lines and an Ask agent note
06

Execution

Commands, tracked processes, and interactive terminals stay attached to the workspace.

  • Command buttons grouped by purpose
  • Ad-hoc commands and a real PTY
  • Completed, stopped, and crashed outcomes
  • Replayable ANSI output after reconnect
  • Allocated port for the project run script
  • Open the live app over your tailnet
07

Git and GitHub

Local git is built in. Issues, pull requests, and PR review require a GitHub remote and the gh CLI signed in on the Mac.

  • Update from base with abort or agent-assisted conflict handling
  • Editable drafted commit messages
  • Push with remote and ahead or behind state
  • Issue-backed workspaces and editable trailers
  • Editable PR title, body, base, and draft flag
  • Automated PR review from a disposable worktree
  • Host-owned posting with repaired anchors and duplicate guards
08

Recipes and automations

Reusable prompts live in files; scheduled work uses five-field cron in the Mac’s timezone.

  • Global and repository-scoped Markdown recipes
  • Content-hash trust on first use
  • Edited files require approval again
  • Unapproved overrides fall back to the built-in
  • Command, command-button, or recipe schedules
  • Catch-up, manual run, and durable run history
  • Fresh worktrees for work-producing runs
New automation sheet scheduling a shell command with kind, repeat, and catch-up controls
09

Staying informed

Activity separates what needs you, what is running, and what happened recently.

  • Cross-host and multi-project filters
  • Opt-in push per device and project
  • Daily quiet hours in the phone’s timezone
  • Generic lock-screen copy
  • Closed-vocabulary payloads with opaque routing ids
  • Authoritative state read from the Mac after opening
10

What PRCHD deliberately doesn’t do

The boundaries are part of the product, not a backlog disguised as fine print.

  • No multi-user or team collaboration
  • No hosted repositories, cloud dev environment, or PRCHD compute
  • No Windows, Linux, or Intel Mac host
  • No offline queue for new work while a Mac is unreachable
  • No speech service; voice input is keyboard dictation
  • No per-tool approval prompts; choose Plan or Work first
  • No phone merge editor for close-time conflicts
  • No public preview tunnel
  • No currency estimator; context and tokens only
  • No event-triggered automation; schedules use cron

Put the whole loop on your phone.

Start with the Mac host, then pair the phone over your tailnet.