--- 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 | ## Thread list groups The sidebar groups threads into collapsible **Ready**, **Needs attention**, **In progress**, **Failed**, and **Archived** sections. Pull-request state participates in grouping: conflicts, failing checks, and unresolved comments can move an otherwise finished thread into **Needs attention**, while running checks keep work in progress. Hoplite remembers which sections you collapse. Transitions among `queued`, `running`, `waiting`, `blocked`, and `ready` appear after the new state has remained stable for five seconds, which keeps brief backend handoffs from bouncing rows between groups. Initial state, `failed`, and `archived` remain immediate, and run actions always use the authoritative state even while a row briefly shows its previous status. Archived threads leave the active groups and collect in the collapsible **Archived** section at the bottom of the list. Open it to find and unarchive earlier work. ## Titles, labels, and notes Thread titles are generated automatically from the opening and recent conversation context. They can be a concise phrase or short sentence of up to 12 words and 100 characters; attachments and incidental actions are treated as evidence rather than the subject. The agent can correct a materially vague or outdated generated title as the purpose becomes clearer, but does not churn an already accurate one. 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 ` to override the title, and `/note ` to pin a note to the thread — handy for context the whole team should see. Right-click (or long-press) a cloud thread row for a context menu with actions like **Open in new tab**. When viewing another member's thread, choose **Add to my threads** from that menu to become a participant and include it in your **My threads** view. This follows the thread without posting a message. ## Archive or delete a thread with an open PR If a thread has an open pull request, Hoplite asks whether to leave it open, convert it to a draft, or close it before archiving or deleting the thread. Draft is the recommended archive choice because the work may resume; close is the recommended delete choice, and you can include an explanatory PR comment. If the provider update fails, Hoplite does not silently continue with the lifecycle action. Workspace owners and admins can set separate archive and delete defaults under **Settings → Workspace → General**, and can either ask every time or apply those defaults automatically. The same area controls automatic archival when a linked PR becomes merged or closed; Hoplite archives the linked thread and its workspace only when no other open linked PR still needs them. ## 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. Historical thread text is treated as reference material, never as instructions, and this does not give ordinary thread runs unrestricted access to workspace history. ## Sitemap See the full [sitemap](/docs/sitemap.md) for all pages. Well-known sitemap: [/docs/.well-known/sitemap.md](/docs/.well-known/sitemap.md).