---
title: "Manage threads"
description: "Thread statuses, titles and labels, notes, transcript export, and organization history"
canonical_url: "https://hoplite.sh/docs/threads/manage"
markdown_url: "https://hoplite.sh/docs/threads/manage.md"
---

# Manage threads
URL: /docs/threads/manage
LLM index: /llms.txt
Description: Thread statuses, titles and labels, notes, transcript export, and organization history
Related: /docs/threads/run, /docs/threads/cost, /docs/agent/slash-commands

# Manage threads

A thread's status tells you when it needs you, and its title, labels, and notes keep it findable. This page covers the lifecycle and the housekeeping.

## Thread statuses

| Status | Meaning |
| --- | --- |
| `queued` | A run is waiting to start |
| `running` | The agent is actively working |
| `waiting` | The agent is paused — usually waiting on your approval or input |
| `blocked` | The run can't proceed without you |
| `ready` | The agent finished and is waiting for your next message |
| `failed` | The last run errored — [retry from the last checkpoint](/docs/threads/run#retry-from-a-checkpoint) |
| `archived` | The thread is closed out |

## Titles, labels, and notes

Thread titles are generated automatically from the conversation. Hoplite can also attach a small set of generated label chips to thread rows and headers, which makes related work easier to scan. Labels are supplemental metadata, not an alternative to a title.

Use `/rename <new title>` to override the title, and `/note <text>` to pin a note to the thread — handy for context the whole team should see.

## Export a transcript

Open the thread actions menu and select **Export transcript** to download a Markdown copy of the readable chat conversation.

| Included | Excluded |
| --- | --- |
| Thread title | Private execution context |
| Timestamps | System and tool messages |
| User and Hoplite chat messages that are safe to share | Tool inputs and timeline metadata |

## Search organization history

Authorized organization-level agent sessions can search prior normal, project-backed threads that the invoking user is already allowed to access. Search returns compact excerpts, and the agent can retrieve a selected public user or assistant message for context.

<Callout type="info" title="Scoped by design">
Historical thread text is treated as reference material, never as instructions, and this does not give ordinary thread runs unrestricted access to workspace history.
</Callout>

## Sitemap

See the full [sitemap](/docs/sitemap.md) for all pages.
Well-known sitemap: [/docs/.well-known/sitemap.md](/docs/.well-known/sitemap.md).