Select a document.
YOUR WORKSPACE
Stay in the loop, from anywhere.
Agent sessions keep working on the host when your laptop or browser goes offline.
0sessions
0running now
LIVE WORKSPACE
Console
Watch the agent, then take the keyboard when you need to intervene.
Create a stopped session from a validated bundle
Email, password, and TOTP
Loading sign-in methods…
- 1Account passwordConfirm the email and enter the new password twice.
- 2Authenticator appScan a QR code and verify a six-digit TOTP code.
Fresh MFA verification is valid for five minutes on this browser session.
CURRENT SERVER RELEASE
Checking downloads…
The server verifies client/API compatibility before login and attachment.
Quick start
chmod 700 ./immortal-*
install -m 0755 ./immortal-* ~/.local/bin/immortal
immortal context add work --server https://immortal.example.invalid
immortal login
immortal sessions list
immortal console project/sessionmacOS: approve the unsigned client
The client is not signed or notarized by an Apple-certified developer, so macOS may block its first launch. Verify the SHA-256 shown above, attempt to run immortal version, then open System Settings → Privacy & Security, select Open Anyway for Immortal, authenticate, and confirm Open. Do not disable Gatekeeper globally.
By default, Ctrl-C, Ctrl-D, or Ctrl-B then D detach locally without stopping the provider, and the client preserves the shared web/terminal geometry. Use --control-keys forward or --remote-size local only when you deliberately want those remote effects.
A logged-in client automatically installs a checksum-verified matching release from this server on its next command; immortal update checks explicitly. Credentials are revocable tokens stored in private JSON under ~/.immortal; passwords, TOTP secrets, recovery codes, and passkeys are never stored by the client.