Projects and sessions

Each tab is one session, in one folder. Several projects can be open at once, and everything comes back after a restart.

Tabs

File → Open Project… (Cmd/Ctrl + O) opens a folder in a new tab. Add Project… adds another without replacing what you have.

Each tab keeps its own folder, model, effort and permission mode. Changing the mode in one tab does not touch another.

A tab you are not looking at shows an indicator when something happens in it — and if Claude needs an answer there, you get a notification.

Sessions and history

Vitrino does not keep its own copy of your conversations. Claude Code already stores them, and Vitrino reads that store — so a session you started in a terminal is visible in Vitrino, and the other way round.

The sidebar lists past sessions for the folders you have open, newest first. Cmd/Ctrl + K focuses the filter. Opening one resumes it: Claude keeps the context it had.

Sessions can be renamed from the sidebar. The name is stored with the session, so it is the same name in the terminal.

After a restart

Vitrino reopens the tabs you had, with unsent drafts still in the box. Sessions resume when you go to them rather than all at once, so starting up is not slow because you had eight tabs open.

The same recovery runs if a window's renderer crashes: the live sessions that window owned are closed, the page reloads, and your tabs and drafts come back.

`/clear` and compaction

Two things end a conversation's memory, and they are different:

/clear discards it. Claude Code starts a new session id; nothing above the line in the transcript reaches Claude again. Vitrino draws a marker you cannot miss, and follows the new session — so reopening the tab later gives you the conversation after the clear, not the discarded one.
Compaction (/compact, or automatically when the window fills) replaces the earlier conversation with a summary. Claude keeps the gist, not the detail.

Where things are stored

What	Where
Conversations	Claude Code's own store, under `~/.claude`
Your API key, and preferences	Vitrino's application data folder, via the OS's standard location
Logs	`logs/main.log` in that same folder

Settings → About links to the log folder directly, which is easier than finding it by hand.

Keyboard shortcuts.