Tutorials
Two sessions working together
Spawn a second session, send it a follow-up while it works, and read back what it did.
At the end of this you will have spawned a second session from the session you are in now. You will also have sent it a follow-up while it worked and read back the file it wrote. It takes about five minutes.
You ask for all of this in plain language, in the composer. Turret has no dedicated button for spawning, messaging or reading another session.
- A session already open, in any mode, since every mode loads spawning, messaging and reading.
- Type
Spawn a child session in this same working directory. Give it this task: create a file named hello-from-child.txt in the current directory containing the single line Hello from the child session.into the composer and press Send. A new row appears nested under this session's own row in the sidebar, with a disclosure arrow beside it. The reply names the file it asked the child to create. - Type
Message the child session you just spawned and ask it to append a second line to hello-from-child.txt saying Second line added by follow-up.into the composer and press Send. The reply confirms the message reached the child. - Type
What did the child session report when it finished, and what does hello-from-child.txt contain now?into the composer and press Send. The reply reports what the child did, then prints the file's current contents — both lines.
The task you gave the child in the first step arrives in its own transcript. Turret marks it as sent by another session. See Sessions that talk to each other, and how that differs from subagents for why.
Next
- Read a subagent's conversation for how a subagent nested under a session differs from the child session you spawned here.
- Queue a message while a turn runs for what happens when you send a message while a session is still working.
- Archive a session for removing a session once you are done with it.