PerchAI
Using Perch

The Chats tool

On Pro and Ultra, the agent can see your other chats, read one, send it a message or stop its turn, so one piece of work can hand off to another without you ferrying messages between them.

Most of the time a chat is a sealed room. The Chats tool opens a door between them: the agent in one chat can see what your other chats are doing, read one, tell it something, or stop it.

The point is handing off. A chat that just merged an API change can tell the chat working on the client to rebase and rerun its tests, and you never have to notice and relay it yourself.

The short version

Part of Pro and Ultra, in Perch Desktop and the CLI. Reading other chats is free of approvals; messaging or stopping one outside the current chat's own family is not.

What it can do

ActionWhat it does
ListYour recent chats: each one's id, folder, when it was last active, how it relates to this chat, what it is doing now, and what is known of its model, mode and where it runs.
LookOne chat in detail: what it is waiting on, the start of its last reply, what its last turn produced, and its parent and sub-sessions.
MessageSend a message to another chat, to an agent of this chat, or to a sub-session. The receiving chat's model is told that another chat's agent sent it.
StopStop a chat's running turn, or an agent of this chat.

Approvals

Reading is read-only, so it never asks: a list or a look runs in every mode, Plan mode included.

Messaging or stopping depends on who the target is:

  • Inside this chat's own family, meaning its own agents, its sub-sessions or the chat that started it, the call runs.
  • Any other chat goes through the normal approval path. In Default Perch asks you, naming the chat by its title. In Auto Review the safety reviewer decides. In Take the Wheel it runs.

In Plan mode, messaging and stopping are held back along with every other change.

The hop limit

Chats messaging chats could loop on your usage, so every cross-chat message carries a hop count. A turn you started is hop zero; a turn started by a message takes that message's hop, and a message that turn sends is one more. After three hops the next message is refused, and the chain only resets when you type into it.

So a hand-off runs a few steps deep on its own and then stops and waits for you, instead of two agents talking past each other all afternoon.

Where it works

Perch Desktop and the CLI, on Pro and Ultra. A Starter account holding an Unlimited DeepSeek pass has it while the pass runs. The tool talks to Perch's server and to the runs in this process, never to your files, so nothing about it depends on folder access.