Architecture Overview
Clioloop's Agentic Fusion is not just "run the same prompt 5 times and pick the best." It's a structured pipeline where different models play different roles, with strict security boundaries between them.
The Pipeline
Step 1: Planning Phase
When you run /fusion, up to 5 planner models are dispatched in parallel. Each planner:
- Receives your original prompt and context
- Has read-only tool access — they can search the web, read files, but never modify anything
- Proposes an approach (not an answer — an approach)
The planners might suggest different strategies:
- Planner A: "Search the web for similar problems, then write a script"
- Planner B: "Read the existing codebase first, then modify in place"
- Planner C: "Break it into subtasks and use the Kanban system"
Step 2: Execution Phase
Your main model takes the planners' proposals and does the actual work:
- Full tool access (file editing, shell, web, browser, image gen, etc.)
- Fully visible — you watch every file edit, every command, every web search in real time
- Not a black box — you can intervene at any time
This is the key difference from "ensemble" approaches: the main model does real work with real tools, not just text generation.
Step 3: Review Phase
Up to 5 reviewer models critique the draft:
- Read-only access — they can see what the main model produced, including generated images
- They check for errors, suggest improvements, flag problems
- Each reviewer works independently
Step 4: Verdict Loop
The draft is revised based on reviewer feedback:
- If reviewers find issues, the main model gets the feedback and revises
- The loop continues until reviewers approve
- You get the final, reviewed answer
Step 5: Fusion
Everything combines into one answer that has already passed independent review.
Security Model
The safety comes from schema-level restrictions:
| Role | Can Read | Can Write | Can Execute |
|---|---|---|---|
| Planners | ✅ Files, web, images | ❌ Nothing | ❌ Nothing |
| Main Model | ✅ Everything | ✅ Files | ✅ Commands |
| Reviewers | ✅ Draft, files, images | ❌ Nothing | ❌ Nothing |
Planners and reviewers are read-only by construction. They can research and critique, but they can never touch your files or run commands. Only your main model has tool access, and you watch it work live.
Why This Works
The quality comes from synthesis, not brute force. Cheap open models combine into something that rivals a frontier model:
- Planners bring diverse perspectives (different models see different approaches)
- The main model does focused execution with full tools
- Reviewers catch errors the main model missed
- The verdict loop ensures quality convergence
You get frontier-level quality at a fraction of the cost, because you're paying for cheap models to plan and review, and only one model does the expensive tool work.
Try It
curl -fsSL https://raw.githubusercontent.com/Clioloop/Clioloop-agent/main/scripts/install.sh | bash
clio setup
clio
Then run /fusion on any task.
Feedback welcome!