Close it. Crash it. It keeps running.
Every terminal in DevMesh Space is backed by a session daemon. Quit the app, lose power, or hit a crash — your builds, dev servers, and agents keep going headless, then reattach with full scrollback.
What Is
DevPersist?
In most editors and terminals, the process and the window are the same thing. Close the window and you kill the build. Crash the app and you lose the agent run. DevPersist breaks that coupling.
Every PTY in DevMesh Space lives inside a session daemon that runs independently of the UI. The window is just a view. Close it and the daemon keeps every process alive, buffering output headless.
Reopen the app and each terminal reattaches in milliseconds with full scrollback — including everything that streamed while you were gone. Nothing lost, nothing replayed from scratch.
$ app quit — window gone ↳ daemon pid 4821 still alive build running pty/0 73% dev-server running pty/1 ↑ 4321 agent:scout running pty/2 $ app reopen ↳ reattaching 3 sessions… ✔ scrollback restored · 0 lines lost ✔ caught up: 2 events while away
How DevPersist Works
Spawn a terminal
Open any PTY in DevMesh Space. It's created inside the session daemon, not the renderer — the window is just attached to it.
Run something long
Kick off a build, a test suite, a dev server, or an agent. The process streams into the pane as usual.
Close, crash, or reboot
Quit the app, lose power, or let the UI crash. The daemon keeps every process alive and keeps buffering its output headless.
Reopen and reattach
Launch DevMesh Space again. Each terminal snaps back with full scrollback — including everything that streamed while you were away.
See what you missed
Output that landed during the gap is marked so you can catch up at a glance. Nothing is lost, nothing is replayed from scratch.
Why It Sticks
The window is disposable. Your work isn’t. DevPersist makes that the default, not a setting you remember to turn on.
Daemon-backed PTYs
Every terminal lives in a background session daemon, not the window. The UI is just a view onto processes that outlive it — quit the app and the PTY keeps its file descriptors, working directory, and environment.
Full scrollback restore
Reattach and every line is there — including the output that streamed while the app was closed. The daemon buffers stdout/stderr headless, so nothing between your last view and now is lost.
Crash-proof long tasks
Builds, test suites, dev servers, and agents survive a quit, a crash, or a forced reboot of the UI. Pick up exactly where you left off — mid-build, mid-run, mid-thought.
Reattach in milliseconds
Restart and sessions snap back instantly. No replaying logs from disk, no waiting for a process to respawn — the daemon was running the whole time.
Catch-up on what you missed
A test that finished while you were gone, a deploy that completed, an agent that asked a question — it's all waiting, marked so you can see what landed during the gap.
One daemon, every terminal
Open ten panes across five repos. They all attach to the same daemon, so closing the window never kills a single one. Power user workflows stay intact across restarts.
Frequently Asked Questions
Never lose a running session again.
DevPersist ships inside DevMesh Space — every terminal is daemon-backed by default. Nothing to enable.