From Unspaghettit to Lyriks Community Edition: Moving Your Projects
A thank-you to the first Unspaghettit users, what the Community Edition adds, and how to move your projects across in four steps with your own LLM.
November 5, 2026 · 2 min read
Thank-you offer
6 months of Lyriks Enterprise, on us.
You tested Unspaghettit when it was rough. As a reward, every beta tester gets the full Enterprise edition free for 6 months.
Unspaghettit was the first public version of Lyriks. You installed it, modeled real projects and told us what broke. Thank you: many choices behind Lyriks come straight from your feedback, and as a reward we’re offering you 6 months of Enterprise.
Here is why to move to the Lyriks Community Edition, and how to bring your projects across. It takes a few minutes per project.
What you gain by moving
The Community Edition is free and open source. It keeps everything you used: features, surfaces, actions, rules, scenarios and an MCP server for your agent. And it adds:
- Impact reports. See what a change touches, and which past decisions it conflicts with, before you build it.
- Post-implementation reports. After the build, a verdict: what was implemented, left out, or added unasked.
- One portfolio. All your projects in one place, shared by the team.
- A memory beyond the agent. Any LLM reads the same validated spec through MCP.
Moving a project in four steps
No converter needed. Your projects are plain JSON and your LLM does the work.
1. Export each project
In each repository, ask your coding agent:
Using the Unspaghettit MCP, export the full model of this project, with every feature in full detail, into
unspaghettit-export.jsonat the root of the repository. Then tell me how many features, surfaces and actions it contains.
Keep the counts. You’ll use them to check the import.
2. Install the Community Edition
One command on Linux, macOS or Windows. Get it on the Start for free page, details in the install guide.
3. Connect your agent
The First steps page gives the MCP command for Claude Code, Codex and other clients. Then remove the Unspaghettit MCP so the two don’t mix.
4. Recreate the project
Read
unspaghettit-export.json. Using the Lyriks MCP, create a project with the same name, then recreate every feature with its surfaces, states, actions, rules, effects, scenarios, personas and events. Keep the original names and descriptions. Then compare the counts with the export and list anything you could not carry over.
If the counts match, you’re done. If not, the agent’s list shows what to fix. Then try an impact report on your next change.
Need help?
Ten minutes with us beats being stuck halfway.
- Email: contact@lyriks.io, or our contact page.
- GitHub: open an issue on lyriks-io/lyriks-community.
- Discord: join our server.