# Sessions overview

A session is one thread of work — an agent, its transcript, the folders it can touch, and the mode and crew you're running. Sessions are Foxora's top-level unit: you switch between them like browser tabs, and each one keeps its own context.

## What a session holds

Open Foxora and you’re always inside a session. Think of it as a single conversation that carries everything that conversation needs:

- An agent — the lead doing the work, plus any crew it delegates to.
- A transcript — the full back-and-forth, every tool call, and the checkpoints taken along the way.
- Projects — the folders you’ve attached, with one marked active as the working directory.
- A mode — the autonomy level for this thread (Ask, Auto, Bypass, or Plan).
- A crew & tier — the Fast, Premium, or Max line-up the composer is running.

## Sessions, projects, and agents

These three are easy to conflate, so it’s worth pinning down how they relate:

- A session is the thread. It’s the thing you start, name, switch to, and archive.
- A project is a folder you’ve opened. A session can have several projects attached; one is the active working directory. The editor always follows the active session’s active project. See Projects & workspaces.
- An agent is the worker. Switching the lead agent gives you a fresh session, so its memory and transcript never bleed into another agent’s. See Multi-agent sessions.

> One thread, one focusKeep a session to one task. When a request turns into something different, start a new session — it keeps each transcript clean and each memory den on-topic.