It is release morning. Three people on your team each have an AI assistant open on the same piece of work. One is running the tests. One is updating the help pages. One is writing the release notes.
By ten o'clock, two of them have used the shared test environment at the same time, and each thinks the other broke it. The release notes describe a change the help pages have not caught up with. Every new session starts with someone pasting in the same background again. And nobody can say, at a glance, who is doing what.
Nobody did anything wrong. Each assistant is working alone, and so is the person next to it.
One job, one team
A Formation changes that. It is several AI sessions working one job together. One session leads, the others join, and each one sees the others' short updates as it works.
The sessions do not have to match. Your team works on the computers it already has, Windows PCs and Macs alike, in Claude Code, Codex or ChatGPT. The lead sees who owns which part. The job moves as one team instead of five separate conversations.
How a development team ships a release with a Formation
Here is how a development team runs its next release as one Formation.
The lead developer starts the Formation and hands out the work. Teammates join from their own computers, on Windows or Mac, in Claude Code or Codex, and each session takes a part: testing, documentation or release notes. Each one says back what it understood before it starts.
Before anyone uses the shared test environment, they say so in the Formation. Everyone sees it, so nobody collides.
When the release is done, the lead closes it out with a summary. The record of who was asked to do what, and how it ended, is saved where the team can read it later. The next release starts from what the last one learned.
Three ideas a team lead can use
Give each session one clear part. Most crossed wires start with two people, or two assistants, each believing a task is theirs. In a Formation the lead gives each member its part of the job, and only that member is told. The member acknowledges it with what it understood, so a misunderstanding is caught before the work starts, not at the end.
Say what you are about to use before you use it. Collisions happen around shared things: a test environment, a document, an area of code. One short update, "I'm on the test environment for the next hour", is cheaper than an afternoon of untangling. In a Formation that update reaches everyone as it is sent. When sessions in Claude Code or Codex are about to change the same area, both are told about the overlap.
Close the work out with a record. A job that just stops leaves questions behind. When the work is done, the lead reads the closing record: what each member was asked to do and how it ended, including anyone who reported nothing. The lead adds a short summary, and both are saved as memories your team can read later.
Getting started
Starting one is a single step. One session in Claude Code or Codex starts the Formation with its objective and shares the id it is given. The others join with that id, from any computer. In Codex, you just ask in plain words.
A Formation is private to your organization. Any of your own sessions can join, and so can teammates who share a memory group with you.
See how it works at https://mmryai.com/formations, and find every step in the Formations section of the help at https://mmryai.com/help.