1# Durable session recovery
2
3Named sessions are saved to disk and come back after a daemon restart. This page explains what is saved, what can go wrong, and how to recover.
4
5## What is saved
6
7- Session name and working directory.
8- Tabs and layout.
9- Scrollback and the last visible screen, restored as copy-mode history.
10- Allowed processes are relaunched (see `snapshot.restore_processes` in [configuration](configuration.md)).
11
12The live process state, cursor, and terminal modes are not restored.
13
14vev keeps the latest checkpoint and the one before it as a fallback.
15
16## Session states in `vev ls`
17
18| State | Meaning |
19|---|---|
20| `up` | Running. |
21| `temporary` | Running numbered session. Not saved to disk. |
22| `down` | Saved and stopped. Attaching restarts it. |
23| `broken` | Saved state could not be loaded safely. Attach is refused until you recover it. |
24
25## Recover a broken session
26
27```sh
28vev cmd -s NAME session-recovery discard
29```
30
31This deletes the saved tabs, layout, and history of `NAME`. The name and working directory are kept, so the next attach starts a fresh session.
32
33## Upgrades
34
35- A new vev release converts the old session catalogue automatically at startup. A backup is written next to it as `sessions.kv.pre-v6.bak`.
36- To go back to an older vev, stop vev and restore that backup first.
37- When the checkpoint format changes, old checkpoints are reset: names and working directories stay, but tabs, layout, and history are cleared.
38- Installing a new binary does not restart a running daemon. Run `vev kill --all` to switch.
39
40## When the daemon refuses to start
41
42If the session catalogue cannot be read, the daemon stops instead of starting empty. This protects your data.
43
441. Do not edit or delete files in `~/.local/state/vev/`.
452. Look for `catalogue_validation_failed` in `~/.local/state/vev/vev-daemon.log`.
463. Fix the cause (disk full, wrong file owner), then start vev again.
474. For real corruption, back up the whole directory before trying anything else.
48
49A `lifecycle_owner_wait` log line means another daemon is still starting or stopping. Wait for it to finish.
50
51## Where files live
52
53| What | Where |
54|---|---|
55| Catalogue, snapshots, logs | `~/.local/state/vev/` |
56| Socket and lock | `$XDG_RUNTIME_DIR/vev/` |
57
58Recovery logs never contain terminal content.