> ## Documentation Index
> Fetch the complete documentation index at: https://ade-ac1c6011-ade-mobile-chat-stability-54bd7ef0.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Work and terminals

> Run chats, terminals, provider CLIs, and managed sessions in lane-scoped workspaces.

Work is where active sessions live. A session can be a chat, an interactive terminal, an agent terminal, or a managed process opened from Run.

## Session types

| Type                     | Use it for                                                 |
| ------------------------ | ---------------------------------------------------------- |
| **Chat**                 | Ask an agent to inspect, edit, test, or explain.           |
| **Interactive terminal** | Run commands manually in a lane.                           |
| **Agent terminal**       | Watch commands an agent runs during a chat or worker task. |
| **Managed process**      | Follow logs from commands started in Run.                  |

## Lane scope

Each Work session belongs to a lane. Commands run in that lane's worktree, with that lane's environment. Check the lane label before typing or prompting.

## What ADE records

ADE keeps transcripts and metadata for sessions so you can revisit them later:

* Start and end time.
* Lane and working directory.
* Command output.
* Agent attribution.
* Related file changes.
* Links to commits, PRs, proof, or Linear issues when available.

## Recovery

If ADE restarts, it restores the visible session record and attempts to reconnect to live processes where possible. If a process is gone, the transcript still remains in History.

<CardGroup cols={2}>
  <Card title="Agent chat" icon="comments" href="/chat/overview">
    Use chat for agent-driven edits.
  </Card>

  <Card title="History" icon="clock-rotate-left" href="/tools/history">
    Search completed sessions and checkpoints.
  </Card>
</CardGroup>