Skip to content

Releases: thunderdew-dawn/fls-pilot

Release list

v3.0.0-beta.2

v3.0.0-beta.2 Pre-release
Pre-release

Choose a tag to compare

View all tags
@thunderdew-dawn thunderdew-dawn released this 15 Jun 23:44
v3.0.0-beta.2
d0e9cd5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

fls-pilot v3.0.0-beta.2

This beta release is the next milestone in the fls-pilot v3 release train.

v3.0.0-beta.2 introduces the new Control Center, improves guided setup and read-only project review workflows, and continues to harden release readiness, documentation, safety wording, and GitHub project hygiene.

This is still a beta release. It does not mark the full v3.0 release effort as complete.

Highlights

  • Added the new Control Center as the recommended first-run and daily runtime surface.
  • Added guided setup and local readiness checks to make onboarding easier.
  • Added read-only project review panels for faster insight into FL Studio project state.
  • Improved the assistant-facing workflow model around Mix Review, Project Preflight, and Project Organizer proposal-mode flows.
  • Improved README restructured docs/ for better user faced information and user-guidance.
  • Continued release-train cleanup across CI, documentation, labels, project automation, and dependency maintenance.
  • Consolidated mcp server surface to user/dev environments scopes.
  • MCP Server now supports prompts and also context resources, and knowledge-base access for more LLM support (scope).

User-facing changes

The new Control Center makes - while still beta status - fls-pilot easier to start and understand.
It provides a local overview for setup checks, runtime status, ports, MCP snippets, and project-review information.

The Control Center is useful both with and without an AI agent. Without an agent, it exposes read-only access to useful fls-pilot review tools. With an agent, it helps visualize information, discuss findings, plan changes, and safely execute approved workflows.

Plugin and EQ automation guidance is clearer about a hard safety rule: unknown normalized parameter mappings must be verified instead of guessed, interpolated, or silently applied.

Safety and reliability

  • Reinforced the rule that normalized plugin/EQ parameter values must not be mapped without verified calibration data.
  • Kept persistent FL Studio writes approval-gated.
  • Added or refined CI permissions, project automation, docs builds, and release evidence.
  • Maintained the proposal-first workflow model for actions that can affect FL Studio projects.

Developer / maintenance notes

  • Version 3.0.0b2 is a breaking release.
  • do not expect anything! we refactored many smal and big things to prepare fls pilot for higher flights. :-)
  • Dev Docs are now separated from agent-docs for LLM scope Efficiency.
  • MCP prompts, context resources, and knowledge-base access were added.
  • dev tools are no longer published by default via mcp server.

Known limitations

  • This is still a beta release.
  • Full v3.0 release readiness is not complete yet.
  • Some Control Center review tools are still beta and intentionally read-only.
  • Risk scoring may still be incomplete or imprecise in some review panels.
  • fls-pilot must not infer unknown plugin parameter mappings without verified calibration data.

Upgrade notes

No migration step is expected for users of the previous beta.

For source installs, update to the v3.0.0-beta.2 release/tag and verify that the package version reports 3.0.0b2.

What's Changed

Breaking Changes

Safety and Release Gates

  • v3.0.0-beta.2 — New Control Center, Guided Setup, and Read-only Project Review Panels by @thunderdew-dawn in #114

Other Changes

Full Changelog: v3.0.0-beta.1...v3.0.0-beta.2

What's Changed

Breaking Changes

  • refactor: consolidate tool retirement logic into a dedicated module a… by @thunderdew-dawn in #112

Safety And Release Gates

  • v3.0.0-beta.2 — New Control Center, Guided Setup, and Read-only Project Review Panels by @thunderdew-dawn in #114

Other Changes

Full Changelog: v3.0.0-beta.1...v3.0.0-beta.2

Contributors

thunderdew-dawn
Loading
0 Join discussion

v3.0.0-alpha.1

v3.0.0-alpha.1 Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 11 Jun 20:20
v3.0.0-alpha.1
b4adee6
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What's Changed

Breaking Changes

Safety And Release Gates

Fixes

Documentation And GitHub

Other Changes

Full Changelog: v2.0.0-stable...v3.0.0-alpha.1

Contributors

thunderdew-dawn
Loading

v2.0.1-stable

v2.0.1-stable Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 10 Jun 16:31
v2.0.1-stable
6fcd9da

v2.0.1-stable — naming transition and documentation alignment

v2.0.1 is a small stabilization and communication release for the v2 stable line.

There are no breaking changes in this release.

Naming transition

This project is moving toward the fls-pilot / FL Studio Pilot identity. During the v2.x stable line, the existing package names, commands, controller identifiers, and setup conventions intentionally remain compatible with the earlier flstudio-mcp naming.

That means v2.x may still contain names such as:

  • flstudio-mcp
  • fl-studio-mcp
  • FLStudioMCP

This is intentional for compatibility and does not indicate a separate product line.

What changes in v2.0.1

  • Clarifies the naming transition in the README and project documentation.
  • Marks the current v2.x line as the stable compatibility line before the planned v3 rename.
  • Keeps existing installation and runtime behavior stable.
  • Prepares the public migration path toward the v3.x breaking rename.

What does not change

  • No package rename.
  • No CLI rename.
  • No MIDI port rename.
  • No FL Studio controller rename.
  • No breaking workflow changes.

Planned v3 direction

The v3.x line is planned as the breaking rename line where project naming can be consolidated around fls-pilot / FL Studio Pilot.

Users who are already on v2.0.0-stable do not need to change their setup unless they want the clarified documentation.

Assets 5
Loading

v2.0.0-stable

v2.0.0-stable

Choose a tag to compare

View all tags
@github-actions github-actions released this 07 Jun 16:29
v2.0.0-stable
b04cf18

v2.0.0-stable — first extended stable release after the fork

v2.0.0-stable is the first materially extended stable release of this maintained fork after the initial fork line.

This release marks the project’s transition from a focused FL Studio MCP prototype into a broader rollback-first FL Studio production assistant for MCP-compatible LLM clients. It stabilizes the expanded direction of the fork before the upcoming breaking rename and package/API cleanup in the v3.x line.

What this release represents

This is the last extended stable release before the breaking v3.x rename path.

The goal of v2.0.0-stable is not to pretend that FL Studio exposes more automation than it actually does. Instead, this release formalizes a safety-first contract:

  • supported write operations should be scoped, reversible, and backed by snapshots where possible;
  • API-exposed actions should be preferred over UI automation claims;
  • unavailable FL Studio API features should be documented as boundaries, not simulated or overstated;
  • LLM-facing workflows should use conservative defaults, readback where available, and explicit human approval for risky mutations.

Highlights

  • Expanded MCP workflow coverage for real FL Studio production tasks.
  • Rollback-first safety model for supported project mutations.
  • Clearer API-boundary documentation for unavailable FL Studio actions.
  • Stronger positioning as a production assistant, not only a MIDI/note sender.
  • Knowledgebase-backed value handling for safer parameter conversion and reduced LLM guesswork.
  • More explicit roadmap separation between stable, API-dependent, and rejected/not-planned capabilities.
  • GitHub-based release, roadmap, and governance tracking prepared for the breaking v3.x line.

Stable user-facing areas

This release establishes the stable direction for:

  • mix review and live peak-watch workflows;
  • project cleanup, naming, color, and organization assistance where FL Studio exposes metadata;
  • routing review and safe bus-layout proposals;
  • composition and scale workflows through the supported bridge approach;
  • plugin and preset assistance within FL Studio API limits;
  • audio analysis via local file analysis;
  • MIDI export and preflight/export-readiness reporting;
  • snapshot/changelog/rollback handling for supported writes.

Important limitations

This release intentionally keeps FL Studio API limits visible.

The project does not claim support for actions that FL Studio does not expose through its scripting API, including automatic plugin loading, arbitrary playlist clip editing, deep Audio Clip internals such as Stretch/Normalize/source-path control, or automatic audio rendering to WAV.

Where those actions are not exposed, the project should provide suggestion, checklist, report, bridge, or manual workflow support instead of unsafe automation claims.

Fork and attribution note

This repository remains a maintained fork of rosasynthesiz/flstudio-mcp.

The upstream project provided the foundation for this work. v2.0.0-stable documents the point where this fork has grown into its own release path, safety model, roadmap, and product direction.

Migration note

The next major line, v3.x, is expected to be breaking.

Users who need the last extended stable release before the breaking rename should use v2.0.0-stable.

Users following active development should expect the v3.x line to standardize the new fls-pilot naming, commands, imports, controller names, and environment-variable conventions without retaining old compatibility aliases.

Discussion

For context, migration notes, and follow-up discussion, see:

https://github.com/thunderdew-dawn/fls-pilot/discussions/77

Loading