Migrate Lemon Squeezy Desktop App Licensing with Codex

Use a local coding assistant to audit your desktop app’s activation, validation, and device storage before changing its licensing API.

Run a read-only migration check

Open your app repository in Codex or Claude Code, then paste the prompt. Review the plan and decide if you want your assistant to implement it in staging.

Request a 20-minute rehearsal with one existing key

Review this app’s Lemon Squeezy licensing for a possible move to LicenseFerry. Start with a read-only check using the repository and these public guides.

https://licenseferry.com/docs/lemon-squeezy-migration
https://licenseferry.com/docs/api

Find how the app activates, validates and deactivates keys, identifies devices, and grants access. Point me to the relevant files. If the app uses a different licensing system, report what you found and stop.

Give me a short plan covering three things.
1. Which key types may carry over and what a local inventory still needs to confirm.
2. What happens to existing installs and to customers who replace a device at their seat limit.
3. How to test one existing key in staging before switching, including an app update and a replacement device where applicable.

Use only read-only inspection for this report. Real keys, credentials and customer data are unnecessary for this step. Stop after the plan and wait for my approval before changing files, installing dependencies or calling any licensing API. After approval, implement the agreed changes in staging. Ask separately before importing real records, resetting devices or switching live traffic.

Get the LicenseFerry skill

Download the skill and extract its licenseferry folder into ~/.codex/skills/ for Codex or .claude/skills/ in your project for Claude Code. You can also attach the extracted SKILL.md directly to a session.

Review the result before shipping

Check that secrets stay in platform-provided secure storage. In Electron, keep license keys in the main process and expose narrowly scoped operations to the renderer. Include tests for an interrupted request and the same device making a repeated activation request.