Describe a task and work with a team

Projects and threads

A project is a folder. A thread is one task in it, with its own conversation and history. Start as many threads as you like and run several at once. The sidebar shows which are running, and Mission control (the layers icon on the left rail) shows every thread of every project in four groups: Needs you, Running, Ready for review and Done.

• Search every conversation, pin the ones you keep returning to, and archive the rest.
• A thread can be forked from any of your messages (hover the message and use the ⋯ menu), or you can Edit and resend a message. The original keeps everything it had.
• A side conversation (/side) lets you ask a question about the thread without disturbing its run.

The message box

Write the task the way you would tell a colleague: what it should do, who it is for and anything it must not touch. The footer of the box holds the attach button, the access mode, the team, the model and Send. Once you have typed something, the box shows an estimate such as “About 40 cents · ~6 min”.

• Attach pictures and files with the plus button, by pasting or by dragging them in.
• @ mentions. Type @ to point at a file, a folder, another thread or a skill. Each shows as a chip above the text.
• Slash commands. Type / as the first character to see every command, with the ones that cannot run now shown dimmed with the reason.

Choose a team

With the Full squad, the architect shows a design with diagrams before anything is built, and nothing is built until you approve it. Pressing Approve and build on the design card is your go-ahead.

You can design your own agents and teams under Customize. See Customize Maxtkn.

Plan first

Turn on Plan first, or accept the hint that appears on a long request. The lead may ask one question (with options, your own answer, or “Skip, decide for me”). Then a Plan for your approval card appears with a chip saying nothing has been changed yet. Edit, reorder, remove or add steps, then press Proceed, or Ask for changes to send a comment and get a new plan.

While the team is working

• The box stays usable. A Steer / Queue choice lets a message join the run that is going, or wait until it ends.
• Stop ends the run at once. Nothing half-written is left on disk.
• The timeline shows each agent’s steps, tool calls and approvals. A Reasoning tab and a live reasoning card show what each team member is thinking, for models that provide it. A setting chooses whether that is open, collapsed or hidden.
• If a run goes quiet for six minutes with no event and no waiting approval, it is stopped and flagged instead of hanging.
• Notifications tell you when something needs you or has finished, unless the window is in front.

Slash commands you will use

Keyboard shortcuts