██╗███╗ ███╗███╗ ███╗ ██████╗ ██████╗ ████████╗███████╗██████╗ ███╗ ███╗ ██║████╗ ████║████╗ ████║██╔═══██╗██╔══██╗╚══██╔══╝██╔════╝██╔══██╗████╗ ████║ ██║██╔████╔██║██╔████╔██║██║ ██║██████╔╝ ██║ █████╗ ██████╔╝██╔████╔██║ ██║██║╚██╔╝██║██║╚██╔╝██║██║ ██║██╔══██╗ ██║ ██╔══╝ ██╔══██╗██║╚██╔╝██║ ██║██║ ╚═╝ ██║██║ ╚═╝ ██║╚██████╔╝██║ ██║ ██║ ███████╗██║ ██║██║ ╚═╝ ██║ ╚═╝╚═╝ ╚═╝╚═╝ ╚═╝ ╚═════╝ ╚═╝ ╚═╝ ╚═╝ ╚══════╝╚═╝ ╚═╝╚═╝ ╚═╝
Immortal Terminals
Are you afraid
to close VS Code?
ImmorTerm makes your terminal sessions immortal. Your AI remembers everything. One install, zero config.
Your terminals are immortal
Every developer knows the panic. You have 5 terminals open — a dev server, a test runner, a Docker tail, an SSH session, a log stream. Then VS Code crashes. Or your laptop restarts. Everything is gone.
ImmorTerm runs a lightweight C binary (a GNU screen fork) that owns your terminal processes. They live outside VS Code. When VS Code comes back, the extension reconnects to your running sessions automatically.
Full scroll history. All environment variables. Running processes still running. Zero config.
Claude that never forgets
Every time you start a new Claude Code session, it has amnesia. All your past decisions, debugging sessions, architecture choices — forgotten. You end up re-explaining the same context over and over.
ImmorTerm Memory gives Claude 25 MCP tools for persistent memory. It auto-extracts decisions, tracks code changes, digests entire books into searchable knowledge packs, and lets you browse and resume any past session.
The memory stack runs locally via Docker (5 containers: Qdrant vector DB, Redis, MCP server, Celery worker, Neo4j). The extension handles setup automatically — you just need Docker Desktop running.
500x compression. Session continuity. Decision tracking. Your Claude becomes a teammate with a real memory.
Kill the invisible RAM bloat
Here's something most developers don't realize. Every Claude Code session you open spawns a separate child process for each MCP server in your config. These are stateless stdio processes — they start up, allocate memory, load models, and sit there.
With 8 MCP servers configured (a typical setup), each Claude session creates 8 child processes. Open 10 Claude sessions throughout your day?
That's 80 zombie child processes.
They consume 11.7 GB of RAM doing absolutely nothing. Your laptop fans spin up. Your battery drains. You blame VS Code, but it's the MCP processes.
The ImmorTerm MCP Gateway hosts all your MCP servers once, using the new Streamable HTTP standard. Every Claude session connects to the gateway instead of spawning its own children. One process per server, shared across all sessions.
11.7 GB → 56 MB. That's a 96% reduction.
Make your terminal uniquely yours
Each project gets its own theme. Click any theme below and watch the entire page transform — that's exactly what happens to your terminal.
Purple Haze
Click a theme to transform the page
Try a theme — watch the whole page change
Per-Project Identity
Each project gets its own theme. Jump between repos and instantly know where you are by the gradient glow of your status bar.
Live Status Bar
Not just colors — a dashboard. See terminal last-active time, Claude's context window, RAM and CPU usage, all at a glance. Zero polling.
Developer Joy
10 hand-crafted themes from Purple Haze to Neon Tokyo. Personalize your workspace and feel excited every time you open a terminal.
Can your Claude answer these?
Try asking Claude Code these questions right now. Go ahead, we'll wait.
How it works
Three steps. That's it.
Install
One command. No config files, no setup wizard, no Docker. Just install the VS Code extension.
Use
Keep working as you always do. Open terminals, run builds, use Claude Code. ImmorTerm works invisibly in the background.
Survive
VS Code crashes? Laptop restarts? No problem. Your terminals — and your AI's memory — are already back.
Simple pricing
Free forever for Immortal Terminals. Pro unlocks AI memory superpowers.
| Feature | Free | Pro |
|---|---|---|
| Persistent terminal sessions | 1 project | Unlimited |
| Terminal slots | 3 terminals | Unlimited |
| Auto-restore on crash | ||
| Full scroll history | ||
| Status bar themes | 5 themes | All 21 themes |
| AI memory (25 MCP tools) | ||
| Cross-session context & resume | ||
| MCP Gateway (RAM optimization) | ||
| Knowledge packs (expert agents) | ||
| File checkpoints & revert | ||
| Code change tracking | ||
| Priority support |
Frequently asked questions
ImmorTerm runs a lightweight C binary (a GNU screen fork) that owns your terminal processes. When VS Code crashes or restarts, the extension reconnects to the running sessions. No data loss, no interrupted builds.
The opposite. The MCP Gateway alone frees up to 96% of RAM consumed by Claude MCP servers (11.7 GB → 56 MB). The terminal binary uses negligible resources.
ImmorTerm's OpenMemory server provides 25 MCP tools that give Claude persistent memory across sessions. It can recall past conversations, decisions, code changes, and even digest entire books into searchable knowledge packs.
No. The free tier (persistent terminals) needs nothing extra. The Pro tier uses a local Docker stack for AI memory, but the extension handles setup automatically.
Yes. The MCP tools work with any MCP-compatible client. The terminal persistence is VS Code specific, but AI memory works everywhere.
Your terminals keep working (that's free forever). AI memory data stays on your machine — you just lose access to the MCP tools. Re-subscribe anytime to get them back.