Get Yah AI on your phone and your computer
Yah AI is coming to the App Store for iPhone, iPad and Mac. It is not there yet, so the phone side of this page is a waitlist. Two free things for a computer install today: the desktop app, which lets your phone’s agent work on your computer, and the connectors, which let developers bring an AI tool they already run into the app as a friend’s agent. Every command below matches the reference page at relay.yahai.app/help.html.
iPhone, iPad and Mac, from the App Store
Yah AI is not on the App Store yet. The listing is being prepared for review, so there is no store link to give you and no date to promise. Leave an email and we will write once, when it is available.
Join the waitlist
One email, one message.
What the App Store build is
- One purchase, three devices. Yah AI runs on iPhone, iPad and Mac, and one purchase covers all three.
- Called YahAi on the home screen. That is the listing’s name; Yah AI is the product.
- No account. There is no sign-up and nothing to log in to. Yah Pro is a normal App Store purchase that works on your iPhone, iPad and Mac; you manage or cancel it in your phone’s subscription settings, and Family Sharing is on.
- A brain is included; no key needed. Setup downloads the app’s own brain — about 1.7 GB, once — and every chat runs on the phone from then on. It runs on every supported iPhone. A Claude, Z.AI or DeepSeek key is an optional extra.
- Free forever: on-device chat, every model in the catalog, and nearby agents over Bluetooth or local Wi‑Fi. Yah Pro covers the parts that run on the internet — see what is Pro.
- Requires iOS 18.6 or later (iPadOS 18.6 on iPad, macOS 15.6 or later on the Mac). An iPhone 12 or newer is recommended; an older phone that runs iOS 18.6 gets the app too, with the lightest models and shorter conversations.
- Not on the Mac version: Workout Quest and Apple Health. Kokoro neural voices are iOS-only; on the Mac the assistant speaks with Apple’s built-in voices.
- Apple Intelligence is optional. On a device that supports it, two things use it: the assistant can answer with Apple’s own on-device model (iOS 26 or later), and Image Playground can make pictures (from iOS 18.6). The app never depends on either.
Which iPhone
Any iPhone that runs iOS 18.6 can run Yah AI; an iPhone 12 or newer is recommended. At first launch the app sizes itself to the phone in your hand: a newer phone with more memory can run larger models and hold more of a conversation at once, and an older one gets lighter models and shorter conversations. The device step of setup shows you what your phone gets. Models are downloaded on first launch; nothing is bundled in the app.
Your computer: the desktop app
A connector brings another agent into the mesh; the desktop app gives your phone’s agent a second machine to work on. It installs the Yah Desktop service — the background helper your phone pairs with to run coding sessions on that machine, watch them, and answer their permission prompts — and a window with five views: Sessions, Files, Rooms, Agents, This Machine. The window is ready-made on macOS and Linux; on Windows the service installs today and the installer does not yet ship a window. One command per platform; the tabs follow the device you are reading this on.
Not the App Store app. On macOS this command installs /Applications/Yah AI.app, the desktop app that runs the Yah Desktop service for you. The App Store build for Mac — listed as YahAi and included in the one purchase with the iPhone app — is a different program, and it is not out yet. The desktop app is free and is never sold separately; the phone it pairs with is what needs Yah Pro.
macOS
Needs macOS 14 or later, and curl and tar, both part of every Mac. Run it in Terminal as yourself, not with sudo.
curl -fsSL https://relay.yahai.app/desktop | shmacOS — installs Yah AI.app into /Applications and the service, then opens the app
What this command does
- Downloads the app and its background helper, then opens the app. Nothing else to run.
- The first install takes a few minutes.
- Then pair from the phone: Yah AI → Settings → Yah Desktop.
The installer prints every step as it goes; nothing is hidden. Step by step, and what each file is for.
Linux
Needs curl and tar. Run it as your own user, not root — the service and the app both install per-user.
curl -fsSL https://relay.yahai.app/desktop | shLinux — the same command; installs the background helper and, where its prerequisites are present, the window
What this command does
- Downloads the background helper and, if your desktop has what the window needs, the window too. Without it the helper runs regardless, and your phone can pair and drive the machine now.
- The first install takes a few minutes.
- Then pair from the phone: Yah AI → Settings → Yah Desktop.
No window is needed to pair — one short command on this machine hands you the 6-digit code. How, on Linux and Windows. Step by step, and what each file is for.
Windows
Run it in PowerShell as your own user. Everything it installs lands under your own profile.
irm https://relay.yahai.app/desktop.ps1 | iexWindows PowerShell — installs the Yah Desktop app (Start menu) and the background helper, and sets the helper to start at logon
What this command does
- Downloads the background helper, starts it quietly with no window, and sets it to start again at every logon.
- The first install takes a few minutes.
- Then pair from the phone: Yah AI → Settings → Yah Desktop.
The service is what installs today. The installer does not yet ship a Windows window. Your phone pairs to the service, starts coding runs on this machine, and sees every session without one.
No window is needed to pair — one short command on this machine hands you the 6-digit code. How, on Linux and Windows. Step by step, and what each file is for.
Pair the phone
On the phone: Yah AI → Settings → Yah Desktop. Turn the node on, tap the machine in the list — it is found on its own when both are on the same Wi‑Fi — and enter the 6-digit code the desktop app shows (on a Linux or Windows machine with no window, one short command on that machine hands you the code). You do this once per machine; after that the phone reconnects on its own. Pairing a computer is a Yah Pro feature.
Then choose the project folder and who plans the work: a mesh agent already paired to your phone (Claude Code, OpenClaw, Hermes Agent or OpenCode), a model file on the computer that works with no network, or a cloud model called from the phone whose key never leaves it. A run has no fixed limit — it ends when the task is done, when you press Stop, or when the app catches a step that has stalled. By default the agent asks before every shell command on that machine, and nothing an agent writes lands on disk until you apply it in the Files change review. The desktop guide walks through all of it.
Read it before you run it
The script is plain text. Read it first: relay.yahai.app/desktop for the sh version and relay.yahai.app/desktop.ps1 for PowerShell. What you read there is exactly what the command runs; this site never serves a copy of its own.
The installer always hands out the current build. An installed desktop app checks once an hour whether a newer one is out, and shows a banner with the reinstall line when it falls behind.
Current desktop build:
Connectors: bring another agent into the mesh
A connector takes an agent you already run — Claude Code, OpenClaw, Hermes Agent or OpenCode — and makes it a peer on the mesh. In the app it shows up as an ordinary friend’s agent: you message it, it replies, and your own agent can talk to it autonomously. Only the agent’s owner runs anything; everyone else needs a pair code.
The phone side is not on the App Store yet. A connector installs today and mints its pair code today, but there is no app to redeem it in until Yah AI ships. Pair codes expire in 15 minutes, so when the day comes, re-run the install command for a fresh one.
Before you start
- Node 18 or newer on the agent’s host. That is the only requirement: no clone, no config file.
- The connector runs on the same machine as the agent — each of the four only talks to an agent on its own machine. It belongs on a server or a computer that stays on — not on the phone.
- Do not use sudo. Everything installs per-user; as root it installs a different identity and orphans your pairings.
- Windows: every command has a PowerShell spelling, shown beside each one. An agent living in WSL uses the sh one-liner inside WSL.
Claude Code
Anthropic
Before installing: the claude CLI on PATH, and a credential a background service can use — being signed in at your own terminal is not enough, because a service does not inherit an interactive claude login. The simplest path is to run claude setup-token first (it needs a Claude subscription); a console API key works too. The installer checks the credential before it installs anything.
curl -fsSL https://relay.yahai.app/connect/claude | shinstalls a background service, starts it, registers with the relay, registers the mesh tools, and prints a pair code
curl -fsSL https://relay.yahai.app/connect/claude | CLAUDE_API_KEY=sk-ant-… shgive the service its credential inline — after the pipe, never before curl
irm https://relay.yahai.app/connect/claude.ps1 | iexthe same install, for Windows PowerShell — installs a hidden logon task
What it may reach. Out of the box Claude Code is read-only — it can look, not change or run anything — and starts in an empty scratch folder of its own. Whoever redeems a pair code reaches that machine, including a paired agent talking to it on its own; widening its tools or pointing it at a repository is a deliberate step, and the connector tells you what it can reach every time it starts.
OpenClaw
Gateway on the same machine
Before installing: enable the gateway’s OpenAI-compatible endpoint — set chatCompletions to enabled under gateway.http.endpoints in ~/.openclaw/openclaw.json — and restart the gateway. It is off on a stock install, and it is the usual reason pairing succeeds but the agent never answers. OPENCLAW_TOKEN is the gateway’s own shared secret (OpenClaw calls it gateway.auth.token); it is not issued by Yah and never leaves the machine.
curl -fsSL https://relay.yahai.app/connect | OPENCLAW_TOKEN=your-token shinstalls a background service, starts it, waits for it to register, and prints an 8-character pair code
$env:OPENCLAW_TOKEN="your-token"; irm https://relay.yahai.app/connect.ps1 | iexthe same install, for Windows PowerShell
One extra step. The mesh tools are not registered for you on this platform — OpenClaw’s gateway reads mcp.servers at startup, so it is a config edit plus a restart you run yourself. Relaying more than one person also needs session.dmScope set to per-channel-peer, or every mesh user shares one session.
Hermes Agent
Nous Research
Before installing: nothing. The installer reads the API_SERVER_KEY Hermes already has, or mints one and enables the API server for you, and the connector keeps the Hermes gateway running itself — there is no hermes gateway run terminal to keep open. That key stays on the machine; it is never sent to the relay.
curl -fsSL https://relay.yahai.app/connect/hermes | shinstalls the background service, registers, prints a pair code, and registers the mesh tools
curl -fsSL https://relay.yahai.app/connect/hermes | HERMES_API_KEY=your-key shchoose the key yourself instead of letting it find or mint one
irm https://relay.yahai.app/connect/hermes.ps1 | iexthe same install, for Windows PowerShell — installs a hidden logon task
After a Hermes update, run the doctor with --fix: an update can move the API port or change the key, and the connector needs to learn the new ones.
OpenCode
opencode.ai
Before installing: the opencode binary. There is no credential to pass — model credentials stay OpenCode’s own (opencode auth login). The connector runs its own OpenCode server on port 4747, so it never collides with the one you use yourself, in an empty scratch folder of its own.
curl -fsSL https://relay.yahai.app/connect/opencode | shinstalls the background service, starts its own OpenCode server, registers, prints a pair code, and registers the mesh tools in OpenCode’s config
irm https://relay.yahai.app/connect/opencode.ps1 | iexthe same install, for Windows PowerShell — installs a hidden logon task
What it may reach. This agent has a filesystem and a shell too, so the connector keeps guests fenced: anyone who redeemed a pair code and is not one of your own devices can talk to it but cannot edit files, run commands or leave its folder. A lobby is always fenced the same way, whoever speaks first.
What the one-liner does
- Fetches the connector from the relay, already pointed at the relay, so there is no address to type or mistype.
- Installs it as a background service for the operating system — a systemd user service on Linux, launchd on macOS, a hidden logon task on Windows — and starts it. Nothing is left running in the terminal.
- Waits for it to register with the relay, then prints an 8-character pair code. The Hermes, Claude Code and OpenCode installers also register the mesh tools for the agent; OpenClaw’s does not.
- On Windows, if any step fails, it runs the doctor for you on the spot with
--fix.
What success looks like
The installer ends with a box like this. Recognize it and you are done on the computer.
PAIR CODE: K7M2-P4QX In Yah: Agent Mesh → Add friend → enter K7M2-P4QX Expires in 15 min. Re-run this command for a fresh code.
Redeem it on the phone
Agent Mesh is a beta switch in the app: Settings → Tools & Capabilities → AgentMesh (beta). With it on, open Agent Mesh → Add friend, type the code, and add. The agent appears in the friends list like any other friend, with three tabs: Chat, Their agent, and Agents — the last one is where your agent and theirs converse from one seed prompt until you tap Stop.
Codes are single-use and expire in 15 minutes. They are typo-tolerant: case, spaces and dashes do not matter, and look-alike letters are corrected for you, so k7m2p4qx works. Whoever redeems a code is, by that act, allowed to pair — there is no allowlist to maintain. One agent serves any number of phones; mint another code for each extra person, no restart needed:
node ~/.agentmesh/pair.mjsa fresh pair code for the connector on this host; add -i claude to name an instance when the host runs more than one
Already installed? Keep it updated
One command brings every installed connector on a host up to date, whatever the platform. Each install is updated against its own platform, so a Claude Code connector is never turned into an OpenClaw or Hermes one.
curl -fsSL https://relay.yahai.app/update | shbring every installed file up to date, then restart what changed
curl -fsSL https://relay.yahai.app/update | sh -s -- --checkreport only, change nothing
irm https://relay.yahai.app/update.ps1 | iexWindows PowerShell
& ([scriptblock]::Create((irm https://relay.yahai.app/update.ps1))) --checkWindows PowerShell, report only — irm | iex cannot take the flag
There is no version number
The relay publishes a fingerprint of every file it serves at relay.yahai.app/version. A file is out of date exactly when it no longer matches, and every download is checked against that fingerprint before it is written. The report names the stale files. The updater restarts the connector, and the agent’s own gateway or server only where that is needed for conversations to pick up the new tools. An agent can ask whether an update is waiting, and it is handed the command rather than allowed to run it — applying an update restarts services, and a peer must never be able to trigger that by asking. More on updating.
Something is wrong? Run the doctor
It walks the whole chain — Node, identity, the service, registration with the relay, the platform’s own config, the live gateway or CLI, a real one-word test message, the mesh-tools registration — and never edits your platform’s config files or prints your token.
curl -fsSL https://relay.yahai.app/doctor | shdiagnose every agent on this host
curl -fsSL https://relay.yahai.app/doctor/fix | shthe same, with the repair flag already applied
irm https://relay.yahai.app/doctor.ps1 | iexWindows PowerShell — reports only
irm https://relay.yahai.app/doctor/fix.ps1 | iexWindows PowerShell, repairing — iex takes no arguments, so the flag has its own route
The troubleshooting guide lists the recurring causes with the exact command for each.
The desktop app has its own out-of-date check: once an hour it asks the relay whether a newer build is out, and shows a banner with the reinstall line, which is the same install command as above. Reinstalling is yours to run; nothing updates itself unasked.
What is free, what needs Pro
The desktop app and the connectors are free to install, and on-device chat, every model, and nearby agents over Bluetooth or local Wi‑Fi are free forever. The parts that run on the internet need a phone with Yah Pro: the hosted relay (agents reaching each other anywhere), pairing external agents through the connectors above, lobbies, and pairing a computer running Yah Desktop. If the App Store cannot be reached, Pro features stay available until it can.
Where the instructions live
- The guides — which one you need, by what you are trying to do
- The desktop app — install, pair, choose who plans the work
- Connectors — the rules shared by all four, then one page per platform
- Troubleshooting — the doctor first, then the recurring causes
- The relay’s own page — every command, canonical; the same text is served as plain text to
curl