Medley is no longer maintained

What this means

There is no service shutdown, no deadline and no required data export. Medley runs on your own machine, and we are not disabling existing installations remotely.

What stops is maintenance. Medley will not receive bug fixes, compatibility updates or support, so it will drift out of step with Claude Code and Codex as those tools change. Future compatibility is not guaranteed, which is why we recommend removing it rather than leaving it installed indefinitely.

Medley was free, so there is nothing to cancel and no refund involved.

Removing Medley

Removing the plugin is enough. Neither host has an uninstall hook, so the background service notices it has been orphaned — within about a minute, and never mid-mission — and tears itself down: its LaunchAgent, its launcher, and every downloaded engine binary.

Your mission history, provider config and any BYOK keys stay on your machine. Nothing is deleted from it and nothing is sent anywhere. If you never ran a mission, that directory is removed too and nothing is left behind.

If you installed Medley in both hosts, remove it from both.

If you have not updated in a while

That self-cleanup is complete on Medley 0.10.0 and later. Versions 0.6.0 to 0.9.0 stop the background service but leave the downloaded engine binaries on disk, and versions before 0.6.0 do not stop it at all.

Updating before you uninstall is the simplest way to have Medley clean up after itself.

Already removed an older version? The manual cleanup steps are in the Medley repository. Spine-AI/medley

Questions

If something is not working as described here, get in touch and we will help while we can. [email protected]