claude code native · local-first · sessions never die

ImmorTermthe immortal terminal.

It keeps your terminal sessions running through anything.

ImmorTerm is a terminal for developers who work with AI. When your editor crashes or your laptop restarts, the work you had running simply continues, and you come back to it exactly where you left off. It also remembers everything you and your AI worked on together, and reminds your AI automatically — so you never have to explain last week twice.

one command to install · the free plan is real · your code never leaves your machine

recalled 3 memories (8ms) · still running
immorterm — your session
$ npm run build
…41,207 lines of scrollback…
what it does

nothing dies, and nothing needs explaining twice.

ImmorTerm is two things working as one: a terminal whose sessions survive anything, and a memory that quietly files away everything you work on, so the right context comes back at the right moment.

the third dimension

your terminal was 2D. hover it.

Hold Cmd and hover: file paths open into live previews, images render in place, folders unfold into a browse tree, Claude's tasks show their context — the depth behind every line, without leaving the terminal. Multi-cursor and full text manipulation on Claude's input box included. It reads like a terminal; it behaves like a workspace with a z-axis.

immorterm — cmd+hover
demo footage — landing soon
the cockpit

drag anything into the conversation.

Drag a session onto another and its context comes along. Drag files and folders from the built-in browser straight into your prompt. Tasks carry their context too — a TODO knows the conversation that created it. Share pills stack up and consume on your next message. The terminal is the workspace.

psst — you can drag him.

immorterm — drag & drop
demo footage — landing soon
the canvas

your AI can see this terminal. and draw on it.

It takes real screenshots of your output. It highlights the line that failed, draws the chart, annotates the diff — inline, on the terminal itself. It opens workshops: interactive panels that survive across turns, wait for your click, and wake it back up. A closed loop of eyes, hands, and canvas — not a chat box bolted to a shell.

immorterm — ai canvas
demo footage — landing soon
the memory

it recalls before you ask. and your tokens stop bleeding.

Every session is digested as it happens — decisions, root causes, dead ends. When you type, recall runs on your machine, for $0 — no LLM call — and injects a few curated lines, not the wall. No giant CLAUDE.md preamble, no re-pasting files, no re-explaining the week. Prompts that don't need memory get zero tokens added: a classifier decides in under a millisecond. ~49ms end to end, local, no API key. the whole memory story →

immorterm — proactive recall
demo footage — landing soon
the archaeology

git blame says who. this says why.

Every edit and commit is linked to the conversation that produced it. explain_change correlates diffs, commits, and memories to answer the only question that matters six weeks later: why does this code look like this?

immorterm — explain_change
demo footage — landing soon

undo the AI

Pre-edit checkpoints on every file the agent touches. Revert one file — or everything a session did — in one call.

your laptop is just a window

Run the daemon on a remote box over SSH. Sessions live there, render here, and survive your flight.

gpu-rendered. not a text box.

WebGPU keeps thousands of lines smooth, overlays included. npm today; desktop app and VS Code extension coming soon.

comment on terminal output

Select output, leave a comment, and it survives scrolling — a review tool for the terminal itself.

claude code native

Hooks, tasks, and overlays wired for Claude Code specifically — not bolted on. Other CLIs come when there's pull.

23 water-lights

Hand-tuned 7-color themes — Matrix, Dracula, Ocean Depths, Hot Pink. Free ships the core set; Pro ships all 23.

how it works

three commands, and the resets stop.

Install it, open a terminal, and keep working the way you already do. Everything else — the memory, the hooks, the session protection — sets itself up underneath.

1
install
npm install -g immorterm
2
initialize
immorterm init --yes
3
add memory
immorterm memory install
install

one package. macos and linux.

coming up

Native desktop app + one-click VS Code extension. Today it's npm.

the memory
~8ms
recall. on-device. before you ask.

The memory digests every session as it happens. The next one opens already caught up — no re-explaining last week to your AI. While you were reading this it recalled twice.

recalled 3 memories (8ms) — tuesday you chose rotating refresh tokens. loading it before you ask.

the whole memory story →
under the hood

one mcp process. not five.

Open five terminals and naive MCP setups spawn five copies of every server. The gateway multiplexes them: stateless servers share a single child process; stateful ones get their own. A reaper watches session activity and cleans up orphaned PIDs on its own.

shared-process multiplexing

Stateless MCP servers run once, not once per terminal.

isolation where it matters

Stateful servers get a dedicated process.

self-cleaning

Activity-based reaper with PID-orphan detection. No manual cleanup.

zero config

Ships and runs underneath ImmorTerm.

a utility, not a product. it keeps your mcp servers from multiplying.

faq

the questions everyone asks.

What actually happens when my editor crashes?+

Nothing, to your session. The process runs in a daemon underneath your editor. When you reopen ImmorTerm, you reattach to the same live session — scrollback, running commands, and all. You were gone; it wasn't.

Do I have to change how I use Claude Code?+

No. Install, init, and keep working. Hooks and memory wire themselves; capture is ambient. If a tool asks you to babysit persistence, it isn't this one.

Does my code or data leave my machine?+

No. The terminal and memory are local-first — search, embeddings, and reranking run on-device in ~8ms. No API keys, no external calls for recall.

What's on Free vs Pro?+

Everything works on Free, and everything is captured and kept forever. Recall on Free reads 5 results from the last 72 hours; Pro ($29/mo) lifts the window and the result cap, and brings all 23 themes. The gate is a window, never a purge.

Is there a desktop app or VS Code extension?+

Both are coming soon. Today, install via npm — the same session shows up wherever you run it.

Which AI tools does it work with?+

Claude Code today, with the deepest integration. Other CLIs are coming when there's pull.

Why an axolotl?+

It's the most studied regeneration organism on Earth — it regrows limbs, heart tissue, chunks of its own brain, without a scar, and it never stops being itself. An animal famous for refusing to die, working for the immortal terminal. The fit was not subtle.

the depths

your sessions live down here, safely.

Crashes happen up in your editor, and the sessions down here never notice them. Each one keeps running, and each one is waiting for you to reconnect.

$ immorterm -ls
auth-refactor · claude · still running · 41,207 lines
embed-queue · zsh · still running · 12,033 lines
digest-daemon · claude · still running · 8,411 lines
three live sessions. the editor above them has died twice today.

go ahead and crash your editor — we'll wait.

pricing

free is real. pro remembers further back.

Free
$0

Everything captured, kept forever.

  • Persistent sessions — reattach after any crash
  • GPU rendering + inline overlays
  • 5 memory search results per query
  • 72h memory retention
  • All 41 memory tools, all hooks
  • Core theme set
install free
Pro
popular
$29/mo

For the long-running project.

  • Unlimited memory search results
  • Unlimited retention — whole history searchable
  • All 23 themes
  • Everything in Free
go pro

Free is genuinely free — no card, no trial clock. Nothing is ever deleted on Free; memories past the window are held, not purged. Memory alone is Memory Pro, $9/mo.

install immorterm once.
it outlives the editor.

local-first · ~8ms recall · claude code native · free is real