AI tools, scored for your job
Get paid to train AI
🤝 You're in the Free & Open Source library — community-built tools you can use without paying. A different concept from our scored AI directory.
Home › Free & Open Source › Software › Loop Engineering
✦ Free & open sourceSoftware

Loop Engineering

Practical patterns and CLI tools for loop engineering with AI coding agents.

Design the loop for your AI coding agents

Stop prompting and start orchestrating AI agents with patterns, starters, and CLI tools.

Free forever · open source · MIT
✓ Light setup✓ Browser-based✓ Real-time collaboration
7.3
ZEKAI
Stop prompting, design loops
Free & open source · Software
Ease of setup3
Usefulness8
Maintenance9.5
Community8.5
★ 11,313
GITHUB
Sep 2026
UPDATED
MIT
LICENSE
🛠 Don't want to self-host? We can set it up →
⚡ Quick answer

Loop Engineering provides a structured pattern library and CLI tool to orchestrate AI coding agents like Claude Code, Grok, and Codex around your codebase. It suits developers wanting to move past manual prompting into automated daily triage, PR babysitting, and CI sweeps.

Runs on
Cross-platform
Hosting
Desktop
Languages
TypeScript
License
MIT

What it is

The tool uses a TypeScript CLI (@cobusgreyling/loop) to initialize, audit, and estimate costs for agentic loops across patterns like daily-triage, dependency-sweeper, and issue-triage. It guides your transition from report-only week-one setups to cautious assisted execution, helping verify results before persisting state.

Who it's for

It suits software engineers and teams actively integrating AI coding agents into structured repository maintenance. It does not suit developers looking for a simple one-click module rewriter or those unprepared to monitor token costs and review automated output.

Key features

Unified CLI Control

Initialize, audit, and check costs using npx @cobusgreyling/loop commands.

Pre-built Operating Patterns

Deploy predefined workflows like daily triage, PR babysitting, and CI sweepers.

Graduated Safety Levels

Progress safely from week-one L1 reports to L2 assisted and L3 unattended loops.

Multi-Tool Support

Configure loops to work with Claude Code, Grok, Codex, and OpenCode.

How to start

Up and running in 3 steps

1
Run `npx @cobusgreyling/loop init . --pattern daily-triage --tool claude` to set up your first loop.
2
Run `npx @cobusgreyling/loop doctor .` to verify your repository setup.
3
Run `npx @cobusgreyling/loop cost --pattern daily-triage --level L1` to estimate execution token expenses.
Real talk

Our honest verdict

What's great

  • Includes concrete patterns for common repo tasks like dependency sweeping and post-merge cleanup.
  • Provides built-in cost and health auditing via the CLI.
  • Supports multiple AI coding tools including Claude Code and Grok.
  • Enforces a safe progression path from passive reporting to active execution.

Where it falls short

  • Token costs can explode if loops are left running unattended without careful monitoring.
  • Requires active oversight, as unattended loops can make unattended mistakes.
  • Loop Ready logic strictly weights recent runs harder than old files on disk.
Cost

Pricing & license

The software is free under its MIT license, and the only cost is running it yourself and paying for the underlying AI token usage.

Paid work

Open remote AI-training roles

880 open remote AI-training roles, updated November 15, 2026; most pay $20–$175 an hour. Zekai lists them free; the application goes to the employer’s platform.

See all open roles →
Compare

Alternatives

🎁 Free & open-source alternatives

These reviewed AI tools do the same job instantly — from our scored directory.

Get more

Use it, or have us set it up

📄 Free PDF: Loop Engineering for Software
A plain-language guide to getting your first result. Sent to your inbox.
🔔 64 people want a full video tutorial — add your vote
🛠 Don't want to set it up yourself?
We'll install, host & configure Loop Engineering for you — and train your team.
Get it done for you ↗
Questions

FAQ

What tool does it default to if none is specified?

It defaults to Claude if you omit the --tool flag.

Should I use unattended loops right away?

No, week one is strictly report-only, and you should only roll out higher levels after the verifier has been right for a week.

Radar

Latest AI news

✉️ The weekly free toolkit
The best new free & open-source tools for Software — one short email a week, in your language.
Free · 1 email/week · unsubscribe anytime
Get paid to train AI →

See Zekai first in Google