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.
Provider software updates
Read-only checks compare the selected verified runtime with each provider's upstream latest channel. Nothing is built, stopped, or changed by this check.
Checking…
Checks run automatically every six hours; failed checks retry after fifteen minutes.
Jev decision service
Check the personal Jev account used by your decisions and jobs.
Checking…
Every user supplies a private TypeSafe API key in Keys & Tokens and consumes their own credits. The saved key is encrypted and can only be replaced or removed, never displayed. Jobs use their creator's credential.
Calculating safe cleanup candidates…
Automatic reconciliation runs every six hours. Session residue waits 24 hours; completed upgrade snapshots wait seven days.
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.
Each account consumes its own Jev credits. The key is encrypted at rest and can only be replaced or removed; it is never displayed or returned.
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/session
immortal skills list
immortal skills granted project/session
immortal files upload project/session
immortal workspace browse project/session
immortal workspace list project/session
immortal workspace download project/session build/result.pdf --output ./result.pdfmacOS: approve the unsigned client
The client has an Immortal Ed25519 release signature but is not code-signed or notarized by an Apple-certified developer, so macOS may block its first launch. Verify the SHA-256 and complete signing-key fingerprint shown above through an administrator-controlled channel, 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 safely
Ctrl-C, Ctrl-D, or Ctrl-B then D detach locally without stopping the provider. Use --control-keys forward only when you intentionally want those control bytes to reach the provider. Ctrl-B then F opens the local textual workspace browser. Dragging or pasting one local file path into the live native console asks before uploading it and requests an optional agent comment. The client preserves shared web/terminal geometry.
A version mismatch displays the installed and required releases and asks before installing the Ed25519-and-SHA-256-verified matching client. immortal update checks explicitly; immortal update --yes is available for deliberate non-interactive automation. Omit the local path from immortal files upload project/session to drag one file into its prompt. Credentials are revocable tokens stored in private JSON under ~/.immortal; passwords, TOTP secrets, recovery codes, and passkeys are never stored by the client.