Many agents at once
Keep several agents working and visit each conversation from one terminal. Press Ctrl+G or type /agents to open the list.
To start with the list instead of a conversation:
tatu agentsOpen an agent
Section titled “Open an agent”Each row shows the session title, project folder, git changes and current activity: idle, working, running a tool, waiting for you, done or failed.
Select a row and press Enter. You can read the conversation, send a message and answer its questions. Open the list again to switch to another agent; switching views does not stop its work.
To interrupt an agent, open it and press Esc. Or select it in the list, press X and confirm with Y. This interrupts the current run, not the session.
When another agent needs an answer, the footer shows a note such as ● 1 waiting · ctrl+g. Open the list to find it.
Start another session
Section titled “Start another session”Choose + New session to open a session in a folder on this computer. Tatu starts the daemon when needed; the new session runs separately from the terminal you use to visit it.
For agents on a paired computer, see Another computer’s agents.
Sessions that open by themselves
Section titled “Sessions that open by themselves”Choose ⏰ Automations or press S to see the automations and make new ones. When some will run, the header of the list says so, for example ⏰ 3 automations · next 09:00. The sessions they open are ordinary agents in the list, named ⏰ <name>. See Automations.
Leave without stopping the wrong agent
Section titled “Leave without stopping the wrong agent”Use /quit to leave the terminal. Agents you are visiting keep running. Your terminal’s own agent stops when you quit; if you are viewing another agent while your own is working or waiting, Tatu asks you to confirm. In the initial tatu agents list, Esc quits.
/logout and /remote do not run on an agent you are visiting. Use them in that agent’s own terminal. /login does, with the same list of providers, showing what that computer has: the credential is stored on the computer the agent runs on, and the page opens in your browser, here. When a sign-in comes back to a local address (the subscription logins of Claude and ChatGPT, OpenRouter and MCP servers), your terminal catches the code and gives it to the agent, so there is nothing to paste. If that port is busy here, paste the code as usual.