Skip to content

⚡ SIMPLETI AI LABS · AUTONOMOUS AGENT ORCHESTRATION

Simplicio Loop

simplicio-loop turns GitHub issues into tested PRs: it maps the repo, an AI plans, a deterministic editor applies, tests verify, squads review.

50 Extension points
3 tiers Haiku → Sonnet → Opus / Fable
24/7 Watcher for opted-in repos, paid subscription
Evidence Green runs pass a secret scan, then open a PR with evidence.

What it does

From GitHub issue to a PR with evidence

The mapper reads the repo, the planner only plans, the deterministic editor applies the change, and the tests decide whether it ships.

01

GitHub issue

The work starts as an issue in your repository.

02

simplicio-mapper

Maps files, symbols and tests, and hands a map slice to the planner.

03

Planner in a sandbox

claude / codex / grok / gemini. It plans as a JSON plan and never writes.

04

simplicio-dev-cli

Deterministic apply of the JSON plan. No free-form edits.

05

Tests verify

simplicio-loop turbo --apply - --verify runs the suite. Two failures escalate the model role.

06

Secret scan → PR

Green runs pass a secret scan and open a PR with evidence.

Animated flow in 8 steps: issues, intake, general coordinator, squads, workers (mapper, plan, dev-cli), squad review, merge train, main and the Simplicio Live kanban
Issues, intake, general coordinator, squads, workers, squad review, merge train, main.

Install

Install in four commands

Needs Python 3.11+, git, and an authenticated gh for GitHub issues.

# 1-command installer (macOS & Linux): installs the Runtime
$ curl -fsSL https://raw.githubusercontent.com/simpletibr/simplicio/master/install.sh | sh

# Windows (PowerShell as Administrator):
> irm https://raw.githubusercontent.com/simpletibr/simplicio/master/install.ps1 | iex

# simplicio-loop on every OS, via pip:
$ pip install simplicio-loop

# sign in, only needed for the 24/7 watcher:
$ simplicio-loop login

# verify health and operators:
$ simplicio-loop doctor

Use it

One command, from your editor

In Claude Code or VS Code, write the goal. The loop does the rest.

> /simplicio-loop finish all the open issues
STEP 1

You write the goal

Write /simplicio-loop and the goal.

STEP 2

The loop works

Mapper maps, planner plans, dev-cli applies, tests verify.

STEP 3

PR with evidence

You get a pull request with the evidence attached.

24/7 watcher

A worker that watches your repos

A service that watches the repos of the GitHub owners listed in SIMPLICIO_247_OWNERS that opt in, opens PRs, and needs an active subscription. Auto-merge is off by default.

# one simulated tick, changes nothing
$ simplicio-loop watch247 --once --dry-run
# are the exec CLIs logged in?
$ simplicio-loop watch247 login-check
# from a repo checkout, as root, after creating the non-root user simplicio-loop:
$ sudo cp packaging/systemd/simplicio-loop-247.service /etc/systemd/system/
# edit it, then chmod 600
$ sudo cp packaging/systemd/simplicio-loop-247.env.example /etc/simplicio-loop-247.env
$ sudo systemctl enable --now simplicio-loop-247
REPO OPTS IN

.simplicio-loop/loop.toml

enabled = true in the repository.

ISSUE OPTS IN

Label loop:auto

The issue was opened by an owner, member or collaborator.

WORKER LOOP

PR opened

The worker loop runs and opens the pull request.

MERGE

Squad or human merges

Auto-merge stays off unless you turn it on.

Details: docs/WATCHER_247.md ↗

How it works

Model escalation, merge train and squads

Tier 1 does the mechanical work. Stronger models step in only after failures, and they replan rather than execute.

Model escalation

Tier 1

Haiku

Mechanical work, one module.

Tier 2

Sonnet

After 2 failures. Integration and security work.

Tier 3

Opus / Fable

After 2 more failures. Replan only, never executes.

Merge train

TEST THE BATCH

PR A ✓ · PR B ✓ · PR C ✓ · PR D ✓

The batch is tested once together.

GREEN

Merge all into main

When the batch passes, every PR lands.

RED

Bisect

The bad PR (C) goes back to its squad. A, B and D still merge.

Squads

GENERAL COORDINATOR

Opus / Fable

Plans, never executes.

SQUADS

Sonnet coordinator per squad

Each squad coordinates up to 4 Haiku workers.

MERGE COORDINATOR

Sonnet merges in series

Only squad-approved work reaches main.

1 coordinator and 29 workers versus squads: before and after
One coordinator and 29 workers, versus squads: before and after.

Extension points

The 50 extension points

Status of the extension points in the 24/7 path, out of 50.

Wired
19
Partial
29
Absent
2

docs/EXTENSION_POINTS_SERVICE.md ↗ · issue #1509 ↗

Learn more

Docs and references

Everything else lives in the repository.