Flows

Flows are part of Pro and still in beta: the menu marks New flow Beta. A flow is a frame on your canvas with chats and cards in it, joined by arrows. When a chat in the frame finishes an answer, the answer goes along its arrows: to the next chat as its next message, onto the end of a note, or into a card. You start it from the frame's Start, and it can also start by itself on a schedule.

A flow can be a team working down a list, a review from several sides, a council of different AIs that gives you one answer, a pipeline (research, write, edit), or a digest that runs every morning. You can see every step: each chat is a normal chat card you can read, type in or stop.

Flows replaced swarms and Automations in October 2026. A swarm you had becomes a flow the first time you open Morphy: its chats come out into a frame, in a column, and its brief and any waiting messages come along. An automation you already had stays on your canvas and keeps working as before: its runs, its outputs and its conductor chat. You can still run and change it, but new ones are flows.

Make oneCopy Anchor Link

Right-click the canvas and pick New flow. A frame appears with your own Morphy beside it, joined to the frame by a thin line, asking what the flow should do. Tell it in your own words, like "write two video scripts about our launch, let me pick one, then turn it into a storyboard". Morphy builds it: the chats, the arrows between them, a card where you need to choose or fill something in, the brief and a schedule if you want one. Keep talking to it to change the flow later.

Things Morphy often builds:

• Team: three chats share a list of tasks. Type one task per line; each goes to whichever chat is free.
• Review from three sides: every chat gets the same thing and reviews it its own way (mistakes, what could be simpler, what a reader would miss). Their reviews land in a note.
• Council: four chats answer from four roles (builder, skeptic, simplifier, user advocate), each on a different AI you have connected where it can. A fifth chat waits for all four and writes one answer: what they agree on, where they disagree, what nobody checked, and a recommendation. It lands in a Decision note.
• Pipeline: research, then write, then edit, into a Result note.
• Review loop: a chat makes something, and you look at it before it goes on.
• Daily digest: every morning at 08:00 two chats look at what you tell them to watch, one writes it up, you approve it, and it lands in a note.

For now a flow lives outside projects: inside a project's frame, New flow is greyed out. Its chats can still work in a project's folder. You can also ask the Morphy in your sidebar: "make me a flow where three chats each review my landing page and one writes up what they agree on".

What Morphy builds is a start. Change anything yourself: drag more chats or cards into the frame, draw arrows, delete the ones you don't want.

Start itCopy Anchor Link

Click Start on the frame (the chip at its left, or ▶ Start in its name row). Type what it should start with and press Enter. With One task per line on, each line is its own task. The Start's chip says where its work goes: → one free chat or → every chat.

A card can start a flow too: an HTML card's own Send button sends along the card's arrows instead of to Morphy.

ArrowsCopy Anchor Link

Point at the edge of the Start, a chat or a card in the frame and a dot appears in the middle of that side. Drag the dot onto a chat or a card: the arrow lands on the side nearest your pointer. Let go on empty canvas instead and pick New chat or New note to make the next step right there, already joined.

To move an arrow, drag it near one of its ends onto another chat or card, or another side of the same one. Drag an end onto empty canvas to delete the arrow.

Click an arrow to choose how it carries:

• Every answer (the usual one): every answer goes along it.
• One free chat: of the arrows like this leaving one place, the first chat that isn't working gets each item. This is how a team shares a list. It's for arrows into chats; an arrow into a note or a card brings every answer.
• Wait for all: the chat it goes to waits until every arrow like this into it has brought an answer, then gets them together, each under who wrote it. This is how a writer sums up a council. It only puts together answers from the same run: if a chat failed last time, its old answer isn't mixed into the next one.
• Ask me first: each answer waits for you before it goes on. The arrow says Waiting for you and the frame's name row says 1 answer to look at. Click either to read it, then Keep (it goes on), Send back… (type what to change; the chat answers again, and that answer waits for you too) or Drop. Up to 100 answers can wait; past that the oldest is dropped, and the name row says so.

An arrow into a note adds each answer at the end of the note, under who sent it and when. If you're typing in the note when an answer arrives, both stay. An arrow into an HTML card puts it in the card's data, where the card can show it.

Each arrow ends in a small arrowhead on the chat or card it goes to, so you can see which way it goes. It stays dim while nothing goes along it and gets thicker when you point at it. While a chat works on what an arrow brought, two small lights drift along that arrow, and while an answer on it waits for you it turns blue. To delete an arrow, click it and press Delete, or pick Delete arrow. Deleting a chat or card takes its arrows with it, and Ctrl + Z brings both back.

Cards as stepsCopy Anchor Link

When you need to choose, change or fill something in before the flow goes on, Morphy puts a card in the flow for it. What reaches the card waits there for you: the frame's name row says Pick a script needs you (click it to go to the card) and the arrow into the card says Waiting for you. Only what you send from the card goes on.

Morphy has five cards ready and makes its own when none of them fits:

• Pick one: shows the options side by side; you pick one and only that one goes on.
• Review: shows the text so you can edit it, then send it on.
• Shortlist: tick the items you want; only those go on.
• Form: fields Morphy chose for this flow; what you fill in goes on.
• Results: collects everything that arrives in a list you can mark.

Brief, jobs and scheduleCopy Anchor Link

• Brief (⋯ → Brief…): the goal and limits for the whole flow, like "for parents, plain words, under 300 words". Every chat in the flow gets it with everything that reaches it, so you never repeat it. It shows after the flow's name; click it to change it.
• Jobs: each chat Morphy makes for a flow has a job ("Find three facts about what arrives"), shown in its chat before it starts. It goes with every message that reaches the chat.
• Schedule (⋯ → Schedule…, or right-click the Start): every hour, every day or every week at a time you pick, with what it starts with. It runs while Morphy is open; if Morphy was closed when it was due, it runs once when you open Morphy. After a pause it counts from when you resume: a time that passed while it was paused doesn't run straight away.

Watch itCopy Anchor Link

The name row shows what's going on: how many chats are working, what's waiting, Paused, and when a run was stopped. ⏸ pauses the flow (what chats hand on waits until you resume), ■ stops every chat the flow is running and drops what was waiting, answers waiting for you too. ☰ shows what happened, newest first: what started it, which answer went where, what you kept, sent back or dropped.

The bell in the name row tells you when a flow is done, so you can leave it running and do something else. It starts off (struck through); click it to turn it on. When a run comes to rest, because the last answer has landed or because the flow is waiting for you (an answer to look at, a card that needs you, the handoff limit), the bell rings and swings. It keeps ringing until you click or type in the flow: its frame or name row, a chat or card in it, its Morphy, or the bell itself. Stopping a flow with ■ doesn't ring it. It plays the same sound as a chat's bell, which you can change in Personalization.

If two chats keep handing work to each other, the flow stops after 10 handoffs in a row and asks: Continue goes on.

In a flow where answers come back to a chat (a loop), the chat that leads the loop (the one work comes into it through) can end the run when the work is done: it ends its answer with the line [flow done]. That answer still lands on notes and cards, but goes to no other chat, and the run stops there. Morphy tells such a chat how to do this, so you only need to say what counts as done, in its job or the brief.

Move and change itCopy Anchor Link

Drag the frame's name row to move it with everything in it. Morphy, the conductor beside it, stays where it is: drag it on its own to put it anywhere, or select it first (click its title) to move both together. A flow's chats and cards, and its Morphy, stay on the flow's canvas: you can't drag them onto another tab or move them to a project. They stay in the frame, too: drag one a little past the frame's edge and the frame grows to hold it. Drag it well away and it leaves the flow: the name row says so, its arrows still bring it work, and ⋯ → Tidy up puts it back. A chat or card you let go of in the frame becomes part of the flow. Arrange leaves a flow's chats and cards where they are and lines up everything else clear of the flow. You can't drag a flow into a project: it slides back. ⋯ → Tidy up lays the flow out by its arrows, left to right: a column per step, chats that work side by side stacked, the frame fitted around them, and anything that isn't part of the flow moved out of its way. Morphy does this by itself whenever it builds or changes a flow. Drag its sides or corners to resize it (never smaller than what it holds). Double-click its name to rename it. Ctrl + Z undoes moving it, resizing it, a chat or card going in or out, and adding, changing or deleting arrows, and leaves what Morphy changed in the meantime alone.

⋯ → Delete flow… deletes the flow and everything in its frame: its chats, its cards and its conductor. Morphy asks first and says what goes. Ctrl + Z brings it all back. If a chat in it is still working, stop it first.

Ask MorphyCopy Anchor Link

Morphy can build and run flows for you:

Make a council about whether we should rewrite the backend in Go.

Every Monday at 9, have two chats check what changed in our competitors' docs and write me a summary.

Add a chat to the Blog flow that checks the facts before the editor gets it, and make me approve its answer.

Morphy builds the flow chat by chat, puts in a card where you need to choose, tells you what it made, and can start it, pause it, or read and answer what waits for you.

Several accountsCopy Anchor Link

Saved more than one Claude or Codex account in Settings → Account? Ask Morphy to put each chat on its own, and they all work at the same time:

Give each worker its own Codex account.

You can also pick a chat's account yourself: its model button → Account.

Code and GitHubCopy Anchor Link

For code in a git repository, Morphy sets the flow up the way a team works: each chat that writes code gets its own copy of the repository on its own branch, ends its work with a pull request, and a reviewer chat reads the pull request and leaves its review on GitHub. You merge. If you want the flow to merge too, each merge waits for your OK.

Pull requests need GitHub's command-line tool, signed in: install GitHub CLI, then run gh auth login in a terminal (for example the one in the side dock). Without it, the chats push their branches and give you the link to open a pull request yourself.

Build the settings page and the export button in parallel, each as a pull request, and review both.

FreemiumCopy Anchor Link

On Freemium, New flow shows what Pro adds instead. Flows you already have keep running.