Welcome to FL Studio Pilot Discussions

Welcome to FL Studio Pilo / fls-pilot Discussions 👋

Welcome to the discussion space for fls-pilot.

fls-pilot is a rollback-first FL Studio production assistant for MCP-compatible LLM clients. It is maintained as an extended fork of rosasynthesiz/flstudio-mcp, with a stronger focus on safe FL Studio workflows, documented API boundaries, local-first project assistance, and production-oriented tooling.

This space is for questions, ideas, roadmap feedback, release notes, and practical workflow discussions around using LLMs safely with FL Studio.

What belongs here? 💬

Use Discussions for:

• questions about installation, setup, and usage;
• workflow ideas for FL Studio production, mixing, routing, MIDI, and project organization;
• feedback on roadmap items and planned capabilities;
• safe automation ideas that should be considered for future versions;
• release and migration discussions;
• examples of how you use fls-pilot in real projects.

For confirmed bugs, regressions, missing documentation, or actionable implementation tasks, please use Issues instead.

Safety-first project direction 🛡️

fls-pilot does not try to hide FL Studio API limits.

When FL Studio exposes a reliable scripting API, the project may provide safe helpers, validation, snapshots, rollback support, and LLM-facing tools.

When FL Studio does not expose a capability, the project should document that boundary and provide a checklist, report, bridge workflow, or manual fallback instead of pretending that unsafe automation is supported.

This is especially important for areas such as playlist clip editing, automatic plugin loading, deep Audio Clip internals, rendering, and UI-only operations.

Release status 🚀

The current stable milestone is v2.0.0-stable, the first extended stable release after the fork and the last broader stable line before the breaking v3.x rename path.

The upcoming v3.x line is expected to standardize the new fls-pilot naming, commands, imports, controller names, and environment-variable conventions.

If you are evaluating the project, start with the latest release notes and the documentation before relying on old fork-era names.

Community guidelines 🤝

Please keep discussions practical, respectful, and grounded in verified FL Studio behavior.

Good reports usually include:

• your operating system;
• FL Studio version;
• Python version;
• fls-pilot version or commit;
• the MCP client you are using;
• what you expected to happen;
• what actually happened;
• logs or screenshots where useful.

Thanks for helping make fls-pilot safer, more useful, and more honest about what can and cannot be automated in FL Studio.