Detour
Detour
An SSH client for teams, with no server in the middle.
Hosts, keys and passwords are shared through a Git repository or a folder you already have, encrypted end to end and signed on every change.
Download · App Store · Docs · Security design · Build from source
Features
Terminal. Tabs, split panes, search, themes. Output that comes without colours gets them: the prompt, paths, addresses, sizes and status words. Copy and paste like your system terminal, or like Termius.
SFTP. Files and whole folders with progress and cancel, permissions, a terminal in the current folder. A failed transfer never leaves a half-written file.
Tunnels. Local (
-L), remote (-R) and SOCKS (-D) forwarding.Proxies. Chains of jump hosts (
-J), and saved proxies hosts go through: SOCKS5, HTTP, WireGuard (only for Detour, no system VPN) and VLESS over TCP or XHTTP with TLS, REALITY and Vision. From avless://link or a.conffile.Import.
~/.ssh/configwithInclude, patterns andProxyJump, keys andknown_hosts.All your devices. Your vault syncs between them. A new device joins with a one-time code.
iPhone and iPad. Detour SSH on the App Store: the terminal with a key bar of your own, files over SFTP, keys, snippets, Face ID, sync and teams.
Teams. Access per host, key and snippet, per person.
Command line.
detourdoes everything the app does, in a terminal and on servers without a desktop. MoreAI agents. Claude Code, Codex, Cursor and others work on your servers over MCP, only where and for as long as you allow, without ever seeing a password or key. More
Related MCP server: TunnelAdmin
Security
Detour treats the storage, the network and every other member's computer as hostile. There is no Detour server to trust or to breach.
If | Then |
your Git host or shared folder leaks | the attacker gets ciphertext. Names, addresses, logins, members and who can see what are encrypted. |
the storage alters, reorders, hides or rolls back changes others have seen | every member's Detour detects it and says so. |
a teammate's copy of Detour is modified | it still holds only the keys that teammate was given. Access is enforced by encryption, not by the app. |
someone is removed from a team | the rest of the team moves to new keys. Nothing written afterwards is readable to them. |
your laptop is stolen | the vault is sealed with your master password and locks itself when idle. |
a server's host key changes | the connection stops before any password or key is sent. |
a Detour ID is swapped on its way to an admin | the fingerprints you compare don't match. |
someone publishes a fake update | the app refuses it: updates must carry the project's signature. |
an AI agent goes further than asked | it reaches only the hosts and rights you allowed, for the time you chose, never sees a password or key, and can't accept a new server key. |
Built on age (X25519, scrypt), ChaCha20-Poly1305, Ed25519 signatures and per-device hash chains, russh and rustls. No accounts, no telemetry.
The full design, including what cryptography can't protect against: docs/teams.md.
Teams
Create a team in a Git repository (any SSH or HTTPS remote) or in a shared folder (Syncthing, Dropbox, OneDrive, SMB).
Add a teammate by the Detour ID they send you, and pick what they can see.
They open the same repository or folder.
Install
Installers for macOS, Windows and Linux are on the Releases page. Detour updates itself from there. They put the detour command line on your PATH too; for servers without a desktop, the release has it alone (detour-cli-<version>-<system>).
For iPhone and iPad, get Detour SSH from the App Store.
The interface is in English and Russian.
Privacy
Detour sends nothing to anyone except the servers, repositories and folders you set up yourself, and GitHub releases when it checks for updates (this can be turned off in Settings).
Build from source
Requirements: Node 20+, Rust (stable), and the Tauri prerequisites for your system.
npm install
npm run tauri dev # the desktop app
npm run dev # the UI alone in a browser, with demo data
cargo run -p detour-cli -- --help # the command line
cargo test --workspaceRelease builds sign their update files with the updater key: set TAURI_SIGNING_PRIVATE_KEY (and TAURI_SIGNING_PRIVATE_KEY_PASSWORD if it has one), or build without update files:
npm run tauri build -- --config src-tauri/tauri.bundle.conf.json --config "{\"bundle\":{\"createUpdaterArtifacts\":false}}"tauri.bundle.conf.json builds the command line (scripts/sidecar.mjs) and puts it into the installers, with the PATH set up on Windows (src-tauri/windows/).
CI builds the macOS and Linux installers and the command line archives for every v* tag into a draft release. The Windows ones are signed with a Certum code signing certificate in SimplySign, so they are built locally and added to that draft by scripts/release-windows.ps1. It then makes the MCP bundle (detour-<version>.mcpb, for Claude Desktop and the MCP Registry) with scripts/mcpb.py, which also updates server.json for mcp-publisher publish.
Layout
crates/detour-core/ SSH, SFTP, vaults, team sync, crypto. No UI dependencies.
crates/detour-ipc/ the protocol between the core and its clients
crates/detour-daemon/ the core as a process: sessions, tunnels, sync, AI agents
crates/detour-cli/ the `detour` command line and MCP server
src-tauri/ Tauri 2 shell: the window, the tray, a proxy to the core
src/ React + TypeScript UI, xterm.js terminal
lib/api.ts the only boundary between the UI and the coreContributing
Issues and pull requests are welcome. Contributions are published under the project's license. cargo test --workspace and npx tsc --noEmit must pass.
License
Detour is free software under the GNU AGPL v3 with the additional terms in NOTICE.
Use it anywhere, including at work, at no cost. Whoever distributes a modified version, or runs one as a network service, must publish its source under the same license, credit it as Based on Detour with a link to this repository, and must not call it Detour.
Available Tools
33 toolsadd_hostB
Add a host to the person's vault, or to a team (needs vault:edit; in a team, over all its hosts). To use it, request access to it.
Inputs: name (required), address (required), key, port, +4 more.
add_snippetB
Save a snippet: a named command (needs vault:edit).
Inputs: name (required), command (required).
add_tunnelB
Save a tunnel through a host (needs vault:edit; for a team's host, one your access reaches): local (ssh -L), remote (ssh -R) or dynamic (SOCKS5, ssh -D).
Inputs: via (required), kind (required), name (required), port, +2 more.
chmodC
Change a file's permissions on a host.
Inputs: host (required), mode (required), path (required).
close_sessionB
Close a session of yours.
Inputs: session_id (required).
downloadC
Download a file or folder from a host to this computer.
Inputs: host (required), local_path (required), remote_path (required).
generate_keyB
Create a key in the person's vault (needs vault:edit). Returns its public key, e.g. for authorized_keys; the private key never leaves Detour.
Inputs: name (required), algorithm.
list_dirC
List a folder on a host.
Inputs: host (required), path (required).
list_hostsA
The person's hosts in Detour, with the access you have to each. Never shows passwords or keys.
Inputs: no named parameters.
list_sessionsC
Your open sessions.
Inputs: no named parameters.
list_snippetsC
The person's saved snippets: named commands.
Inputs: no named parameters.
list_tunnelsB
The person's saved tunnels and their teams', and whether they run.
Inputs: no named parameters.
make_dirC
Create a folder on a host.
Inputs: host (required), path (required).
open_sessionB
Open a terminal session on a host. The person sees it as a tab in Detour.
Inputs: host (required).
read_fileB
Read a text file on a host (up to 1 MB).
Inputs: host (required), path (required).
read_screenC
What the session's terminal shows now, as text.
Inputs: session_id (required).
removeB
Remove a file, or a folder with everything in it, on a host.
Inputs: host (required), path (required).
remove_hostA
Remove a host from the person's vault or from a team (needs vault:edit; in a team, a host your access reaches).
Inputs: host (required).
remove_snippetC
Remove a snippet (needs vault:edit).
Inputs: name (required).
remove_tunnelA
Remove a saved tunnel (needs vault:edit; for a team's, through a host your access reaches). A tunnel you started is stopped first.
Inputs: name (required).
renameC
Rename or move a file or folder on a host.
Inputs: to (required), from (required), host (required).
request_accessA
Ask the person for access to hosts. They see your name, the hosts, the scopes and your reason, and may allow less than you asked. Waits up to 100 seconds for the answer; if it is still pending, ask the person to approve it: their answer takes effect by itself, and wait_for_access waits for it.
Inputs: hosts (required), reason (required), scopes (required), duration.
run_commandA
Run a shell command on the session's host and get its exit status, stdout and stderr. It runs non-interactively, beside the terminal (not typed into it); the person sees it in the session's tab. Don't run commands that wait for input; use send_input for interactive programs.
Inputs: command (required), host, session_id, timeout_secs.
run_snippetC
Run a saved snippet in a session, like run_command.
Inputs: name (required), host, session_id.
send_inputA
Type into the session's terminal, as the person would: for interactive programs. Read the result with read_screen.
Inputs: text (required), session_id (required), enter.
start_tunnelC
Start a saved tunnel (needs the tunnels scope on its host).
Inputs: name (required).
stop_tunnelB
Stop a tunnel you started.
Inputs: name (required).
sync_nowA
Sync the person's vault with their other devices now (needs vault:edit).
Inputs: no named parameters.
update_hostB
Change a host of the person's vault or of a team (needs vault:edit; in a team, a host your access reaches).
Inputs: host (required), name, port, user, +3 more.
update_tunnelC
Change a saved tunnel (needs vault:edit; for a team's, through a host your access reaches).
Inputs: tunnel (required), via, kind, name, +2 more.
uploadB
Upload a file or folder from this computer to a host. An existing file there is replaced.
Inputs: host (required), local_path (required), remote_path (required).
wait_for_accessA
Wait for the person's answer to a request_access that is still pending (up to 100 seconds).
Inputs: request_id (required).
write_fileB
Write a text file on a host, replacing it if it exists.
Inputs: host (required), path (required), content (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 33 tools
Tools are grouped cleanly by resource (sessions, files, hosts, snippets, tunnels, access), and pairs that could collide are explicitly differentiated in the descriptions — run_command vs run_snippet vs send_input, read_file vs read_screen, request_access vs wait_for_access. The only mild ambiguity is `remove` and `rename`, which act on host filesystem paths but carry no noun in the name, so an agent must infer their scope from context.
The dominant pattern is verb_noun (read_file, add_host, start_tunnel, list_snippets, request_access), applied consistently across the four collection domains. Deviations are bare verbs — remove, rename, upload, download, sync_now — and the file-level `remove` is inconsistent with its own siblings remove_host/remove_snippet/remove_tunnel; also `make_dir` uses 'make' where the rest of the server uses 'add'.
33 tools is high in absolute terms, though it is spread across six genuinely distinct sub-domains (sessions, filesystem, hosts/vault, snippets, tunnels, access negotiation), each of which needs its CRUD surface. A few could be folded (e.g. start/stop_tunnel or upload/download as a single transfer tool), so the surface is heavier than strictly necessary but not padded.
Coverage is strong: hosts have add/update/remove/list, files have read/write/list/make_dir/rename/chmod/remove/upload/download, tunnels have the full add/update/remove/start/stop/list lifecycle, and access negotiation has both request and wait. The notable gap is snippets — add/remove/list/run exist but there is no update_snippet, so a saved command can only be deleted and recreated.
Maintenance
Related MCP Connectors
SSH client, server management and one remote MCP URL for your machines, with human approvals.
Scoped, audited SSH exec, sessions, and SFTP on your saved servers without exposing credentials
Manage remote servers, SSH terminals, files, databases and proxies with scoped access and approvals.
Use a person's computer after they approve it there: files, Terminal, browser, local MCP.
Related MCP Servers
- AlicenseAqualityDmaintenanceZero-config SSH/SFTP MCP server that lets an LLM client open temporary SSH/SFTP sessions to remote hosts, run commands, and upload/download files without holding any pre-baked credentials.177 npm2MIT
- FlicenseNot gradedqualityCmaintenanceWeb-based SSH connection manager with an MCP server that enables AI agents to manage remote hosts via terminals, file transfers, and port forwarding, featuring human-in-the-loop approval for secure access.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to manage an entire fleet of servers over SSH through MCP, fanning a single intent out across many hosts with target expressions while enforcing a policy engine, approval gates, and tamper-evident audit logs. Supports rolling execution with circuit breakers, cross-host diffing, bulk file transfer, tmux sessions, and YAML workflows.19AGPL 3.0
- AlicenseAqualityBmaintenanceEnables MCP clients to securely work with local files, directories, searches, terminal sessions, and processes on paired computers via outbound connections, without exposing inbound ports.74MIT