Product
Shipping the workflow builder
Branching, transfers, and mid-call actions without writing code. What we cut to keep it usable, and why deterministic steps sit alongside the model.
The first version of the builder let you express almost anything, which meant nobody could get anything working. The rewrite started from the handful of shapes real call flows actually take.
Deterministic where it matters
Some steps should never be left to a model's judgment: verifying a caller's identity, confirming a payment amount, deciding whether a transfer is allowed. Those run as deterministic checks the agent has to pass through.
The model handles the conversation around them. The gates stay fixed.
What we cut
Arbitrary nesting, custom scripting in the canvas, and per-node model overrides all went. Each one made the builder more expressive and considerably less likely to produce a working agent.
