Projects, Worktrees, Sessions

If Jean feels simple when it is new and still usable when it is full, this model is the reason.

The hierarchy

Jean organizes work like this:

Folder
└── Project
    ├── Base session
    │   └── Session tabs
    └── Worktree
        └── Session tabs

A project is the repository Jean knows how to operate on.

Projects can hold defaults such as:

A base session uses the project's main directory directly.

Think of it as the stay-on-the-trunk option.

Use it when:

A worktree is a branch-backed workspace with its own path and lifecycle.

Jean tracks metadata around each worktree, including:

Use a worktree when:

A session is a chat thread inside a base session or worktree.

Sessions also keep UI and workflow state such as:

Jean can either archive or permanently remove items when you close them, depending on your preferences.

Archiving is useful when you want a cleaner active workspace without losing the conversation or worktree record.

Jean also tracks enough metadata to help you resume work:

That makes the canvas feel more like a work queue and less like a raw file tree.