Field notes
Architecture decisions, cost numbers, what worked and what didn't — from the people building Maestro. Released alongside the changelog when a release earns more than a one-line summary.
-
Building the Composer canvas: React Flow, dagre, and the bug that ate two evenings
The Composer is the editor that turns Maestro from a configure-and-run product into a build-your-own product. Here's the architecture decisions that made it work — and the silent edge-rendering regression that almost shipped.
-
Why we promoted LLM nodes to first-class Agents
When the same prompt lives in three places, you've got an abstraction problem. Here's how we lifted LLM-node configs out of score graphs and into a workspace-level catalog — and why the schema change was easier than the naming.
-
Decomposing the cold-leads agent: a 9× cost reduction
Cold-leads used to run on a 130-line instructions blob and burn 110K tokens per run. Replacing the blob with a graph cut cost to $0.04 — and the drafts got better. Here's why.