Getting started with iVibecode —
download to first steered agent.

What iVibecode is

iVibecode is a clean Mac app for watching and steering the AI coding agents you already run on your own machines. Instead of keeping a pile of terminal windows open and SSH-ing in by hand to find the right session, you open one app, see a tidy list of every running agent session with a friendly name, and tell at a glance which ones are waiting on you. Tap into any one to read what it's doing in plain language and answer it — from your Mac today, with iPhone and iPad in early access.

What you need before you start

• A Mac to run the app.
• At least one machine you can already reach over SSH — your own server, a cloud box, or the Mac you're sitting at — with sessions running inside tmux. iVibecode connects to where your agents already run; it doesn't set up the server, install anything on it, or move your code.
• An Expertly account. The first time you open the app it asks you to sign in with your Expertly account. You only do this once — it's remembered on your device.

Install and first launch

That's it — there's nothing to install or configure on your servers.

Add your first server

When you have no servers yet, the sidebar shows an "Add your first server" button. (Later, the Servers section has an "Add server" button to add more.) Either one opens the Add server form.

The fastest paths first

• This Mac — a one-tap shortcut at the top that points iVibecode at the computer you're using right now. (Remember: it needs Remote Login turned on — see the requirements above.)
• From your SSH config — if your Mac already has servers in your SSH config, the form lists them. Pick one and iVibecode fills in the connection details and connects the same way you already do — no password, no key to install. (It reads your SSH config to save you typing; it never changes it.)

Or fill in a brand-new server by hand under Connection

• Display name — optional. It's just the friendly name in your sidebar. Leave it blank and iVibecode uses the server's address as the name.
• Hostname — the address you'd use over SSH (for example server.example.com, or a private Tailscale/VPN address).
• Port — defaults to 22.
• Username — your login on that server.

Then choose how to sign in to the server

• Install this device's key on the server (the default) — you enter your server password once, and iVibecode adds this device's key so future connections don't need a password. The password is used once and not kept.
• I'll paste the key on the server myself — iVibecode shows you a public key to copy and paste into the server yourself, if you'd rather not hand it a password.

On the default Install this device's key path — including the This Mac shortcut — you enter your server password once and press Install key now. Once iVibecode confirms the key is installed, Save becomes available. If you're pasting the key yourself, add it on the server first, then press Test connection; Save becomes available once that test passes.

Watch your sessions

Once a server is connected, the sidebar (on Mac) or the session list (on iPhone) becomes your map of everything running on it. Sessions show friendly names — the name the agent set for itself, or a sensible label iVibecode works out — instead of a cryptic identifier.

iVibecode also gathers sessions into helpful groups so you can find what matters without scrolling, including:

• Waiting for you — sessions where an agent has paused and needs your answer, or has finished and is ready for your next instruction. This is the group you'll usually want first.
• Recently used — whatever you opened most recently.
• Broken connections — sessions whose live link dropped (a network blip, for instance) but which are still running on the server, so you can step back in.
• Workspaces — your own named folders for grouping related sessions.

A session that genuinely ends on the server (you typed exit, the process stopped) drops out of the list on the next refresh, so you're not left clicking dead rows.

Tap any session to open it. You land in it as a live terminal with the keyboard already focused — start typing right away. For a calmer way to catch up, switch to the Readable view: it shows the session as a plain conversation — the messages and answers up front, with each answer's "thinking out loud" tucked into a collapsible thread, a "typing" indicator while the agent is working, and the exact question shown as text when the session is waiting on you. A Detailed view button flips back to the raw terminal at any time.

Respond to an agent

You don't have to open a session to answer it. The Waiting for you screen lays out every session that needs you as roomy cards. Each card states the session's name, what's happening, and — in plain language — what it's asking (for example, "Asking permission to run something" or "Waiting on a yes or no"), often quoting the exact text on screen so you recognize it instantly.

To answer, hover a card (on Mac) or tap it (on iPhone/iPad) to reveal the controls:

• A suggested reply. When you're signed in, iVibecode can suggest an answer and pre-fill the reply box with it, so the common case is a single Send. You can edit it first, or tap Suggest a reply to generate one.
• Type your own instruction in the reply box and Send it straight to that session.
• Numbered choices. When an agent is parked on a "pick 1, 2 or 3" style menu, the card describes the option to choose (for example "Choose option 2") and Send delivers exactly that choice the way the menu expects.

iVibecode confirms your answer landed: a card shows "Sent" when delivery is confirmed, and "Couldn't send" (with the suggestion kept on screen to retry) if it didn't go through — so an answer never silently vanishes.

You can also steer a session you have open. Its Steer this session control lets you type a short instruction and inject it into the running session without first clicking into the terminal — handy on a phone.

Hand a whole task off — "Do Something For Me"

There's a Do Something For Me quick-capture box for when you want to ask for something rather than answer a prompt. Type (or dictate) what you'd like done and press Send; your request goes to a dedicated background coding session that picks it up. You can open that session from the sidebar any time to watch it work. If a request can't be delivered, the box reopens with your text and an explanation so you can retry.

Manage a session

• Mark done. When a session has finished and you no longer need it, the Mark done button relabels it (so it's easy to spot later) and closes out the agent. iVibecode confirms it actually took — you'll see "Marked done", or "Couldn't confirm — try again" if it didn't, so a session is never falsely shown as finished.
• Switch a rate-limited session to another account. If a session hits a usage limit and pauses, its card offers Resume on another account. This ends the stuck session and continues the same work on another account so you don't have to wait for the limit to reset. Because it ends the current session, the app asks you to confirm first.
• Reconnect a dropped session. If the live connection drops but the session is still alive on the server, it shows under Broken connections (and ended ones gather in an "Ended" group with a "Tap to reconnect" hint). The app reconnects on its own after an unexpected drop, and when it can't, you can reopen the session to reconnect manually.

Works across Claude Code, Codex, Gemini, and Qwen

iVibecode isn't Claude-only. It recognizes Claude Code, OpenAI Codex, Gemini, and Qwen Code sessions, shows them side by side, and labels each one correctly — a small badge marks the non-Claude ones (for example "Codex" or "Gemini") so you always know which assistant a session is running. The Readable view names the right assistant too, rather than calling everything "Claude." (Qwen Code is a Gemini fork, so its sessions read through the same view as Gemini.)

Troubleshooting

• A session won't connect. iVibecode shows a plain-English reason — for example, "Couldn't reach the server" (check Wi-Fi or VPN and that the server is online), or "The server didn't accept that username and password." The raw technical error is tucked behind a Technical details disclosure if you want to copy it.
• "This Mac" fails to connect. This almost always means Remote Login is off. Turn it on in System Settings → General → Sharing and try again — the app points you straight at this fix when it detects it.
• A connection dropped. If it was a network blip, iVibecode reconnects on its own when things recover. The underlying session keeps running on the server the whole time, so nothing is lost — when you come back, reopen the session and you're back where you left off.

Privacy and security

Your agents — and your code — stay on the machines they already run on. iVibecode connects to them over the same SSH access you already use; it doesn't copy your source anywhere, expose anything new to the internet, or edit your SSH config (it only reads it).

Your credentials stay on your device. When you let the app install a key on a server, you enter that server's password once — it's used to log in that single time and is never saved anywhere. The key iVibecode uses to connect to your servers, and your Expertly sign-in, are held in your device's secure keychain, marked to this device only and never synced to iCloud. Some things do leave your device, though, and here is the complete list.