LlamaTreeSessions and projects
A session is one agent (or any command) running in its own real terminal, in a folder you choose. Projects group sessions, and the Project view lines up every worktree of a repository.
Status dots
Every session's tab and tile carries a dot. Each state has its own colour, shape and motion, so you can tell them apart at a glance:
| State | Means |
|---|---|
| Working (blue) | The agent is busy. Its name shimmers on the tab too. |
| Needs your answer (pink) | The agent is asking for a permission, a question, a plan to approve or whether to trust the folder, and can't carry on until you answer. |
| Waiting for you (orange) | The session finished working while you weren't watching it. |
| Idle (green) | Done, and you've seen it. |
| Not running (grey ring) | The process has stopped. |
The palette button › Status dots offers four styles: Glow (the default), Classic, Calm and Signal. With your OS's animation effects turned off, the dots stay still and still differ in shape.
Each session has its own conversation
A new Claude session's command is just claude. LlamaTree gives it a conversation id of its own and starts it with --session-id, then --resume once something is saved, so restarting the app or the session always reopens the same conversation, even with several sessions in one folder.
- When you
/clearor/resumeinside Claude, LlamaTree follows it to the new conversation. - Hover a session's tab for its conversation's title and when it was last used.
- Commands with their own
--resume,--session-idor--fork-sessionare left alone.
Codex sessions work the same way, with a few differences: see Claude Code and Codex.
Resuming a conversation
In New session, or a session's ⋯ menu › Resume a different conversation…, pick any saved conversation from the list. Conversations used in the last few minutes are tagged active now: close them in any other terminal first.
Closing the window
Closing the window with sessions running asks what to do with them:
- Keep running closes only the window. The sessions carry on in the background, and opening LlamaTree again shows them as they are, with what they printed meanwhile.
- Stop sessions stops them, but loses nothing: each conversation is kept, and the sessions come back with the app. The question says which pick up where they left off and which start a new conversation.
Tick Don't ask again to always do one or the other; the version menu (top right) changes it, and has Quit and stop all sessions. With no session running, closing the window ends LlamaTree.
Restarting
After a restart, the sessions come back, each in its own conversation. A Claude or Codex session brought back after a restart waits until you first open it, or until another session sends it a message (its tile says Starts when you open it), so its start-up context is fresh and a session you don't open costs nothing. Sessions running other commands, such as a dev server, start straight away.
Projects
Projects group sessions, for example one product across its worktrees. Tick projects on and off in the Projects row; All and None do what they say, and Ctrl+click shows only one. Hidden sessions keep running, and each project's tab counts its sessions waiting for you, so a hidden project still gets noticed.
- Put a session in a project when you add it, by dragging its tab into the project's group, or right-click its tab › Move to project…
- Rename, recolour or delete a project by right-clicking it. Deleting a project keeps its sessions.
- Add a session to a project with the + at the end of its tab group: in the same folder, in a new worktree on a new branch, or in a different folder.
Project view
Click a project's name at the start of its tab group to see every worktree of its repositories in one table, including worktrees made outside LlamaTree. Each row shows:
- the branch and folder, and the session in it with its status dot;
- what the session is on: its latest prompt, or its conversation's title;
- how many files are changed, with a ⚠ when the same file is also changed in another worktree;
- how far the branch is ahead of (↑) and behind (↓) the base branch;
- its open pull request.
Click a row for the latest prompt and the start of the answer, the changed files and the actions: open the session, start one in a worktree that has none, view or create the pull request, or remove the worktree. Removing never forces: a worktree with uncommitted changes is left alone, and the branch stays. New worktree… on the toolbar adds one on a new branch from the base branch, with a session in it.
Where sessions are kept
Sessions are saved in %APPDATA%\LlamaTree\sessions.json on Windows and ~/.config/LlamaTree on Linux. Set LLAMATREE_DATA to use a different folder, for separate profiles. Only one copy of LlamaTree runs per profile; launching it again brings the window forward.