---
title: "Workspace"
description: "Use a workspace to bound what the agent can touch."
lang: en
---

The workspace is the boundary the agent may operate within. Pick a workspace and every file operation is confined to it.

## Why the boundary exists

Without one, an agent can follow a relative path out of the project and change unrelated files. A workspace keeps the impact inside a directory you explicitly chose. This layer is independent of approval settings and cannot be relaxed by auto-approval.

## Switching workspaces

Different projects use different workspaces. After switching, new sessions use the new workspace; existing sessions keep their own paths.

## Inspecting the project

The agent only expands directories inside the workspace, which lets both you and the agent get oriented quickly.

## Project settings

Once a workspace is selected, a gear appears next to the “project directory” pill beside the input box. It configures **this project**:

- **Prompt**: a project system prompt, appended after the global prompt and written to `.bi/agent.md` inside the project. The field shows the byte count live and refuses to save beyond 64 KB.
- **Plugins**: all enabled by default; unchecking a plugin disables it for this project only, leaving the global setting untouched.
- **Skills**: skills declaring `pin: true` can be pinned as project-level always-on skills, injected into every session under this project.

Changes across the three tabs are saved together when you press Save; switching tabs only changes the view. The entry is hidden when no workspace is selected.

## Related

- [Sessions](/docs/using-bi/sessions)
- [Operations that need approval](/docs/configuration/permissions)