← Back to the blogOpen source

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.

We use your email only to check you were an Unspaghettit beta tester and to reply to you.

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:

YOU KEEPYOU GAINFeatures and surfacesActions and rulesScenariosMCP server for your agentImpact reportsbefore you buildPost-implementation reportsafter you buildOne portfolioall your projectsA memory beyond the agentsame spec for any LLM
What you keep from Unspaghettit (features, surfaces, actions, rules, scenarios, the MCP server) and what the Community Edition adds: impact reports, post-implementation reports, one portfolio and a memory beyond the agent.
  • 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.

01Exportto a JSON file02Installone command03Connectyour agent over MCP04Recreateand compare countsa few minutes per project, your LLM does most of the work
Moving a project in four steps: export it to a JSON file, install the Community Edition, connect your agent over MCP, then have your LLM recreate the project and compare the counts.

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.json at 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.

unspaghettit-export.jsonLyriks projectFeatures12Features12Surfaces38Surfaces38Actions214Actions214your LLM, over MCPCOUNTS MATCH · DONEIf not, the agent lists what it could not carry overExample counts, yours will differ
After the import, the counts of features, surfaces and actions in the Lyriks project are compared with those saved in the export file. If they match, the project is across; if not, the agent lists what it could not carry over. Example counts.

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.

Keep your software in tune

Start with one module. Lyriks recovers its spec, then verifies every change. All it needs is your repository.