Launch your agents.
Close your laptop.
Five agents on five projects, each on its own orbit around you. Voyageur hands you back the one that needs an answer, and tells you where the others stand. This is not a picture: hover a satellite, click the one waiting on you.
open alpha · mac, linux and windows · we answer every question
Alpha · 3 August to 30 September 2026
The alpha's benefits stay yours for life.
Reserved for alpha testers who send us usable feedback. The app itself is open to everyone during the alpha.
Your agent is running. Your laptop is hostage.
Staying local means staying on a leash. The run holds the machine, and the moment you go multi-project you lose track of who finished and who is waiting on you.
The run pins the machine
A long agent owns the terminal. You cannot let go of the screen without feeling you are breaking something mid-flight.
Juggling between repos
Five projects, five windows. You spend your time checking by hand which one finished and which one is stuck on a question.
Attention scatters
With no signal you watch everything continuously, afraid to miss the moment an agent needs you. That is the leash.
A workspace fits in one medallion.
Every project carries an orbital medallion. One moon per pane, coloured by what the agent is doing. A cluster of three dots when sub-agents are still running in the background. And if an agent blocks on a question, the whole medallion turns amber with a beacon pinned at the top, always in the same place. Poke the buttons: this is the app's real component.
The real product: a control tower for your agents.
Not one more persistent terminal, everybody ships that. At five agents what you lack is not horsepower: it is knowing what is going on, and not losing it. Voyageur fans out across all your projects, surfaces the one waiting on you, and keeps the log of what each was asked to do.
Multi-project fan-out
One agent per project, all in parallel, in a single view. You go from N projects spread over as many machines as you like to one control tower.
Attention router
The agent that finished or asked a question rises to the top, tinted and flagged. You answer, it carries on.
Mission log
Every pane carries its mission: its title, where it stands, and the summary the agent writes when closing it. You know what each one is working on, and you find it again weeks later.
Out-of-band signal
The agent waits on you even with the lid closed: you get pinged, you stop standing guard.
One field, and what needs you on top.
Double-Shift opens the palette. It does not list your projects alphabetically: it sorts them by urgency. What blocks rises, what runs follows, your open files bring up the rear. The same field finds a past mission, by its title, by what was asked, or by the summary the agent wrote of it. Type in it, it works.
A terminal that drops in, outside your workspaces.
Split the screen into as many panes as you want, each mirroring a remote terminal live through tmux control-mode. Plus a Quake terminal that slides down from the top wherever you are, with its own machine picker.
- Split side by side Cmd+D, stacked Cmd+Shift+D
- Zoom a pane Cmd+Shift+Enter, stash it Cmd+G
- Overlay with Double-Ctrl, local or cloud
Your machine, your own server, or ours.
Every server has its own tint, and it means something: sage for local, lantern for your SSH box, violet for hosted. The same colour comes back everywhere in the app, down to the edge of the medallions.
Local
localhost · local
Claude Dev
your box · SSH over Tailscale
Atelier · EU
Voyageur hosted · comfort option
You keep root and your Claude Code. The inference that writes your code stays yours: Voyageur orchestrates, it never sits between you and your agent.
Remote to local, without thinking about it.
The working tree syncs continuously both ways. You open the file on your Mac, the agent sees it on the server. The console shows you the flow and leaves you in control of it.
- Bundled Mutagen engine, zero server-side prerequisites
- Flush, pause, resume, reconcile, on demand
- The .git comes down as a replica, the tree goes both ways
One machine diverged. Nobody loses their work.
One reference library, deployed to every one of your environments. Voyageur compares, spots the machine that drifted, and only asks you to arbitrate the passages genuinely in conflict. Click Combine on the amber row.
Most changes combined on their own. For this step, both sides wrote different text. Nothing gets overwritten: pick the one that becomes the reference.
Your agent knows it is in a control tower.
An agent that does not know how you read it writes for a terminal you are not looking at. Voyageur offers to add a short block to the server's global CLAUDE.md: the agent learns it runs in one pane among many, and the conventions that follow.
- The exact text is shown first: permission is about those lines
- Delimited, versioned block, the rest of the file is never touched
- A block you edited by hand is left exactly as it is
- "Later" or "Stop offering": it is a proposal, not an install
Yes, you can set up a VPS. That is not the question.
A VPS with Tailscale, tmux and Claude Code costs three euros, and for a single project it does cut the leash. What DIY does not give you: fan-out, the attention router, the out-of-band signal. Assemble it and maintain it, all of that has a real cost, including the day the infra breaks.
| What you actually need | Home-rolled VPS + tmux | Voyageur |
|---|---|---|
| Persistent shell, run that survives | yes | yes |
| Fan-out across all your projects | by hand | native |
| Attention router | missing | native |
| Signal when an agent waits on you | missing | out of band |
| Skills reconcile across machines | missing | native |
| Maintenance when the infra breaks | on you | our problem |
Your environment, your stack, your rules.
Voyageur orchestrates, it does not lock you in. Where others drop you on an isolated box with a single vendor, you keep full control.
Full root
Your complete environment, your access, your tools. No sandbox holding you back.
No model imposed
You keep Claude Code and whichever model you want. Your agent writes the code: Voyageur orchestrates, it never sits in between.
Your stack, your rules
Neither Codespaces at Microsoft nor Ona at OpenAI. No vendor lock-in, no bill by machine-time.
Do not want to run a server? Tick the box.
On your machine by default. Or, if you prefer, a hosted environment on our cluster, ready in one move. A comfort option, never the core of the product.
And here is what it actually looks like.
Everything above is the app's visual language, replayed live. Here is the app itself, captured untouched.
Free during the alpha. Free for the essentials after.
The alpha runs until 30 September 2026 and is open to everyone: everything is free, no limits. Only the cloud is capped, at 50 seats. After that the control tower stays free. Only three comfort features become paid.
Hosted environment
A ready-to-use workspace with Claude Code already installed. You plug in your own key: the inference that writes your code never goes through us.
Fan-out at scale
More than two parallel workspaces, as many projects at once as you want.
Centralised skills backup
Voyageur keeps and syncs your whole library, you stop thinking about it. Deploying and reconciling skills across your environments stays free.
Alpha open to everyone, cloud capped at 50 seats. See the details
Launch your agents. Close your laptop.
Mac, Linux and Windows, all direct. You keep Claude Code, you gain the control tower.
A question, a bug, an idea? voyageur@e2pz.app