How it works
Wigwam connects the terminals on your machine to any device you own. Click any component to learn more.
Terminals
Persistent sessions
Terminals you open in Wigwam live inside the base process. If the hut crashes, gets updated, or restarts — your terminals keep running. The base buffers output while disconnected and replays it on reconnect. You never lose a running process.
Real-time streaming
Terminal output streams to every connected device simultaneously. Type on your phone, see the output on your laptop. Every keystroke is sent in real-time over an encrypted WebSocket connection through the relay. Multiple devices can view and control the same session at once.
Multi-machine
Run wigwam on as many machines as you want. Each one
connects to the relay independently. From a single browser tab,
switch between machines and control them all. Your dev server, your
CI box, your home lab — all in one place.
End-to-end encrypted
All terminal data is encrypted between your machine and your devices. The relay routes connections but never sees the content. In secure mode, devices must verify an out-of-band key (QR code or mnemonic) before they can connect.
IDE
Your code lives everywhere
Being able to work from anywhere means your code should live everywhere too. The built-in IDE keeps your codebase in sync in real-time — see every change from any device, the moment it happens. No git push/pull cycle, no cloud IDE vendor lock-in.
Every keystroke, every device
Changes sync instantly across all your devices. Edit on your laptop, see it on your phone. Your coding agent writes a file, you see it immediately in the browser. Your codebase is always current, no matter where you are.