Installation
the-loop is installable directly from GitHub via each harness's marketplace construct — no bespoke marketplace publishing. One repo, one set of skills/commands/templates, two plugin manifests (.claude-plugin/ and .cursor-plugin/).
From a terminal (Claude Code)
If you have the CLI, one command installs the plugin without opening a session — at user scope, or for one project only:
pip install the-loopy-one # once
the-loop install # the CLI + the Claude Code plugin
the-loop install claude --scope project --project-dir . # this repository only
the-loop upgrade # later, when a release landsIt drives Claude Code's own plugin installer, prints every command before running it (--dry-run to preview), and reports what it skipped and why. See install · upgrade.
Cursor is not covered by that command yet (issue #157) — use the Cursor routes below. The in-session routes work exactly as before for both harnesses, and are the shortest path if you do not want the CLI.
Claude Code
/plugin marketplace add MadaraUchiha-314/the-loop
/plugin install the-loop@the-loopCursor
Cursor (≥ 2.5) resolves the plugin from this repo's .cursor-plugin/ manifests. Install it either way:
From the marketplace — in the slash menu run
/add-plugin, or open Settings → Plugins → Add, and point it at the repository URL:texthttps://github.com/MadaraUchiha-314/the-loopLocally (for development) — check the repo out under Cursor's local plugins dir:
bashgit clone https://github.com/MadaraUchiha-314/the-loop \ ~/.cursor/plugins/local/the-loop
Skills follow the Agent Skills open standard, so the same SKILL.md powers both harnesses; commands appear in Cursor's slash menu (by filename, e.g. /init); the Claude Code SessionStart hook is replaced by the always-applied rule rules/the-loop.mdc.
CLI companion (optional)
Besides the plugin, the-loop ships a lightweight, extensible Python CLI for quality-of-life commands the plugin uses (webhook routing, polling, observability). See installing the CLI for install instructions, and the-loop CLI for what it does and why you might want it.
Next
Run /the-loop:init in your target repo, then follow the quickstart.