kumi

<p align="center"> <img src="docs/assets/kumi-logo.svg" alt="kumi" width="300"> </p> <p align="center"> <a href="https://github.com/user1303836/kumi/actions/workflows/kumi.yml"><img alt="CI" src="https://github.com/user1303836/kumi/actions/workflows/kumi.yml/badge.svg?branch=main"></a> <a href="https://github.com/user1303836/kumi/releases/latest"><img alt="Release" src="https://img.shields.io/github/v/release/user1303836/kumi?label=release"></a> <img alt="Ableton Live 12" src="https://img.shields.io/badge/Ableton%20Live-12-111111"> <img alt="Node 22 | 24" src="https://img.shields.io/badge/node-22%20%7C%2024-339933"> <a href="LICENSE.md"><img alt="License: MIT" src="https://img.shields.io/badge/license-MIT-blue"></a> </p> <p align="center"> English · <a href="README.zh-CN.md">简体中文</a> · <a href="README.ja.md">日本語</a> </p> **A studio producer agent for Ableton Live that learns how you work.** Kumi will literally do anything in your set that Ableton exposes via Extensions/LOM... and even some things it doesn't intentionally expose via the API. From the tedious jobs to the ones you never have time for: rebuilding a sound from a YouTube tutorial, matching your mix to a reference, writing a Max for Live device you describe, or reworking the rack you point at. Every change shows up in HISTORY, most with their own undo, and a whole plan is one undo in Live (Cmd-Z, or Ctrl-Z on Windows). Kumi remembers the techniques you keep, so it fits you better with every session. Support for other DAWs is planned. <p align="center"> <img src="docs/assets/kumi-screenshot.png" alt="Kumi rebuilding a Drift bass from a video tutorial: the conversation with each step it took, FOCUS showing the new track's device chain, and HISTORY with an undo for every change" width="760"> </p> ## What it does - **Changes almost anything in the Set:** tempo, scale and groove; the mixer, routing and sidechains; tracks, scenes and clips; notes and MIDI transforms; devices, racks and their parameters. - **Listens:** loudness, tonal balance, width, tempo and key of a mix, a sample or its own bounce, and how your mix compares with a reference. - **Matches a reference:** builds several takes on a sound, scores each against the reference and refines the best. `/goal` keeps at it until it gets there. - **Watches tutorials** from YouTube or a file, then builds what they show on a new track. - **Plays, records and resamples**, to let you hear what it built or to check its work. - **Takes full control of Live:** deletes what you ask for, writes MIDI straight into the Arrangement, renders offline, runs Python inside Live for what its other tools can't reach, and answers for what you right-click in Live ("Ask Kumi about this"). Big Sets of hundreds of tracks stay quick. - **Makes Max for Live devices** you describe in plain words (MIDI effects, audio effects and instruments) and puts them on your tracks. - **Looks things up:** searches the web and reads pages, PDFs, manuals and code on GitHub, so it can build an effect like one it has read about. - **Shows where you are:** FOCUS follows what you touch in Live, as a device tree, a piano roll or a Session or Arrangement strip. Click a device to point at it: "this Saturator's too harsh". - **Remembers:** notes about you and each Set, techniques it learns from what you keep, and recipes you can replay. Every save is shown, and one click forgets it. - **Keeps your conversations** for each Set, and says what changed while it was closed. - **Works with your model:** sign in with ChatGPT, or use an OpenAI, Anthropic or OpenCode API key. ## Get started You need Ableton Live 12 on macOS 13 or later, or on Windows 10 or 11. Live 12.4 or later adds the right-click menu, MIDI written straight into the Arrangement and offline renders. Making Max for Live devices needs Max for Live (Live Suite, or Standard with the add-on). Kumi brings its own Node. **macOS:** open Terminal and paste: ```sh curl -fsSL https://raw.githubusercontent.com/user1303836/kumi/main/install.sh | sh ``` **Windows:** open PowerShell and paste: ```powershell irm https://raw.githubusercontent.com/user1303836/kumi/main/install.ps1 | iex ``` Then, in a new terminal window (on Windows, the same window works): ```sh kumi login # sign in with ChatGPT, or an Anthropic, OpenAI or OpenCode key kumi bridge # with Live closed: connect Kumi to Live (once) kumi # open Kumi next to your Set ``` The first time you open Live afterwards, pick **AbletonMcpBridge** as a Control Surface in Live's **Settings → Link, Tempo & MIDI**. After that, Kumi finds Live by itself. Inside Kumi, type `/` for commands. Esc stops what Kumi is doing, and `/stop` stops Live. While Kumi works, Enter tells it more (it reads it after the step under way), Tab sends a message for after, and `/btw` asks something on the side. Something off? `kumi doctor` checks everything and says what to run. `kumi report` puts what went wrong in one file to send us. `kumi uninstall` removes Kumi. Kumi tells you when there's a newer version as it starts. `/update` inside Kumi, or `kumi update` in a terminal, gets it and brings the bridge along; `kumi update --check` only asks, and `kumi update --rollback` goes back. To stop the check, put `"updateCheck": false` in `~/.kumi/settings.json`. [Guide](docs/en/KUMI_GUIDE.md) · [Commands, keys and screens](docs/en/KUMI_TUI.md) · [How Kumi changes your Set](docs/en/KUMI_CHANGES.md) · [Changelog](CHANGELOG.md) ## Status Kumi 1.7.4 is tested with Ableton Live 12.4 (beta) on macOS. On Windows, installing Kumi and connecting it to Live are tested; the rest is new there, so please send a `kumi report` when something breaks. Support for Renoise and Reaper is next. ## Development From a copy of this repository, with Node.js 22 or 24: ```sh npm run setup # install and build npm run kumi # run it (npm run kumi -- bridge, -- doctor, and so on) npm run typecheck npm test # no Live or sign-in needed ``` | Folder | What's in it | | --- | --- | | `apps/kumi` | The terminal app and the `kumi` command | | `packages/runtime` | Kumi's agent core: model providers, memory, audio analysis, video, the web, and the Live integration | | `apps/mcp-server` | The bridge: a local MCP server Kumi starts, which also works on its own with other MCP clients ([bridge guide](apps/mcp-server/README.md)) | | `remote-script` | The bridge's Remote Script, which runs inside Live | | `apps/live-extension` | Kumi's Live extension (Live 12.4 and later) | | `protocol` | The list of operations the bridge and the Remote Script share | The [developer guide](docs/en/DEVELOPER_GUIDE.md) covers building, testing and releasing. ## License [MIT](LICENSE.md). Ableton Live is a trademark of Ableton AG; Kumi is not affiliated with or endorsed by Ableton.