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

Where to place human approval gates in your agent loops

Automating a loop is easy; knowing where a human should still sign off is the hard part. Here is a practical method. Step 1: classify every action by reversibility. Read-only calls, drafts, and local file edits are low-risk; sending emails, publishing content, paying invoices, or deleting records are high-risk. Gate only the high-risk class — approving everything trains reviewers to rubber-stamp. Step 2: place the gate at a boundary, not inside reasoning. The best position is right before an external side effect, after the agent has prepared everything. Reviewers then see a finished proposal with all context attached, instead of judging an intermediate thought. Step 3: make the pending state useful. Configure the approval timeout so the loop takes a fallback branch — for example, queue the item for the next business day — instead of blocking a whole batch on one decision. Step 4: use editable approvals. Let reviewers fix a field and approve in one click; every correction becomes a signal you can later turn into an automation rule. Step 5: audit everything. Keep the reviewer's identity and comment in the trace so you can answer who approved what, and retire any gate that never rejects anything. Default recipe: gate irreversible external actions, review approvals weekly, and remove gates with a 100% approval rate. Full guide available at https://getloopcraft.com — sapsap@qq.com.