Editor tour
By the end of this page you will know where every setting lives, what each centre view is for, and how saving, publishing and deploying relate to each other.
Prerequisites
- A Planner / Executor system created (Create a MAS).
- Admin or Developer role.
The editor at a glance
The system editor is a full-screen editor with three panes. Drag the dividers to resize them.
| Pane | What’s in it |
|---|---|
| Left | Two tabs: Configuration and Live. |
| Centre | One of three views of your team and its work. |
| Right | The live chat preview. |
The header
From left to right:
- Back — returns to the Agent Systems list.
- Configure Planner / Executor, with the system name beneath it.
- Badges — version state: New (nothing saved yet),
v2 • DRAFT(an unpublished draft), Prod: v1 (the live published version), and Unsaved whenever you have pending changes. - The chat preview toggle.
- Save, Publish, Deploy, and — once a draft exists over a published version — an overflow ⋮ menu with Discard Draft.
Each action unlocks the next one:
| Action | Enabled when |
|---|---|
| Save | You have unsaved changes |
| Publish | Everything is saved and a draft version exists |
| Deploy | A published production version exists |
The left panel
Configuration
Everything that shapes how a turn is handled, in six numbered groups plus a turn budget and an Advanced section. Each group states what it is for above its controls.
See Planning settings and Loops, failures & approvals for what each control does.
Live
The running commentary of the turn in progress: which step started, what each agent did, what it wrote to shared memory, and any tool activity. Memory writes appear in the same feed, tagged Memory, so a write and the tool calls that produced it stay in order.
Use Live while a preview turn runs, and Configuration between turns.
The three centre views
Each view answers a different question, which is why none of them replaces another.
| View | Answers |
|---|---|
| Canvas | ”What did this turn actually do?” — the plan the system generated, drawn as a diagram of steps |
| Agent map | ”What is the shape of this thing?” — the planner and every agent it can call |
| List | ”Who is on the team, exactly?” — the member catalog, as text |
Canvas is where you start, because watching a plan build itself out of your team is what this pattern is. It is empty until a turn runs — there is no plan to show before then.
Agent map shows the structure rather than any one turn: one planner, the team it may call, and nothing authored in between.
List is the plain catalog, and the easiest view to work in on a narrow screen.
Save, publish, deploy
- Save writes your configuration into a draft version. Do it often; the live deployment is untouched.
- Publish turns the current draft into an immutable production version. See Publish.
- Deploy puts a published version behind an endpoint. See Deploy.
The chat preview runs your saved configuration, not what is currently on screen. After changing anything, click Save, then send a new message.
Common issues
- The Canvas is empty — No turn has run yet. Send a message in the preview.
- Publish is greyed out — You have unsaved changes, or nothing has been saved yet.
- A preview message does nothing — The system has no members. See Your team.