Projects & sessions

Two words come up a lot: project and session. They're easy to confuse early on, so here's the difference.

Projects

A project is one body of work. It holds your notebooks, the files in the workspace, the branches of each notebook, and your sessions. Think of it like a repo or a folder: one analysis, one model, one investigation. "Q3 churn," "receipt classifier," "clean the pricing data."

When you sign in, the dashboard shows your recent projects so you can pick up where you left off. Each project also has a default runtime. New projects start on CPU, and you can change that.

Sessions

A session is a single conversation with the agent inside a project, and you can have several. You might keep one session for cleaning, another for feature work, another for modeling, each with its own chat history. They all see the same notebooks and files. What's separate is the conversation.

Sessions live under the Chats tab in the sidebar. Starting a new one gives you a fresh conversation without losing the old one.

Why bother splitting them up? Long chats drift. Keeping each line of work in its own session keeps the agent focused on the task in front of it, and makes it easier to come back to a specific thread later.

How they fit

The notebooks, files, and branches belong to the project, so they're shared across every session. The chat and which branch you're looking at belong to the session. Two sessions in the same project see the same notebooks but have separate conversations, and one can be working on a different branch than the other. Edit a notebook in one and the change is there in the other, because there's only one notebook.

Project: "Churn analysis"
├── Notebooks   ·· shared
├── Files       ·· shared
├── Branches    ·· shared
└── Sessions
    ├── "Cleaning"   → own chat, own active branch
    ├── "Features"   → own chat, own active branch
    └── "Model"      → own chat, own active branch

Renaming and deleting

You can rename or delete a project from the dashboard. Deleting it removes its notebooks, branches, files, and sessions for good, so it asks you to confirm first.