---
title: "Sessions"
description: "How sessions are stored, bound to workspaces, and exported."
lang: en
---

A session keeps one complete unit of work together: the conversation, the execution trail, artifacts and usage statistics.

## What a session stores

Sessions are stored locally. A session records your conversation with the agent, what the agent did (files read and written, commands run) and usage statistics, so you can review it later.

## Sessions and workspaces

Each session can bind its own workspace:

- Give each project its own session, and the agent stays inside that session’s workspace
- Without a per-session setting, the session uses the global workspace

That lets one Bi process move several independent projects forward at once.

## Managing sessions

Pin, rename or delete sessions. Deleting a session also removes its conversation records.

## Exporting

Export a session as a Markdown file inside the workspace. The export is plain text containing your prompts, the agent’s replies, its reasoning, the execution trail and results, plus approval records — useful for archiving or handing the work to another AI tool.

## Related

- [Workspace](/docs/using-bi/workspace)
- [Long conversations](/docs/advanced/context)