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

# Thread sessions

> Use chat threads as isolated, resumable agent sessions.

# Thread sessions

In Avibe, a chat scope can map to an agent session.

The practical rule:

```text theme={null}
Thread = session
```

Start five threads, run five independent jobs, and keep their context separate.

## Why it works

Chat threads are a natural unit of work:

* One production incident.
* One feature branch.
* One refactor.
* One investigation.
* One follow-up review.

The agent does not need a custom dashboard to understand the conversation boundary. The chat app already gives it one.

## Resume from anywhere

A session outlives the moment. Start a thread on your desktop, reply from your phone hours later, and the agent picks up with the same context — the thread *is* the memory. The [Workbench](/concepts/workbench) Inbox shows the same sessions you reach from chat.

## Routing and switching

Sessions compose with agent routing. Point different channels or projects at different agents — `#frontend` to OpenCode, `#backend` to Claude Code — and each thread runs the agent you mapped. You can also switch the agent mid-thread by prefixing a message with its name, without losing the session's context. Configure routing from the [Workbench](/concepts/workbench).

## Best practices

* Start a new thread for a new task.
* Reply in the same thread to continue the same task.
* Use short, explicit acceptance criteria.
* Stop or archive sessions that are no longer useful.

## Example

Top-level message:

```text theme={null}
Fix the login redirect bug. Reproduce it first, then patch the smallest root cause and run the relevant tests.
```

Thread reply:

```text theme={null}
Good. Also check whether the same redirect path affects signup.
```