Skip to main content
FileChannel writes the conversation to a .md or .txt file, one ## @agent_name section per message. Open the file at any point to see what every agent said. Edit it between runs and the next run continues from your edit. Reference: FileChannel.

Two agents, one file

The file holds the task once, then each answer:
The Writer never receives the Researcher’s answer as an argument. It reads it from the file as a prior turn.

A SequentialWorkflow in a file

Give the channel to the workflow. It posts the task as User, then each agent’s answer in order.

Resume and steer from the file

Every run reads the file first, so a later run, even in a new process, continues from what the file holds. Run the workflow above, then open runs/sequential.md and add a section of your own at the end:
Then run a follow-up against the same file:
The Reviser sees the original task, every earlier answer and your note, and its answer is appended under ## @Reviser. You can also delete a weak answer, correct a figure, or remove whole sections before the next run. What is in the file is what the agents see.

AgentRearrange with a parallel step

The file records User, then Planner, then Coder, then the Reviewer’s and Tester’s answers from the parallel step.

Start over

Tips

  • Use one file per conversation. Two unrelated runs on the same file see each other’s messages.
  • Keep ## @ at the start of a line for headers only. A message body that contains such a line is split into two messages when read back.
  • Check the file into git to keep a reviewable history of what your agents said.

Next steps