Flows

Flow class declares two @start methods. Operator calls flow.kickoff() expecting one to run.

Multiple @start methods are valid — all fire as parallel entry points. If you want one entry, declare a single @start (or parameterize selection). Verify the actual entry set by inspecting the Flow class. Document which entries exist so kickoff behavior is predictable.

Flow declares class MyFlow(Flow[MyState]) with MyState as a Pydantic model. Operator mutates self.state.users.append(...) inside a listener.

Typed Flow state is a Pydantic model; mutations through self.state are valid for declared fields. Adding undeclared fields fails Pydantic validation. Use model_validate / model_copy for atomic updates if you need crash-safe mutation ordering. Document state-shape changes alongside the flow class.

Flow ingests a webhook payload into self.state.message, then a downstream @listen feeds self.state.message into a Crew's Task description.

Untrusted state values that flow into agent prompts must be sanitized or delimited (e.g., wrap in <user_content>...</user_content> tags with explicit instructions to treat as data). Treat the flow state as an injection surface — the agent will follow whatever is in the prompt.