Graph Compose

Graph Compose is where AI-built workflows grow up. Every workflow is plain JSON (the format every LLM has been trained on), so any AI can write one without a plugin or custom prompt. Edit it in Cursor, generate it from Claude, commit it like any other file. Prompt an AI, drag nodes in a visual builder, or write TypeScript; they're all editors for the same JSON. Runs on Temporal-grade execution: agents keep state across crashes, batch jobs resume from the exact item that failed, forEach runs each item as an isolated child workflow. Human-in-the-loop approval is a node, not a rebuild. Why JSON-Native Matters This is the structural thing that makes the vibe-coding story real, not just aspirational. Graph Compose workflows aren't code that imports an AI-friendly DSL. They're plain JSON, the format every LLM has been trained on since GPT-3. That unlocks a few things competitors can't match: - Any AI can author a workflow. Claude, GPT, Gemini, your IDE assistant. All of them produce valid workflow JSON without a plugin, custom prompt, or finetune. The "AI builder" isn't a feature bolted on; the format itself is AI-native. - Workflows are first-class files. Diffable, reviewable in any PR, version-controlled like any other artifact. No proprietary binary format, no database-only representation. - The three build modes converge on the same artifact. Visual builder, TypeScript SDK, and in-product AI assistant aren't competing abstractions. They're editors for the same JSON. Prototype in one, refine in another, no conversion step. - Agents can author and run workflows at runtime. Because a workflow is just JSON, an agent can generate a sub-workflow, hand it to the runtime, and execute it. Meta-orchestration falls out for free. - Zero lock-in on the build side. If a team wants to generate workflows from their own tooling (a spec, a form, another agent), they emit JSON. No SDK dependency required to produce workflows. Competitors force a choice: either a visual-only format (Zapier, n8n) that AI can't really author, or a code-only SDK (Temporal, Inngest) that requires running real language runtimes to generate or inspect. Graph Compose sidesteps both. JSON is the universal interface.