---
title: "Hand threads to your agents, and take them back"
description: "Assign any thread to a person or an agent. Agents are told the moment a thread is theirs with the new thread.assigned MCP event, and a person can take a thread over to pause agents on it until they hand it back."
canonical: "https://machinemail.dev/changelog/assign-threads"
date: "2026-11-17"
---

# Hand threads to your agents, and take them back

> Assign any thread to a person or an agent. Agents are told the moment a thread is theirs with the new thread.assigned MCP event, and a person can take a thread over to pause agents on it until they hand it back.

- Date: 2026-11-17
- Tags: Dashboard, API, CLI, MCP, Webhooks
- Video: https://machinemail.dev/changelog/media/assign-threads.mp4 (A simplified MachineMail dashboard. The inbox support@acme.example lists threads with owner pills for teammates and agents, Dana, Agent and Sam; choosing the Unassigned tab leaves the thread Refund for order 4411 from Maya Chen, which is opened. Its owner button reads Unassigned, and ChatGPT, a connected app, is picked under Agents. A lockup follows, in which a white dot travels from the MachineMail mark to the ChatGPT mark, and Works with ChatGPT appears. In a dark ChatGPT chat, a MachineMail bubble says the thread is yours; ChatGPT replies that Maya wants a refund, refunds need a person, so it drafted a reply and handed the thread to Dana, shown as Assigned to Dana Reyes. Back in the dashboard the owner button reads Dana Reyes with an orange square, and a banner says an agent saved a draft reply. Dana opens the draft, marked Drafted by ChatGPT, and chooses Send now. The sent reply in the thread reads Drafted by ChatGPT, sent by Dana Reyes. Finally Dana chooses Hand back to ChatGPT and a toast says Handed back to ChatGPT. It ends on the MachineMail logo.)
- Source: https://machinemail.dev/changelog/assign-threads

An inbox shared by people and agents needed a way to say who is handling each conversation. Now every thread has an owner. Assign it to an agent and the agent is told straight away; take it over yourself and agents leave it alone until you hand it back.

- **Assign from the thread.** The owner button in the thread header, beside **Show raw**, lists everyone who can take the thread: members, API keys, connected apps such as ChatGPT or Claude, and claimed agents. **All**, **Mine**, **Agents** and **Unassigned** above the thread list filter the inbox by owner.
- **Agents hear about it at once.** MCP clients that support events, such as ChatGPT, can subscribe to `thread.assigned` and are woken when a thread is assigned to them or taken from them. Pair it with `message.received` and `assignee: "me"` to wake an agent only for replies in its own threads. Clients without events call `list_threads` with `assignee: "me"` for their queue.
- **Take over, hand back.** &#x2A;*Take over (pause agents)** assigns the thread to you and marks it with an orange square. Agents get no new-mail events for it, including replies that arrive while you have it, and `get_thread` tells any agent that opens it not to reply. **Hand back** returns it to the agent that had it.
- **Agents can loop in a person.** With `assign_thread`, an agent can claim a thread or hand it to a teammate, for example when a refund needs approval or a customer asks for a human. It can save a draft reply first: when your teammate sends it, the message reads "Drafted by ChatGPT, sent by Dana Reyes".
- **On every surface.** Send `assignee` with `PATCH /v0/threads/{thread_id}`, filter List Threads with `assignee=me`, `none`, `people`, `agents` or one assignee, or run `machinemail threads update --assignee`. Webhooks can opt in to `thread.assigned` too.

Read more: [Hand threads to an agent](https://machinemail.dev/docs/guides/hand-threads-to-an-agent) and [Thread assignment](https://machinemail.dev/docs/concepts/thread-assignment).
