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).

When to Extract a Sub-Loop vs. Inline It: A Decision Framework

As agent loops grow, the temptation to extract every repeated pattern into a sub-loop is strong. But over-extraction creates indirection that makes debugging harder, not easier. Here is a decision framework for when to extract and when to keep inline. Extract when: (1) the sub-task has its own error-handling strategy that differs from the parent; (2) you need to reuse it across multiple parent loops; (3) the sub-task has a clear input/output contract that can be tested independently. Keep inline when: (1) the sub-task only appears once and has no distinct failure mode; (2) extracting it would force you to pass most of the parent context as parameters; (3) the sub-task logic is tightly coupled to the parent's branching decisions. The test is simple: if extracting the sub-loop makes the parent easier to read without making the sub-loop harder to understand in isolation, extract it. If both get harder to follow, keep it inline. LoopCraft's visual editor lets you toggle between inline and extracted views without changing the underlying structure, so you can prototype both layouts before committing. Export to LangGraph, AutoGen, CrewAI, or the OpenAI Agents SDK either way. Feedback: sapsap@qq.com. LoopCraft: https://getloopcraft.com