Skip to content
Loophole

Quickstart

This is the one happy path: build Loophole from source, install the extension in Live, point Claude Code at it, and confirm a read-only tool returns your real track names. It is not the full tool reference (that is here); it is the shortest line to a working setup.

Prerequisites

Section titled “Prerequisites”
  • Ableton Live 12.4.5b Suite (the beta build that ships the Extensions SDK), with Dev Mode enabled in Settings.
  • The Extensions SDK and CLI tarballs, downloaded from your own Ableton Beta Program (Centercode) access. They are not redistributable, so Loophole does not ship them.
  • Node 24.14.1 or newer and pnpm 10.

Build and install

Section titled “Build and install”

  1. Clone the monorepo and install its workspace dependencies.

    Terminal window
    git clone https://github.com/OthmanAdi/loophole.git
    cd loophole
    pnpm install

  2. Add your local SDK and CLI tarballs to the extension package. This edits package.json and pnpm-lock.yaml locally; do not commit those edits (the published tree stays SDK-free).

    Terminal window
    pnpm add file:/abs/path/to/ableton-extensions-sdk-1.0.0-beta.0.tgz --filter @othmanadi/loophole-extension
    pnpm add -D file:/abs/path/to/ableton-extensions-cli-1.0.0-beta.0.tgz --filter @othmanadi/loophole-extension

  3. Build the production .ablx.

    Terminal window
    pnpm --filter @othmanadi/loophole-extension run package:live

  4. Install the .ablx in Live: Settings, then Extensions, then add the built file. Restart Live.

  5. On first start the extension writes a bridge.json (the port and a bearer token) into its storage directory. You will read those two values into your client config next.

Point Claude Code at it

Section titled “Point Claude Code at it”

Loophole speaks Streamable HTTP, so the client connects over a local URL with a bearer token, not a spawned command. With Live running:

Terminal window
claude mcp add --transport http loophole http://127.0.0.1:<port>/mcp
# then attach the header: Authorization: Bearer <token-from-bridge.json>
claude mcp list   # loophole should appear

Use the exact <port> and <token> from bridge.json. The Claude Code install page has the per-client detail, and the skill can write this config for you with /setup.

Verify it worked

Section titled “Verify it worked”

This is the step that tells you the whole chain is live.

  1. Confirm Live 12.4.5b Suite is running with the Loophole extension installed and active.

  2. Confirm loophole appears in your client’s tool list (claude mcp list, or the client’s MCP panel).

  3. Ask the assistant to call one read-only tool, live_get_song_overview or live_find_track, and check the result against your project.

    Run live_get_song_overview and tell me my track names.

    If it comes back with your real track names, tempo, and counts, the bridge is wired correctly. If it does not, see Troubleshooting.

From here, the recipes show the common edits, and the tool reference is the exhaustive surface.