software-mansion / voyager

Voyager 
 Observe, debug, and understand running BEAM systems 
 A desktop app that connects to any BEAM node and shows you what is actually going on inside it 
 Website 
 ·
 Download 
 ·
 Give feedback 
 ·
 License 
https://github.com/user-attachments/assets/8aa3f69e-a692-4b9d-9bf5-75d972f6370f
## Overview
Voyager is a desktop app that inspects running BEAM systems through one interface instead of a patchwork of shell commands copy-pasted into `iex`. It connects to any OTP 27+ node, local or remote, over plain Erlang distribution and surfaces the information the BEAM already exposes, in a form that is actually pleasant to read:
- **Node info** — memory and IO usage, schedulers, system limits, and running applications
- **Supervision trees** — a graphical, navigable view of each application's process hierarchy
- **Processes** — rank processes by memory, reductions, or message queue length, and drill into any one of them
- **ETS tables** — list tables, browse their contents, look up keys, and search with match specs
- **MCP server** — the same data for coding agents such as Claude Code or Cursor, so they can inspect a live system instead of guessing from source code
No setup is required on the target node. On connect, Voyager compiles and loads a small helper module (`voyager_agent`) into the node's memory and gathers everything else over RPC; nothing is written to the node's disk, and all rendering and storage happens on your machine.
### Why Voyager
- **No setup on the target** — no dependency in your app, no hook in your release. If the node is distributed and runs OTP 27+, Voyager can attach to it.
- **The whole BEAM, not one framework** — Erlang, Elixir, Gleam. Voyager speaks the distribution protocol, not framework internals.
- **Production without a remote shell** — connect over SSH and inspect a deployed node directly, instead of opening a shell and piecing the picture together by hand.
- **First-class AI support** — the same data is exposed over MCP, so a coding agent can read a live system instead of guessing from source code.
- **Built to be read** — a graphical, navigable view of process hierarchies and runtime numbers, which also makes it a good way to learn how OTP actually behaves.
## Installation
Download the latest build for your platform from the website. Voyager currently ships for:
- macOS (Apple Silicon)
- macOS (Intel)
- Linux (x64) — distributed as an AppImage, see docs/linux_appimage_guide.md for how to run and install it
The app checks for a new release on startup and can install it in place; the current version and update status are under **Settings → Updates**.
## Connecting to a node
Voyager connects to any distributed node running **OTP 27 or later**, either directly or through an SSH tunnel to a host that can reach it, which is the usual path to a production node behind a bastion. Start the node with a name and a cookie, then enter both in the connect form:
 [code] 
Check out the connection guide for other setups or if