Talk to your coding agents.
On every machine you own.

Your laptop, a big VM, the box under your desk. Run Claude Code sessions on all of them, each piece of work in its own copy of your stack, and drive every one from a single page by talking to it.

curl -fsSL https://raw.githubusercontent.com/FurlanLuka/crew/main/install.sh | sh

Then run crew. macOS and Linux · add any machine you can SSH into · your own Claude Code login

Voice OS: a session on another machine with its work stream, dev servers and spoken summary, and the other active sessions as tabs

This session runs on Build box, a Linux VM. You are talking to it from a Mac.

Every machine, one voice

Your laptop is the cockpit. The work runs wherever it's fastest.

Point crew at a machine you can SSH into and its sessions show up next to yours: same page, same voice, same alerts. The heavy builds, the dev servers and the Claude sessions stay over there. Only your words and their answers travel.

Add it with its SSH host

Install crew there, run crew server remote, then add the host in Set up. No ports to open and nothing exposed. It rides the SSH you already use.

Talk to any session by name

"Build box store front, run the migrations." Home lists every machine's sessions with whatever waits on you first, and alerts say where they come from.

Links drop. Work doesn't.

Close the laptop, lose the Wi-Fi. Sessions over there keep working, and when the link is back you hear what finished meanwhile.

One crew everywhere

Update the main and it brings its remotes along. Logs from every machine come back in one query, and any machine can post to your Discord.

How other machines work →
What it sounds like

You talk. The session on screen listens. The rest wait their turn.

A small router in the middle decides where your words go, and it's strict about one thing: anything about the actual work goes to the session, in your words. It never answers for it or guesses what you meant.

youbuild box store front, run the e2e suite

voice osSent to store-front wrk2 on Build box. Switch there?

youno, stay. what's waiting on me?

voice osBuild box, signals asks: a new events table for clicks, or the orders table?

youthe new table

voice osCheckout is done. Retries back off from 200 ms to 3.2 s, all 41 payment tests pass.

Every piece of work gets its own stack

A worktree per feature with all its repos, dev servers on ports that stay put, and env vars that point the services at each other. crew checks it all starts before you touch it.

Answer without switching

Permissions, plans and questions come to you out loud. Say "yes" or "the second one" and the session carries on, while the one on screen stays on screen.

Hand it what you see

Paste a screenshot or drop a log on a session's page and it goes along with your next words, to a session on this machine or any other.

Home: sessions on two machines, the one asking a question first, and a card for each machine

Home: every machine's sessions in one list, a card per machine, and Lab box out of reach without anything stopping.

Set up with Claude adding a repo, each crew command it ran with a recorded line under it
Setting it up

Or just ask the Claude that lives in Set up.

"Add the store api and store app repos from ~/code, wire the app's API URL to the API, and make a workspace with both." It runs the commands, checks every server starts, and shows you each one.

Away from the desk

Walk the dog, keep shipping.

The page works on your phone, and Voice OS can join a private Discord voice channel so you talk to your sessions from anywhere. Sessions can post screenshots and summaries there when you ask.

Voice OS on a phone
What it costs

crew is free. Sessions run on your own Claude Code login. The router costs about a third of a cent per spoken turn on your Anthropic key, and Soniox bills speech by audio time.

Where your data goes

Your voice goes to Soniox to become text and speech. What you say goes to Anthropic for routing. Keys, notes and logs stay on your machine, and recordings are never kept.

Where it stands

Young and moving fast. I build crew with crew every day, and every change goes through thousands of tests before it merges. Tell me when it breaks.