kneo-studio

Turn an n8n workflow export into a governed Kneo agent spec — and be told, in detail, what could not be carried across.

This is the distributed package: a FastAPI backend-for-frontend that serves a React SPA from inside the wheel. pip install kneo-studio gives you the whole application, with no container and no database service to run — SQLite is created for you.

$ pip install kneo-studio
$ kneo-studio

It binds loopback and, by default, needs no login: your own machine is the default deployment. The same artifact runs for a team on a shared host under a login mode, and refuses to bind a routable address without one — an unauthenticated shared instance would make every request the local owner, with full rights over the project tree.

What it is for

Studio's contract is that it tells you what it could not convert. An n8n workflow uses constructs Kneo has no form for — output parsers, memory, retrieval, inline secrets, branch predicates — and the failure mode worth designing against is not a crash but a spec that looks complete and quietly does something else. Every such construct becomes a gap card the developer has to see, and the blocking ones refuse export until they are dealt with.

That is why an import can succeed and still refuse to hand you a file.

Documentation

• Quickstart
• What imports, and what does not — three example workflows and the exact gaps each produces, measured rather than estimated
• Changelog
• Repository

Studio talks to a kneo-serv platform through kneo-client; it holds no platform logic of its own.

Licence

See LICENSE.