Is LoopCraft free to use?

Yes. LoopCraft offers a free tier for designing and exporting AI agent loop patterns. A Pro plan is available for advanced features.

What is Loop Engineering?

Loop Engineering is designing the control flow for AI agents: how they plan actions, observe results, and iterate. LoopCraft includes 11 pre-built patterns based on research from Anthropic, OpenAI, and others — including ReAct, Plan-Execute, Evaluator-Optimizer, Multi-Agent, and more. Design loops visually and export to LangGraph, OpenAI Agents SDK, AutoGen, or CrewAI.

Which frameworks can I export to?

LoopCraft exports to LangGraph (Python), OpenAI Agents SDK (TypeScript), AutoGen (Python), and CrewAI (Python). Each export produces working code you can run directly in your project.

Do I need to write code?

No. LoopCraft is a visual builder — you design loop patterns with a drag-and-drop interface and configure nodes without writing code. Code export to LangGraph, OpenAI SDK, AutoGen, and CrewAI is generated automatically and is optional.

What loop patterns are supported?

LoopCraft supports 11 agent loop patterns: ReAct (think-act-observe cycle), Prompt Chaining (sequential steps with quality gates), Routing (classify and direct inputs), Parallel Sectioning (independent subtasks in parallel), Parallel Voting (multiple runs for confidence), Orchestrator-Workers (dynamic task decomposition), Evaluator-Optimizer (generate-evaluate loop), Plan-and-Execute (plan then execute with replanning), ReWOO (variable passing between tasks), LLM Compiler (DAG-based parallel execution, 3.6x speedup), and Multi-Agent (collaborative agents with roles).

LoopCraft Adds Visual Failure Paths to Agent Workflows

LoopCraft now treats failure paths as first-class workflow elements. You can mark a node as optional, attach a fallback branch when a tool call fails schema validation or hits a timeout, and review the resulting graph before exporting to LangGraph, OpenAI Agents SDK, AutoGen, or CrewAI. The goal is simple: catch loops that only work on the happy path while they are still diagrams, not after they burn a retry budget in production. The canvas shows retry budgets and timeout attachments next to each node so the on-call story stays short. This ships today as a visual-editor update; export targets are unchanged.