What Voyageur does

A control tower, not one more terminal.

Every piece serves the same goal: launch your agents across all your projects, surface the one that needs you, lose nothing of what was asked, and move from remote to local with zero friction.

01 · Multi-workspace fan-out

All your projects, one view.

One workspace per project, one agent per workspace, all in parallel. The control tower shows the state of each at a glance, across all your machines at once, without juggling five windows.

  • Instant switch between recent workspaces with Ctrl+Tab
  • Workspace quick-picker from history with Cmd+N
  • Session restore: you find your panes and agents where you left them
voyageur · control tower
Voyageur screenshot: the control tower shows every workspace and each agent's state (running, waiting, idle) at a glance.
02 · Agent and mission tracking

The attention router, and the log of what was asked.

Voyageur reads the real state of each Claude Code agent, pane by pane, and surfaces the one waiting on you. Every workspace carries an orbital medallion that sums up everything inside it at a glance. And because knowing which one waits is not enough once five agents are running, every pane also carries its written mission: what it is working on, where it stands, what was done.

  • One moon per pane on the medallion: running, thinking, idle, waiting
  • A cluster of dots for a pane that still has sub-agents running in the background
  • An amber beacon when an agent is blocked on a question: it goes to the front of the queue
  • OS notification "Claude is waiting", even with the lid closed: one click jumps to the pane
  • Urgency timers colored beyond 2 then 5 minutes of waiting
  • Agents from every server, not just the one on screen: each row carries its machine's name
  • An agent waiting on a background machine stays audible: its question surfaces without switching servers
  • Every pane carries its mission on its header: the title, the progress, and the summary written on closing
  • The agent takes part itself: it states where it stands, closes its mission and opens another when the conversation moves on, under the title it gives
  • A past mission is found again weeks later, by title, by what was asked or by its summary; if its pane is gone it opens as a card with its project, dates and duration
  • This tracking is for you, not for the model: it is not a way around the context window, and its token cost, measured then optimised, is negligible
voyageur · tracking and missions
Voyageur screenshot: the active pane's header shows the current mission's title and its state, next to the workspace and the server running it, while an amber medallion flags an agent waiting on an answer.
03 · Panes and Quake overlay

As many panels as you want.

Split the screen into vertical and horizontal panes at will; each pane mirrors a remote terminal in real time through tmux control-mode. Plus a Quake terminal that slides down from the top, independent of workspaces.

  • Horizontal split Cmd+D, vertical Cmd+Shift+D
  • Zoom a pane Cmd+Shift+Enter, stash Cmd+G
  • Quake overlay with Double-Ctrl, with a local or cloud machine selector
voyageur · Quake terminal
Voyageur screenshot: the Quake terminal overlay, opened with Double-Ctrl, sliding down from the top with its local or cloud machine selector.
04 · Remote and hosted servers

Your machine, your own server, or ours.

Add as many servers as you want: your local machine, an SSH server of your own over Tailscale, or a workspace hosted on our cluster, ready in one move. Each server has its own tint and a live daemon line.

  • Guided SSH server add, encrypted connection over Tailscale
  • Hosted Voyageur as a comfort option, never the core of the offer
  • Capacity stays bounded by the cluster RAM: the UI reflects a "capacity reached" state
voyageur · servers
Voyageur screenshot: the launch hub, between local machine, SSH server over Tailscale and a hosted workspace ready in one move.
05 · File navigation

The project tree, wherever it runs.

A full file browser on remote as well as local, with a fuzzy finder to jump anywhere without leaving the keyboard.

  • Fuzzy finder in the tree, quick-open a file Cmd+P
  • Open by pasted or typed path Cmd+K, resolved against the active pane
voyageur · files
Voyageur screenshot: the fuzzy finder in the tree, a three-letter query and the project files ranked by relevance, each with its relative path.
06 · Editor and viewers

Read and fix without switching tools.

A built-in Monaco editor to review what the agent wrote, tweak a line, and save. Rendered files toggle from source to preview in one click.

  • Syntax highlighting, multi-file tabs across all your workspaces
  • Source to Preview toggle, save Cmd+S
voyageur · editor
Voyageur screenshot: the Monaco editor zoomed on a TypeScript file, with multi-file tabs and syntax highlighting.
07 · Real-time sync

From remote to local, no friction.

Your files sync continuously between your machine and the server. You move from one to the other without copying, without pushing, without thinking about it. The sync console shows the state live.

  • Two-way synced working tree, embedded Mutagen engine
  • Zero server-side prerequisites: everything is pushed on first sync
  • Sync console: flush, pause, resume, reconcile, on demand
voyageur · sync
Voyageur screenshot: the sync console, showing the state of transfers between the local machine and the server live.
08 · File transfer

Move files up and down, simply.

Pull a remote file onto your machine, or send one to the server, without leaving Voyageur. The local path is always chosen by you, never imposed.

  • Download to host via native "Save as" dialog
  • Upload from host with collision detection and overwrite confirmation
  • Paste or drop an attachment: it is sent and referenced for Claude
voyageur · transfer
Voyageur screenshot: the context menu on a remote file in the tree, with the "Save to this computer" entry that pulls the file down to the host machine.
09 · Full search

One field, everything that matters.

Search Everywhere opens a single-field palette that sorts what is waiting on you, your workspaces and all your open files. Plus two direct keyboard openings.

  • Search Everywhere Double-Shift: waiting, workspaces, open files
  • File quick-open Cmd+P, open by path Cmd+K
voyageur · Search Everywhere
Voyageur screenshot: Search Everywhere, one single field that sorts what needs your attention, your workspaces and your open files.
10 · Claude Code integration

Your Claude, at hand.

Voyageur supervises your Claude Code sessions without ever getting in the way: you keep root and your Claude. It aggregates usage, tracks the Claude Code changelog, keeps Claude up to date, and opens the config files for you.

  • Usage and rate-limits aggregated (5 h and week windows), reset countdowns
  • Claude Code changelog tracking, summarized in the app: always on top of what is new, without leaving Voyageur
  • Edit CLAUDE.md and settings (project and global), in-place Claude update, notification hooks

Report a bug or a missing feature, right inside the app, in one shortcut.

voyageur · Claude Code
Voyageur screenshot: the Claude config files menu open, with the project CLAUDE.md, CLAUDE.local.md and settings.json, plus the state of the server's global CLAUDE.md.
11 · The CLAUDE.md block

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 two conventions that follow from it.

  • The exact text to be written is shown first: permission is about those lines, nothing else
  • Delimited, versioned block: Voyageur never touches anything else in the file
  • A block you edited by hand is never overwritten, it is left exactly as it is
  • "Later" or "Stop offering": it is a proposal, not an install
voyageur · CLAUDE.md integration
Voyageur screenshot: the CLAUDE.md integration card, showing the target file, the exact text of the block to be appended, and the Add, Later and Stop offering buttons.
12 · Skills library

Your skills follow your agents everywhere.

One reference library, deployed to every one of your environments. Voyageur compares each machine to the reference, spots the one that has diverged, and lets you reconcile in one click. No version is ever lost.

  • Reference library versioned with semver, deployed to every workspace
  • Per-environment status at a glance: up to date, ahead, behind, diverged, not deployed
  • Skills found on a machine but missing from the library: surfaced, never lost
  • Zip import and export to move a whole library in or out
voyageur · Skills
Voyageur screenshot: the skills manager, the reference library on the left and the status of each environment on the right, with one diverged machine to reconcile.
13 · Guided reconcile

Two versions of a skill, neither one lost.

When a machine and the library have both moved on, Voyageur combines what it can and only asks you to arbitrate the passages that genuinely conflict. One passage at a time, with a word-level diff on both sides.

  • Three-way merge: the common base, your library, the machine's copy
  • Four ways out per passage: keep one, the other, both, or write the final text
  • The new reference version is proposed in semver, and stays editable
  • Nothing is overwritten: both original versions stay intact in the library
voyageur · combine
Voyageur screenshot: the guided merge of a diverged skill, the library version and the server version side by side with their differences highlighted word by word.
14 · Keyboard shortcuts

Everything on the keyboard.

The frequent moves are at your fingertips. Pane and window shortcuts are on Cmd only, to let Ctrl+C, Ctrl+D and Ctrl+W through to the shell.

voyageur · shortcuts
Voyageur screenshot: the keyboard shortcuts cheat sheet, grouped by navigation, windows and panels.
15 · Dev server URLs

Your dev server, in your browser.

An agent starting a dev server on a remote machine usually announces http://localhost:3000, an address that means nothing from your machine. Voyageur puts a voy url <port> command in every pane: it returns the URL your browser can open, and opens a tunnel when one is needed.

  • voy url 5173 prints the reachable URL, never localhost, and warns you when nothing is listening on that port yet
  • On by default on Voyageur hosted workspaces, where a tunnel is the only possible path
  • On by default on your own SSH servers too, switchable off per server to keep a direct, stable address
  • The port stays closed on the server: the tunnel rides SSH, already authenticated
voyageur · voy url
Voyageur screenshot: the control tower gathers agents from several machines, each remote row carrying its server's name.
Open alpha

Try it all now.

Mac, Linux and Windows. We iterate fast, we answer every question.

A question, a bug, an idea? voyageur@e2pz.app