Step 1 of 10
Launch the Session
5of 10~5 min
- The session start workflow
- How Agent Mail threads work
- Verifying session initialization
What you'll do
- Create a session thread
- Send kickoff to all agents
- Verify messages were delivered
Now comes the exciting part — launching the multi-agent session. The brenner CLI will send role-specific kickoff messages to each agent via Agent Mail.
1Spawn Your NTM Session & Set Variables
First, define your session ID and spawn the multi-agent panes using ntm spawn.
Terminal
2Launch via Brenner CLI or NTM Pipeline
You can launch role-separated kickoffs directly with brenner session start or run a declarative ntm pipeline from /brennerbot-with-ntm:
Terminal
What this command does:
- 1Registers the Orchestrator agent in Agent Mail
- 2Creates a thread with the session ID
- 3Sends role-specific kickoff messages to each agent
- 4Returns confirmation with message IDs
3Verify Messages Were Sent
Check that all three agents received their kickoff messages:
Terminal
Understanding Agent Mail Threads
Agent Mail organizes messages into threads. Each session has its own thread ID.
Thread: RS-2026-0105-cell-fate ├── [Orchestrator → BlueLake] KICKOFF: hypothesis_generator role ├── [Orchestrator → PurpleMountain] KICKOFF: test_designer role ├── [Orchestrator → GreenValley] KICKOFF: adversarial_critic role └── (awaiting agent responses...)
Warning
Session ID is critical: Use the same session ID throughout. It's how Agent Mail groups related messages and how brenner compiles the final artifact.
Pro Tip
You can watch the session in real-time with:
brenner session status --thread-id "$SESSION_ID" --watch. This shows new messages as they arrive.Session Launched? If you see three KICKOFF messages in the thread, you're ready to run the agents in the next step.