Replaces FL Studio's built-in Gopher AI panel with your own LLM. You talk in natural language, it drives the DAW.
FL Studio 2026 exposes a built-in MCP server. Gopher is just a web panel that calls it. FLAIK takes over Gopher's panel slot via Chrome DevTools Protocol and reuses the same control channel — wired to your LLM instead of Gopher's cloud.
Reversible: close FL, relaunch normally, Gopher comes back.
Gopher is a WebView2 (Chromium) panel in FL Studio 2026 (toolbar button 999,
Alt+F1) that loads https://gopher-fls.image-line.com/.
FL Studio 2026 exposes itself as a built-in MCP server. Gopher doesn't have
special access — it controls FL through a host object (script_handler) that FL
injects into the panel, sending JSON-RPC tools/call requests. We reverse-
engineered the full protocol from Gopher's own mcp_bridge.js (see
FL_BRIDGE_PROTOCOL.md).
This means FLAIK can reuse FL's own control API: take over the slot, inherit
script_handler, and call the same MCP tools Gopher uses — wired to the
user's chosen AI instead of Gopher's cloud.
44 tools across 7 areas:
- Transport — play, stop, get/set tempo
- Channels — add, remove, rename, select, mute/solo, volume, pan, color, route to mixer, step sequencer patterns, open piano roll, quantize
- Mixer — volume, pan, rename, color, mute/solo, reset, add/remove effects, get/set routing
- Piano Roll — run and save Python scripts (arbitrary note manipulation via
flpianorollmodule) - Playlist — get names, rename, color tracks
- Plugins — list, get, and set plugin parameters
- System — session context, browser names, show/hide windows, highlight UI elements
Plus: persistent memory (FL Studio manual docs, notes, learned patterns), inline image display from the manual.
Download FLaiK-Setup.exe from Releases, run it, follow the wizard.
- Always launch FL via
flaik.exe(desktop shortcut or Start Menu). FLAIK can only replace Gopher in the panel when FL Studio is started throughflaik.exe— it sets the debug port that allows the takeover. Launching FL normally means Gopher stays as Gopher. - The injection is not instant. After FL starts, it can take a moment for FLAIK to take over the Gopher panel.
- If Gopher still shows its normal page, click another FL tab and then go back to Gopher — this forces the panel to refresh and FLAIK should appear. Give it a few seconds and try the tab switch once more if needed.
| Layer | Tech |
|---|---|
| Agent brain | Python (OpenAI-compatible API) |
| Panel UI | JavaScript (Shadow DOM, injected into WebView2) |
| FL control | FL Studio's built-in MCP server (JSON-RPC via script_handler) |
| Panel takeover | Chrome DevTools Protocol (port 9222) |
| Launcher | Go (flaik.exe) |
| Installer UI | Wails v2 (Go + WebView2) |
| Installer engine | Inno Setup (silent, embedded) |
| Memory | Markdown files (FL Studio manual + notes) |
- FL Studio MCP server — built-in
script_handlerhost object (protocol reverse-engineered from Gopher's ownmcp_bridge.js) - Chrome DevTools Protocol — navigates Gopher's WebView2 panel to FLAIK
- FL Studio HTML documentation — 445 official manual pages bundled as the knowledge base
- OpenAI-compatible API — any provider (Z.ai, OpenAI, DeepSeek, Ollama, LM Studio, etc.)
- Installer "Launch FLaiK now" sometimes doesn't open the install folder on completion. If this happens, navigate to the install directory manually and double-click
flaik.exe. - Proof of concept. This is minimally tested. It does seem to perform better than Gopher already, but better agent prompting and scripting is still needed.
- Not yet tested on other systems. Installer and launcher behaviour could still be broken on some machines.
Verified (non-destructive, done now):
- Gopher's URL + auth mechanism — read from its own history DB.
- Full control protocol — decoded from Image-Line's
mcp_bridge.js. - FLAIK bridge + panel — built, syntax-checked, serves 200.
- All override tooling — built, fails gracefully without live FL.
Blocked on one human action (live verification):
- The live override itself needs FL's Gopher slot reachable via CDP, which
requires restarting FL with
flaik.exe. This cannot be done autonomously — force-closing the running FL risks unsaved work, and the Gopher button is a GUI click.
Once FL is relaunched via flaik.exe + Gopher opened, everything else runs
automatically and we learn: (a) does the debug port open? (b) does the
injected FLAIK page inherit script_handler? (c) the full live MCP tool
catalog (= the complete controllable surface).
Heads-up for users: the swap to FLAIK is not instant — after FL starts, you may need to click away to another FL tab and back to Gopher to force the panel to refresh before FLAIK shows up. This is normal.
FLAIK takes over Gopher's web panel locally via CDP. It doesn't modify FL Studio. Gray area with Image-Line's ToS — use at your own discretion.