About io.github.dreamrec/livepilot
io.github.dreamrec/livepilot is an MCP server in the Content category: aI copilot for Ableton Live 12 — 91 MCP tools for music production and mixing.
Install
claude mcp add io-github-dreamrec-livepilot -- npx -y livepilotnpx -y livepilotThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about io.github.dreamrec/livepilot
Powered by Claude · Grounded in docs
Security checks
- ✓README presentThe repository ships documentation.
5 checks have not been run yet.
README
██╗ ██╗██╗ ██╗███████╗██████╗ ██╗██╗ ██████╗ ████████╗
██║ ██║██║ ██║██╔════╝██╔══██╗██║██║ ██╔═══██╗╚══██╔══╝
██║ ██║██║ ██║█████╗ ██████╔╝██║██║ ██║ ██║ ██║
██║ ██║╚██╗ ██╔╝██╔══╝ ██╔═══╝ ██║██║ ██║ ██║ ██║
███████╗██║ ╚████╔╝ ███████╗██║ ██║███████╗╚██████╔╝ ██║
╚══════╝╚═╝ ╚═══╝ ╚══════╝╚═╝ ╚═╝╚══════╝ ╚═════╝ ╚═╝
[!NOTE] LivePilot works with any MCP client — Claude Code, Claude Desktop, Cursor, VS Code, Windsurf. All tools execute on Ableton's main thread through the official Live Object Model API. Everything is reversible with undo.
What LivePilot Does
Most MCP servers are tool collections — they execute commands. LivePilot is an agentic production system. It has seven layers that work together:
| Layer | What it provides |
|---|---|
| Deterministic Tools | Direct control: transport, tracks, clips, notes, devices, scenes, mixing, arrangement, browser, automation |
| Device Atlas | Knowledge of every device in Ableton's library — 1305 devices indexed by name, URI, category, tag, genre, and pack (641 pack-indexed). 120 enriched with sonic intelligence (47 with aesthetic-tagged signature_techniques). 683 drum kits mapped. Free-text atlas_describe_chain ("a granular pad like Tim Hecker") and reverse-lookup atlas_techniques_for_device (what techniques reference this device?) added in v1.17 |
| Concept Surface | New in v1.17. Two reference files let the LLM's training translate into LivePilot: artist-vocabularies.md maps ~25 producers (Villalobos, Hawtin, Basic Channel, Gas, Basinski, Hecker, Aphex, Autechre, Dilla, Burial, Henke, Daft Punk, …) to reach_for / avoid / key_techniques; genre-vocabularies.md maps 15 genres to tempo / kick / bass / percussion / harmonic / texture / devices. 146 cross-references between devices and techniques. The LLM reads "sound like Gas" and gets a concrete device chain, not guesswork |
| Sample Engine | Three-source sample intelligence — Ableton's browser, your filesystem, and Splice's catalog (plan-aware: Ableton Live plan uses daily quota, Sounds+/Creator uses credits, free samples bypass both). 6 fitness critics. 29 processing techniques. Collections, presets, preview-URL audition, LIVE Describe-a-Sound + Variations via Splice GraphQL (v1.17) |
| Spectral Perception | Real-time ears via M4L — 9-band FFT (v1.17+, sub_low split at 20-60 Hz), RMS/peak metering, Krumhansl-Schmuckler key detection, pitch tracking, FluCoMa mel/chroma/onset. Closes the feedback loop so the AI hears its own changes |
| Technique Memory | Persistent library of production decisions. Save a beat pattern, device chain, or mix template. Recall by mood, genre, or texture across sessions |
| Creative Intelligence | A dozen engines that understand song identity, learn your taste, diagnose stuck sessions, generate creative options, and evaluate results before claiming success |
Architecture
┌──────────────────────────────────────────────────────────────────────┐
│ │
│ KNOWLEDGE PERCEPTION MEMORY │
│ ────────────── ────────────── ────────────── │
│ │
│ Device Atlas 9-band FFT recall by mood, │
│ 1305 devices RMS / peak genre, texture │
│ 120 enriched pitch tracking 29 techniques │
│ 683 drum kits key detection replay into session │
│ │
│ Sample Engine Corpus Intelligence Taste Graph │
│ Splice (local SQLite) EmotionalRecipe move preferences │
│ Browser search GenreChain device affinities │
│ Filesystem scan PhysicalModelRecipe novelty tolerance │
│ 6 fitness critics AutomationGesture │
│ │
│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
│ │ Device │ │ M4L │ │ Technique │ │
│ │ Atlas │──│ Analyzer │──│ Memory │ │
│ └──────┬───────┘ └──────┬───────┘ └──────┬───────┘ │
│ │ │ │ │
│ ┌──────┴───────┐ ┌──────┴───────┐ ┌──────┴───────┐ │
│ │ Sample │ │ Corpus │ │ Composer │ │
│ │ Engine │ │ Intelligence│ │ Engine │ │
│ └──────┬───────┘ └──────┬───────┘ └──────┬───────┘ │
│ └─────────────────┼──────────────────┘ │
│ ▼ │
│ ┌─────────────────┐ │
│ │ 426 MCP Tools │ │
│ │ 52 domains │ │
│ └────────┬────────┘ │
│ │ │
│ Remote Script ──┤── TCP 9878 │
│ M4L Bridge ─────┤── UDP 9880 / OSC 9881 │
│ Splice (local) ─┤── SQLite (downloaded samples) │
│ │ │
│ ┌────────────────┐ │
│ │ Ableton Live │ │
│ │ 12 │ │
│ └────────────────┘ │
└──────────────────────────────────────────────────────────────────────┘
How the pieces connect
Remote Script (remote_script/LivePilot/) — A Python ControlSurface that runs inside Ableton's process. Listens on TCP 9878. All Live Object Model calls execute on Ableton's main thread via schedule_message. Detects Ableton version at startup and enables three capability tiers: Core (12.0+), Enhanced Arrangement (12.1.10+), Full Intelligence (12.3+).
MCP Server (mcp_server/) — Python FastMCP server. Validates inputs, routes commands to the Remote Script over TCP, manages the M4L bridge, runs the atlas, sample engine, composer, and all intelligence engines. This is what your AI client connects to.
M4L Bridge (m4l_device/) — Optional Max for Live Audio Effect on the master track. Provides deep LOM access through Max's LiveAPI that the ControlSurface API can't reach. UDP 9880 (M4L to server) carries spectral data and LiveAPI responses. OSC 9881 (server to M4L) sends commands. The 32 spectral/analyzer tools strictly require the bridge; device and sample tools that call the bridge also have graceful fallbacks, so core functionality works without it. Backed by 30 bridge commands for hidden parameters, Simpler internals, warp markers, display values, and Simpler warp / Compressor sidechain writes that live on child objects Python can't reach.
Device Atlas (mcp_server/atlas/) — In-memory indexed JSON database. 1305 devices with browser URIs, 120 enriched with YAML sonic intelligence profiles (mood, genre, texture, recommended chains). 6 indexes: by_id, by_name, by_uri, by_category, by_tag, by_genre. The AI never hallucinates a device name or preset — it always resolves against the atlas first.
Sample Engine (mcp_server/sample_engine/) — Searches three sources simultaneously: BrowserSource (Ableton's library), SpliceSource (local Splice catalog via SQLite), FilesystemSource (user directories). Every result passes through a 6-critic fitness battery (key, tempo, spectral, genre, mood, technical). 29 processing techniques (Surgeon precision vs. Alchemist experimentation). Builds complete sample processing plans with warp, slice, and effect recommendations.
Splice Client (mcp_server/splice_client/) — Searches Splice's catalog through two layers: the local SQLite database (sounds.db, already-downloaded samples) and the live gRPC API (full catalog, including samples you haven't downloaded yet). The gRPC client auto-detects Splice's dynamic port via port.conf, handles self-signed TLS, and enforces a 5-credit safety floor before any download. Per-call timeouts (5–10s) prevent a hung Splice process from stalling the MCP event loop. Graceful fallback to SQL-only if grpcio isn't installed. No API key needed — authentication comes from the running Splice desktop app.
Composer (mcp_server/composer/) — Prompt-to-plan pipeline. Parses natural language ("dark minimal techno 128bpm with industrial textures") into a CompositionIntent (genre, mood, tempo, key). Plans layers using role templates (kick, bass, percussion, texture, lead, pad, fx). Compiles to a step-by-step plan of tool calls that the agent executes. Does not execute autonomously — returns the plan. 4 genre defaults (house, techno, trap, ambient) — genres outside this set fall back to a neutral layer plan.
Corpus (mcp_server/corpus/) — Parsed device-knowledge markdown converted to queryable Python structures: EmotionalRecipe, GenreChain, PhysicalModelRecipe, AutomationGesture. Feeds Wonder Mode, Sound Design critics, and the Composer with deep creative knowledge at runtime — not just LLM prompts, actual structured data.
Execution Router (mcp_server/runtime/execution_router.py) — Classifies each step in a multi-step plan as remote_command (TCP to Ableton), bridge_command (OSC to M4L), or mcp_tool (internal), then dispatches it through the correct channel.
The Intelligence Layer
12 engines sit on top of the 426 tools. They give the AI musical judgment, not just musical execution.
SongBrain — What the Song Is
Builds a real-time model of the session: identity core (what defines this track), sacred elements (what must not be casually damaged), section purposes (what each part is doing emotionally), energy arc (where the song is heading). Detects identity drift when edits pull the track away from what made it work.
Taste Graph — What You Like
Learns your production preferences across sessions. Tracks which move families you keep vs. undo, which devices you gravitate toward, how experimental you want suggestions (novelty band), and which dimensions you avoid. Every accept/reject updates the graph. Two producers using the same tools get different recommendations.
Semantic Moves — Musical Actions, Not Parameters
26+ high-level intents ("add contrast," "tighten the low end," "build tension") that compile into tool sequences. Each move carries a risk level, target dimensions, and protection thresholds. The AI knows what it's risking with every action.
Wonder Mode — Stuck-Rescue Workflow
When a session is stuck — repeated undos, overpolished loops, no structural progress — Wonder Mode activates:
- Diagnose — classify the stuckness (loop trap? missing contrast? identity unclear?)
- Generate — find semantic moves that address the diagnosis, enforcing real distinctness
- Preview — apply each variant, capture, undo. Hear before committing
- Commit or Reject — choice recorded into taste and session continuity
Creative Engines
| Engine | What it does |
|---|---|
| Mix Engine | Critic-driven analysis: masking, headroom, stereo, dynamics. Plans corrective moves with before/after evaluation |
| Sound Design Engine | Analyzes patches for static timbre, missing modulation, weak transients. Suggests parameter moves |
| Transition Engine | Classifies transition types (drop, build, breakdown). Scores quality, plans improvements from archetypes |
| Composition Engine | Section analysis, motif detection, emotional arcs. Plans structural moves |
| Performance Engine | Safety-constrained suggestions for live sets. Knows which moves risk audio dropouts |
| Reference Engine | Distills principles from reference tracks. Maps them to your session as concrete moves |
Hook Hunter
Identifies the most salient musical idea — ranks candidates by recurrence across scenes, motif salience, and section placement (payoff-section boost). Tracks whether hooks are developed, neglected, or undermined, and flags when a transition fails to deliver expected payoff. Rhythm-side ranking is currently heuristic (drum-track detection + clip reuse); true onset-based rhythmic features are on the roadmap.
Session Continuity
Maintains creative threads ("the chorus needs more lift") and turn resolutions across the session. When you return to a project: "Last time, you kept the filter sweep for the bridge. The chorus lift thread is still open."
Evaluation Loop
Every engine follows: measure before → act → measure after → compare. If a change made things worse (more masking, lost headroom, identity drift), the system flags it before you move on.
Tools
426 tools across 52 domains. Highlights below — full catalog here.
Core (210 tools)
| Domain | # | What it covers |
|---|---|---|
| Transport | 12 | playback, tempo, time sig, loop, metronome, undo/redo, cue points, diagnostics |
| Tracks | 17 | create MIDI/audio/return, delete, duplicate, arm, mute, solo, color, freeze, flatten |
| Clips | 11 | create, delete, duplicate, fire, stop, loop, launch mode, warp mode, quantize |
| Notes | 8 | add/get/remove/modify MIDI notes, transpose, duplicate, per-note probability |
| Devices | 19 | load by name or URI, insert native (12.3+), get/set parameters, batch edit, racks, chains, drum chain note assignment, presets, plugin deep control |
| Scenes | 12 | create, delete, duplicate, fire, name, color, tempo, scene matrix |
| Browser | 4 | search library, browse tree, load items, filter by category |
| Mixing | 11 | volume, pan, sends, routing, meters, return tracks, master, full mix snapshot |
| Arrangement | 21 | timeline clips, native arrangement clips (12.1.10+), arrangement notes, automation, recording, cue points |
| Automation | 8 | 16 curve types, 15 recipes (filter sweep, sidechain pump, dub throw...), spectral suggestions |
| Theory | 7 | Krumhansl-Schmuckler key detection, Roman numeral analysis, species counterpoint, SATB harmonization |
| Harmony | 4 | neo-Riemannian PRL transforms, Tonnetz navigation, voice leading paths, chromatic mediants |
| Generative | 5 | Euclidean rhythm (Bjorklund), tintinnabuli (Arvo Part), phase shift (Steve Reich), additive process (Philip Glass) |
| Memory | 8 | save, recall, replay, manage production techniques by mood/genre/texture |
| MIDI I/O | 4 | export/import .mid, offline analysis, piano roll extraction |
| Perception | 4 | offline loudness (integrated LUFS, LRA), spectral analysis, reference comparison |
M4L Bridge — 30 tools [optional]
The M4L Analyzer sits on the master track. UDP 9880 carries spectral data to the server. OSC 9881 sends commands back.
[!TIP] Most tools work without the analyzer — it adds 32 spectral/analyzer tools (frequency, loudness, perception) and closes the feedback loop.
SPECTRAL ─────── 9-band frequency decomposition (sub_low → air)
sub_low (20-60 Hz) split off so kick fundamentals don't hide inside sub
true RMS / peak metering
Krumhansl-Schmuckler key detection
DEEP LOM ─────── hidden parameters beyond ControlSurface API
automation state per parameter
recursive device tree (6 levels into nested racks)
human-readable display values as shown in Live's UI
SIMPLER ──────── replace / load samples
get slice points, crop, reverse
warp to N beats, get audio file paths
WARP ─────────── get / add / move / remove markers
tempo manipulation at the sample level
Device Atlas — 6 tools
The atlas is an in-memory indexed database of Ableton's entire device library.
1305 devices total
120 enriched with sonic intelligence (mood, genre, texture, chains)
683 drum kits mapped with note assignments
6 indexes: by_id, by_name, by_uri, by_category, by_tag, by_genre
atlas_search Search devices by name, category, or tag
atlas_suggest Suggest devices for a musical intent (e.g., "warm pad")
atlas_chain Build a device chain from a genre or purpose
atlas_compare Compare two devices side-by-side
atlas_detail Get full enriched profile for a device
atlas_library_scan Scan what's actually installed on this machine
Sample Engine — 6 tools
Three-source sample intelligence with critic-driven fitness scoring.
SOURCES ─────────── BrowserSource (Ableton's built-in library)
SpliceSource (local Splice catalog via SQLite)
FilesystemSource (user-specified directories)
CRITICS ─────────── key fitness · tempo fitness · spectral match
genre alignment · mood alignment · technical quality
TECHNIQUES ─────── 29 processing recipes:
Surgeon (precise, transparent) vs.
Alchemist (experimental, transformative)
analyze_sample Build a complete SampleProfile (material, key, BPM, spectral)
search_samples Multi-source search with critic scoring
suggest_sample_move Recommend processing technique for a sample
build_sample_plan Full processing pipeline: warp + slice + effects
list_sample_techniques Browse the 29-technique library
get_sample_technique Get detailed recipe for a specific technique
Splice Integration
LivePilot reads Splice's local SQLite database to search your downloaded samples with full metadata. No API key needed — it reads the database file directly.
What it does:
- Searches your downloaded Splice samples with key, BPM, genre, and tag metadata
- Integrates as a third source alongside Ableton's browser and filesystem scanning
- Works without a Splice subscription — any previously downloaded samples are searchable
How it works: The Sample Engine's SpliceSource reads ~/Library/Application Support/com.splice.Splice/users/default/*/sounds.db — Splice's local SQLite catalog of downloaded samples. Read-only, no network calls.
Requirements: Splice desktop app running (the MCP server talks to it over gRPC at a dynamic port advertised via port.conf, with self-signed TLS). For fully offline search, previously-downloaded samples are always searchable via the local SQLite fallback even if the Splice app isn't running.
Composer — 3 tools
Prompt-to-plan auto-composition engine.
"dark minimal techno 128bpm with industrial textures and ghostly vocals"
│
▼
┌─────────────────┐
│ Prompt Parser │ → CompositionIntent (genre, mood, tempo, key)
└────────┬────────┘
▼
┌─────────────────┐
│ Layer Planner │ → role templates (kick, bass, perc, texture, lead, pad, fx)
└────────┬────────┘
▼
┌─────────────────┐
│ Plan Compiler │ → executable tool sequences
└────────┬────────┘
▼
┌─────────────────┐
│ Execution Router │ → dispatches: create tracks, search samples, load devices,
│ │ program notes, set volumes, build arrangement
└─────────────────┘
- 4 genre defaults: house, techno, trap, ambient (unknown genres fall back to a neutral plan)
- Returns step-by-step plans — the agent executes each tool call in sequence
compose— plan a multi-layer composition from text promptaugment_with_samples— plan sample-based layers for existing sessionget_composition_plan— dry-run preview (see the plan without credit checks)
Device Forge — 3 tools
Generate M4L audio effect devices from gen~ templates and install them into Ableton's browser.
forge_device Generate a device from a gen~ template
forge_list_templates Browse available gen~ templates
forge_install Install generated device to browser
Agentic Intelligence — 79 tools
The V2 intelligence layer. These tools analyze, diagnose, plan, evaluate, and learn.
| Domain | # | What it does |
|---|---|---|
| Agent OS | 8 | session kernel, action ledger, capability state, routing, turn budget |
| Composition | 9 | section analysis, motif detection, emotional arc, form planning |
| Evaluation | 1 | before/after evaluation with structured scoring |
| Mix Engine | 6 | critic-driven mix analysis, masking, headroom, stereo, dynamics |
| Sound Design | 4 | patch analysis, modulation planning, timbre scoring |
| Transition Engine | 5 | transition classification, scoring, archetype-based planning |
| Reference Engine | 5 | reference profiling, principle distillation, gap analysis |
| Translation Engine | 3 | cross-domain translation, issue detection |
| Performance Engine | 3 | safety-constrained suggestions, safe moves, scene handoff |
| Song Brain | 3 | identity inference, sacred elements, drift monitoring |
| Hook Hunter | 9 | hook detection, salience scoring, neglect detection, phrase impact |
| Stuckness Detector | 3 | momentum analysis, rescue classification, rescue workflows |
| Wonder Mode | 3 | diagnosis-driven variants, taste-aware ranking |
| Session Continuity | 7 | creative threads, turn resolution, session story |
| Creative Constraints | 5 | constraint activation, reference-inspired variants |
| Preview Studio | 5 | variant creation, preview rendering, comparison, commit |
Install
Easiest: Claude Desktop Extension (1 click)
Download livepilot.mcpb and double-click it.
Claude Desktop installs everything automatically. Then:
- Open Ableton Live 12
- Preferences → Link, Tempo & MIDI → Control Surface → LivePilot
- Start chatting
[!TIP] The Desktop Extension auto-installs the Remote Script and M4L Analyzer on first launch.
Quick: One Command Setup
npx livepilot --setup
Runs the full setup wizard: checks Python, installs the Remote Script, creates the Python environment, copies the M4L Analyzer, and tests the Ableton connection.
Manual: Step by Step
npx livepilot --install
Restart Ableton → Preferences → Link, Tempo & MIDI → Control Surface → LivePilot
Claude Code:
claude mcp add LivePilot -- npx livepilot
claude plugin add github:dreamrec/LivePilot/plugin
Codex App:
npx livepilot --install-codex-plugin
Claude Desktop (macOS) — ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"LivePilot": { "command": "npx", "args": ["livepilot"] }
}
}
Claude Desktop (Windows):
npm install -g livepilot
livepilot --install
%APPDATA%\Claude\claude_desktop_config.json:
{
"mcpServers": {
"LivePilot": { "command": "livepilot" }
}
}
Cursor — .cursor/mcp.json:
{
"mcpServers": {
"LivePilot": { "command": "npx", "args": ["livepilot"] }
}
}
VS Code — .vscode/mcp.json:
{
"servers": {
"LivePilot": { "command": "npx", "args": ["livepilot"] }
}
}
Drag LivePilot_Analyzer.amxd onto the master track for real-time spectral analysis.
The --setup wizard and Desktop Extension do this automatically.
Important: The Analyzer must be the LAST device on the master track — after all effects (EQ, Compressor, Utility) so it reads the final output signal.
If you have Splice installed with downloaded samples, the Sample Engine can search them with full metadata (key, BPM, genre, tags) via the local SQLite database.
No API key, no configuration — the Sample Engine reads Splice's sounds.db file directly.
Without Splice, the Sample Engine still searches Ableton's browser and your filesystem.
Verify
npx livepilot --status
Plugin
Codex App
npx livepilot --install-codex-plugin
Claude Code
claude plugin add github:dreamrec/LivePilot/plugin
| Command | What |
|---|---|
/session |
Full session overview with diagnostics |
/beat |
Guided beat creation |
/arrange |
Guided arrangement and song structure |
/mix |
Mixing assistant |
/sounddesign |
Sound design workflow |
/perform |
Live performance mode with safety constraints |
/evaluate |
Before/after evaluation of recent changes |
/memory |
Technique library management |
Producer Agent — an orchestrated multi-step assistant for building, layering and refining sessions. Consults memory for style context, searches the atlas for instruments, searches samples, creates tracks, programs MIDI, chains effects, reads the spectrum to verify, and arranges sections. The agent proposes plans; the user confirms and listens. LivePilot is a high- trust operator, not an autonomous producer.
Core Skill — operational discipline connecting all layers. Consult atlas before loading. Read analyzer after mixing. Check memory before creative decisions. Verify every mutation.
CLI
npx livepilot # Start MCP server (stdio)
npx livepilot --setup # Full setup wizard
npx livepilot --install # Install Remote Script
npx livepilot --uninstall # Remove Remote Script
npx livepilot --install-codex-plugin # Install bundled Codex plugin
npx livepilot --uninstall-codex-plugin # Remove bundled Codex plugin
npx livepilot --status # Check Ableton connection
npx livepilot --doctor # Full diagnostic check
npx livepilot --version # Show version
Compatibility
| Requirement | Minimum |
|---|---|
| Ableton Live | 12 (any edition). Suite required for Max for Live bridge and stock instruments |
| Python | 3.9+ |
| Node.js | 18+ |
| OS | macOS / Windows |
| Splice | Desktop app with downloaded samples (optional — enables SQLite metadata search) |
Version tiers:
- Core (12.0+): All session tools, mixing, devices, MIDI, theory, generative, memory
- Enhanced Arrangement (12.1.10+): Native arrangement clips, arrangement automation
- Full Intelligence (12.3+):
insert_device_native, complete device insertion pipeline
Development
git clone https://github.com/dreamrec/LivePilot.git
cd LivePilot
python3 -m venv .venv && .venv/bin/pip install -r requirements.txt
# Test runner is not in requirements.txt (runtime-only deps) — install it explicitly:
.venv/bin/pip install pytest pytest-asyncio
.venv/bin/pytest tests/ -v
See CONTRIBUTING.md for architecture details, code guidelines, and how to add tools.
Documentation
| Document | What's inside |
|---|---|
| Manual | Complete reference: architecture, all 426 tools, workflows |
| Intelligence Layer | How the 12 engines connect — conductor, moves, preview, evaluation |
| Device Atlas | 1305 devices indexed — search, suggest, chain building |
| Samples & Slicing | 3-source search, fitness critics, slice workflows |
| Automation | 16 curve types, 15 recipes, spectral suggestions |
| Composition | Composer, section analysis, arrangement planning |
| Getting Started | Zero to sound in five minutes |
| Workflows | Beats, session setup, sound design, arrangement, mixing |
| MIDI Guide | Drum patterns, scales, chords, humanization |
| Sound Design | Instruments, effects, parameter recipes |
| Mixing | Gain staging, EQ, compression, sends, stereo width |
| M4L Bridge | Technical reference for the Max for Live analyzer |
| Troubleshooting | Connection issues, common errors, diagnostics |
Community
- Discussions — questions, ideas, show & tell
- Bug reports
- Feature requests
- Contributing guide
- Security policy
Support
LivePilot is source-available under the Business Source License 1.1. If it saves you time in your sessions:
Sponsors get early access to new features, premium skills, curated technique libraries, and direct support.
README copy captured when this server was indexed; it may lag the repository. The original is authoritative.