PinkCollab.

OPEN SOURCE AI TOOL

Android client for
Oh My Pi (OMP).

Oh My Pi is a coding agent for the terminal. PinkCollab starts a real omp --mode rpc-ui process on a host you own, so you can prompt, follow, interrupt, and stop it from your phone.

Get started Explore the source
Oh My PiAndroid clientRust gatewayYour own hosts
home-pc Connected
dev-server Connected
PinkCollabP
START · FOLLOW · ANSWER

Sessions

2 hosts
NEEDS YOUR INPUT now

Review database migration

dev-server / projects/api

Ready to apply the migration.
Would you like to proceed?

Continue the conversation in the app

A decision from you keeps work moving.

You’re in the loop.Live replies. Clear session states.
Illustrative session view · try the tabs

One phone.
Every workspace.

Start a sessionFollow it liveAnswer when needed

FROM YOUR DESK TO YOUR POCKET

Three steps to a running session.

Named exactly as they appear in the Android app.

01

Choose a workspace.

Open Workspaces, browse the roots a paired host allows, and pick the project directory you want to work in.

02

Send the first prompt.

Your prompt spawns omp --mode rpc-ui inside that directory. The session joins the list right away with its live status.

03

Follow it live.

Watch streaming replies and tool activity, then use Send, Stop, or Exit while the app is connected.

No terminal emulator, no editor: PinkCollab starts and controls OMP sessions on your host. It does not attach to a terminal session.

LET’S GET YOU CONNECTED

Built for your setup.
Open from the start.

Download the Android release APK, install the Gateway on the computer that will run sessions, and install and configure Oh My Pi (OMP) separately on that host. Then pair the phone and create your first session.

On your host
Oh My Pi installed and configured separately, with omp --version working in your terminal.
Gateway install
Node.js 18+ for the npm package; Rust 1.89+ only if building from source. No Rust toolchain is needed for the prebuilt downloads.
Android app
The release APK needs no Android build toolchain. JDK 17+ and Android SDK 36 are only for building the app yourself.
Read the setup guide Download the release Android APK Install the signed APK and Gateway from the same release; Gateway binaries and checksums are available there too. A debug APK may require uninstalling the release app first because it uses a different signing key.
Install the gateway

Install with npm

Easiest · Node.js 18+
npm install -g pinkcollab@latest

Installs the released native Gateway binary without Rust. Prefer a direct download? Choose your platform’s Gateway binary and verify it against SHA256SUMS on the latest release.

Build from source (optional)

Needs Rust 1.89+
git clone https://github.com/3xian/PinkCollab.git
cd PinkCollab/gateway
cargo build --release --locked --bin pinkcollab-gateway
Next steps
  1. Allow a project directory that already exists: pinkcollab init --workspace /absolute/path/to/projects.
  2. Publish it with Tailscale Funnel: pinkcollab funnel. Tailscale runs on the host. The phone does not install Tailscale.
  3. Start the Gateway with pinkcollab serve and leave that terminal open.
  4. In another terminal, print a pairing code with pinkcollab pair.
  5. Open PinkCollab on Android, scan the code within 5 minutes, choose a workspace, create a session, and send your first prompt.

For a source build, run ./target/release/pinkcollab-gateway from gateway/ instead of pinkcollab, and build the matching Android app from source. For a direct release download, use ./pinkcollab-gateway-<your-platform> from its download directory after chmod +x on macOS/Linux; on Windows PowerShell use .\pinkcollab-gateway-win32-x64.exe from its download directory.

Deployment and networking guide

FROM A TAP TO A RUNNING AGENT

Your phone starts the session.
Your host stays in control.

PinkCollab is a direct bridge to OMP — not another agent and not a cloud relay.

IN YOUR HAND

Android app

Start, follow, answer

HTTPS · WSScommands + live events
YOUR COMPUTER OR SERVER
RUST SERVICE

PinkCollab Gateway

Auth, sessions, streaming

spawnNDJSON
ONE PROCESS PER ACTIVE SESSION

Oh My Pi

Plans, tools, coding

Host-local state
Allowed workspacesSession metadataOMP session files
provider APImodel requests
YOUR ACCOUNT

Model provider

Your chosen models

01 · StartThe Gateway launches a real omp --mode rpc-ui process.02 · ControlCommands go in; structured events stream back to Android.03 · OwnWorkspace files and session records live on your host; OMP sends model requests to your provider.
Architecture

Your machines stay yours. OMP runs on your hosts. Model provider credentials are configured there, not on the phone; OMP may send them to your provider when making model requests. Pair devices with a single-use QR code and revoke access when you need to.

Deployment guide

BEFORE YOU START

What PinkCollab does not do yet.

So the first surprise isn’t a surprise.

  • Managed, not adopted. A terminal session cannot be attached; PinkCollab manages the sessions it spawns itself.
  • Restarts are not resurrections. Running OMP processes are not restored when the gateway restarts — those sessions show as offline. History can still be read from OMP's session file; the live event stream is not replayed.
  • Notifications are not implemented. A session waiting on your input only shows it while the app is open.
  • No terminal, Git client, code editor, or cloud relay. PinkCollab is a bridge to OMP on your own hosts, not an IDE and not a middleman.

POWERED BY

Oh My Pi does the work.
PinkCollab keeps you in the loop.

Oh My Pi (OMP) is a coding agent for the terminal: subagents, plan mode, LSP and DAP, hindsight memory, hashline edits, and time-traveling rules, on a native Rust engine. PinkCollab adds no agent of its own — it drives OMP on your machines and carries the conversation to your phone.

Meet Oh My Pi
  • Real OMP processes. Sending the first prompt from Android starts omp --mode rpc-ui on the host that owns the code in the current source version.
  • Host-side credentials. Configure model provider credentials on the host, not the phone; OMP may transmit them to your provider for model requests.
  • Choose your reachability. Funnel needs Tailscale on the host; private Serve needs it on the host and phone. You can also use your own HTTPS reverse proxy.

Work keeps moving.
So can you.

Made in the open. Join us on GitHub