> ## Documentation Index
> Fetch the complete documentation index at: https://dshtauri.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspaces and sessions

> Start Harness sessions in the right workspace and keep code changes isolated.

A session combines a conversation with a workspace where Harness tools can read and
change files. Select the workspace deliberately: it defines the boundary of the task.

## Start a session

<Steps>
  <Step title="Choose a workspace">
    Open or select the repository or folder you want the agent to work in. Check the
    displayed path before authorizing file operations.
  </Step>

  <Step title="Create a session">
    Start a new session and state the outcome, constraints, and validation you expect.
  </Step>

  <Step title="Review tool activity">
    Follow commands and file changes in the session. Inspect diffs before committing or
    publishing work.
  </Step>
</Steps>

<Frame>
  <img src="https://mintcdn.com/dshtauri/wkB541IUjMIrkizA/images/en/workspaces-sessions.png?fit=max&auto=format&n=wkB541IUjMIrkizA&q=85&s=690a3af56d1e312f88ef89e23af79d9c" alt="Workspace selector and session list" width="1747" height="1114" data-path="images/en/workspaces-sessions.png" />
</Frame>

## Isolate changes with worktrees

The bundled worktree integration can create a Git worktree per session. This keeps
concurrent tasks on separate branches and protects the repository's main checkout.
When the work is ready, check it out to a local branch; when it is disposable, archive
or abandon the isolated worktree.

<Tip>
  Use one session for one concrete objective. Separate sessions reduce accidental
  context mixing and make branches easier to review.
</Tip>

## Safe operating habits

* Confirm the current workspace and branch before accepting changes.
* Keep secrets outside prompts, source files, and command output.
* Review third-party plugin permissions and source.
* Commit meaningful checkpoints before broad refactors.
* Treat generated commands as code review material, not as inherently trusted output.

For runtime data boundaries, see [Data and privacy](../help/data-and-privacy).