PinkCollab is an Android client for Oh My Pi (OMP). Use OMP on your own computer from your phone.
- Read and continue existing conversations without manual imports.
- Start sessions in your projects and switch between them.
- Keep OMP and its model-provider configuration on your computer.
On your phone, install the Android APK.
On your computer, you need a working OMP installation, Node.js 18+, and Tailscale for the default setup. Use the same OS user that owns your OMP configuration and conversations; omp --version must work for that user.
npm install -g pinkcollab@latest
pinkcollab --versionUse the APK and CLI from the same release. For version mismatches or existing installations, see installation and upgrade checks.
In your terminal, change to the directory containing your projects, then run:
pinkcollab setupSetup confirms that directory as a workspace root, guides Tailscale sign-in and Funnel approval, and starts the Gateway in the background. It does not install OMP or Tailscale. Scan the QR code with the Android app; you can then close the terminal.
The default connection is public HTTPS via Tailscale Funnel. Your tailnet must permit Funnel; app access requires pairing credentials, not a secret URL. Your phone does not need Tailscale. For private access, see Tailscale Serve or your own HTTPS proxy.
For a fixed Linux server with your own HTTPS reverse proxy (Caddy/nginx), Tailscale is not needed:
pinkcollab setup \
--transport external \
--public-url https://pink.example.com \
--workspace /srv/projectsSee external HTTPS setup for proxy requirements and automation.
On Windows, use a normal terminal as your OMP user. The Gateway starts automatically when you log in; no Windows password or service login permission is needed. Signing out stops it, while closing the terminal or locking the screen does not. See Windows login startup and macOS Tailscale installation.
- Continue a conversation: open an On host entry in Tasks. Its project must be inside your configured workspace roots.
- Start a new session: open Workspaces, choose a directory, and create a session.
Close the corresponding OMP instance on your computer before continuing a conversation from the phone. This is not a takeover of a running terminal session; do not use the same conversation elsewhere while PinkCollab owns its runtime.
Send a prompt and check that OMP responds. Swipe to switch sessions; use Stop to interrupt a turn and Exit to end its runtime.
If connection or prompts fail, run pinkcollab doctor and see setup troubleshooting. For missing conversations, see history discovery.
| Task | Command |
|---|---|
| Check the host | pinkcollab |
| Diagnose problems | pinkcollab doctor |
| Pair another phone | pinkcollab pair |
| Update the Gateway | pinkcollab update |
| Add project roots | pinkcollab setup --workspace /path/to/code --workspace /path/to/work |
To upgrade, install the APK and CLI from the same release, then run pinkcollab update. It applies this CLI to the installed Gateway and does not change workspaces, the public URL, or pairings. A changed running Gateway restarts and stops active OMP runtimes; finish current work first. Stopped Gateways stay stopped unless completing an interrupted restart or reloading a still-loaded macOS agent. See upgrade checks.
- Your computer must stay awake and reachable. See the macOS lid-close FAQ and background-service behavior.
- OMP runs with the Gateway user's filesystem permissions. Workspace roots are not an OS sandbox.
- Removing a host in the app does not revoke access. Use
pinkcollab clients, thenpinkcollab revoke --client <clientId>on the host.
- Deployment and troubleshooting: networking, pairing, services, upgrades, and CLI/configuration
- Session interface: status display and interaction behavior
- Architecture · Protocol 3
- Development · Release publishing

