| FMRS | 46 / 100 · D | 79 / 100 · B |
| Reliability | 8 / 20 | 12 / 20 |
|---|
| Security and permissions | 8 / 20 | 16 / 20 |
|---|
| Maintenance | 9 / 20 | 18 / 20 |
|---|
| Documentation | 12 / 20 | 18 / 20 |
|---|
| Setup experience | 9 / 20 | 15 / 20 |
| Best for | - Ableton Live 12 users who want an AI assistant for music production.
- Producers needing intelligent device recommendations, sample analysis, and composition assistance.
- Musicians who prefer controlling their DAW with natural language or artist/genre shorthand.
- Advanced users who want the system to learn their personal plugin library.
- Studios wanting AI-assisted mixing, sound design, and composition with deep integration.
| - Developers auditing NPM dependencies within AI workflows
- Teams performing supply chain security assessments
- Users of Claude Desktop, Cursor, or VS Code
|
| Not for | - Beginners unfamiliar with Ableton Live 12 (requires operating the DAW).
- Users needing fully autonomous AI composition (LivePilot returns plans, not autonomous execution).
- Users who only need simple MIDI control without complex tooling.
- Those expecting a free commercial plugin (it uses BSL-1.1 license).
- Users on other DAWs (Logic, FL Studio) — it only supports Ableton Live 12.
| - Projects outside the NPM ecosystem (e.g., pure Python/Go)
- Environments without network access to deps.dev, OSV.dev, and the npm registry
- Scenarios requiring maintenance by an official upstream vendor
|
| Required permissions | - Communicates with Ableton Live 12 over TCP 9878 (requires Remote Script installation).
- Communicates with the Max for Live analyzer over UDP 9880 and OSC 9881 (optional, for spectral tools).
- Reads local Splice database files and communicates with the Splice desktop app over gRPC (optional).
- Scans the filesystem for plugins and samples (requires user directory access).
- Writes state files to `~/.livepilot/`, including atlas overlays, memory, and logs.
- Makes changes to the Live session (tempo, tracks, devices) — all through the undo stack.
| - Network access to the NPM registry and external services (deps.dev, OSV.dev, OpenSSF, npms.io, GitHub)
- Read access to workspace lockfiles (pnpm-lock.yaml, package-lock., yarn.lock) for cache invalidation
|
| Risks and side effects | - Modifies the Live session in real time, which may inadvertently change your project; backup recommended.
- Splice interactions can consume credits on downloads; there's a safety floor of 5 credits, but still a risk.
- The M4L analyzer listens on LAN (OSC 9881); unauthenticated commands are dropped since v1.28.0, but use trusted networks.
- Filesystem scans can be time-consuming and expose plugin paths/names (privacy).
- With many tools, mis-calling may lead to complex state changes; experimental in production sessions.
- Actively developed; APIs may change frequently. Pin a version for stable work.
| - Third-party READMEs and changelogs are untrusted external content; they are wrapped in tags with _meta flags but should still be handled cautiously
- Depends on availability and accuracy of external services
- Batch requests are capped at 25 packages to prevent registry enumeration; larger sets require batching
- Third-party open source project, not officially maintained by NPM or Anthropic
|
| Supported clients | Claude Desktop, Claude Code, Cursor, VS Code | Claude Desktop, VS Code, Cursor |
| Tools | 10 | 19 |