Skip to content

LoopKing

Open loops. Team-ready tools.

LoopKing is open-source and local-first: readable loop files, dry-runs, verifier gates, and inspectable artifacts, driven by the `loop` CLI. `loopk.ing` is the home for LoopKing Cloud, the hosted team layer for shared loops, skills, MCP tool profiles, approvals, and run history.

Start with the docs Read the syntax GitHub repo

Open corelocal loop CLI and portable loop specs

Tool syncskills, MCP profiles, verifier commands

Team layerregistry first, run history next

The loop CLI is the open core

LoopKing is the mono-tool for launching coding-agent work precisely without turning every task into a custom script. The framework stays open-source: teams keep execution local, inspect every prompt, and route by semantic decisions or shell verifier exits. It runs the readable LoopSpec format (.loop.md files compiled to typed YAML).

Workflow launcher

  • Write readable .loop.md files close to markdown.
  • Compile to typed YAML specs when you need exact reproducibility.
  • Route by Decision: PASS / Decision: FAIL or shell exit code.
  • Keep run state, rendered prompts, command logs, and final reports.

Safe by default

Dry-run renders the workflow without calling agents or running commands. Execute mode is explicit, bounded by iteration limits, and designed around inspectable artifacts.

LoopKing Cloud is the hosted team layer

LoopKing Cloud starts registry-first: make the team's favorite agent tools portable before asking anyone to trust hosted execution.

Shared loop and skill registry

  • Private libraries for blessed .loop.md workflows (loop registry push/pull/list).
  • Team-authored skills, prompt packs, review personas, and verifier recipes.
  • Versioning, ownership, checksums, and run history.

Easy MCP and tool deployment

loop tools sync installs or updates MCP config, skill bundles, allowed command policies, and verifier commands from loopking.yaml so every developer starts from the same known-good agent setup.

MVP: registry first, execution local

LoopKing Cloud MVP

The first hosted surface is a private team registry for loops, tool profiles, and run metadata, served by a Cloudflare Worker at api.loopk.ing and reached with $LOOPKING_TOKEN. Local execution remains the default; loop runs push uploads privacy-preserving run metadata (no source) once teams already trust the registry.

This keeps the product boundary clean: open framework below, hosted coordination above. Teams pay to standardize agent behavior without giving up local control.