The canvas for agentic coding.
Claude Code, Codex or Cursor writes your app, and Lindi puts every screen of it on one canvas. See the big picture, decide what changes, and push it to your code.
- Claude Code
- Codex
- Cursor
A design canvas
that holds your code.
Your app, as code
You will not see drawings. Every screen is read from the Swift, Kotlin or React it is written in.
All of it at once
Enough of seeing your app one screen at a time in a simulator, and of sending screenshots to change a button.
A real design tool
Frames, auto layout, components, variables and prototypes, on your app’s real screens. A push sends the change to its code.
Lindi’s canvas does not hold an HTML design of your app. It holds the code your app ships in.
Open the app
you already have.
Choose your project folder in Lindi Desktop. Lindi reads it and puts every screen on the canvas, as layers you can edit.
Bring the agent
you already pay for.
Once your screens are on the canvas, Lindi Agentic connects Claude Code, Codex, Cursor or any MCP client to the file. It runs on your own subscription, reads your designs, and changes them on the canvas while you watch.
- One command to connect, with a token you can revoke
- Your agent on the canvas, with its own cursor
- Every change it makes is one step to undo
claude mcp add --transport http --scope user lindi https://lindi.design/api/mcp --header "Authorization: Bearer PASTE_YOUR_TOKEN_HERE"Change it on the canvas.
Push it to your code.
What your agent builds is yours to change. Restyle a screen or say what should be different, then push. The change lands in your code and goes through the review your team already runs.
Design on your real screens
Select a layer and change it, as you would in any design tool. The screen is drawn from your code, so the change is a change to the real screen.
Or describe it to Lindi Build
Say what should be different, and build it with Lindi Build in the Code tab. It shows you each edit before it makes it.
Push, and the code changes
A push writes what it can straight into your files, such as text, styles and tokens, and hands the rest to Lindi Build. Either way the change lands as ordinary edits, ready for someone to read.
Or hand it to your agent
Claude Code, Codex, Cursor or any coding agent that speaks MCP reads the design, with its real sizes and variables, and writes the change.
Change it once, everywhere
Edit a component or a variable at its source, and every screen that uses it follows.
One file, every role
Design, product and engineering open the same file. The role decides the view, and the server decides the role.
Bring the whole team
into the same file
Everyone in the same file
Cursors, presence and live editing, on the real screens of your app.
Comments on the exact spot
Pin a note to the screen it belongs to, and answer it where the work is.
Branch, review, merge
Try a change on a branch of the file, ask for a review, and merge it back when it is ready.
Only the tools you use
On a whitelabel, switch off what your teams do not use. What is off is gone from the interface and blocked on the server.
Every version has a name on it
Named checkpoints, and whoever made them. Restore one and the current version is saved first.
Who is allowed to do what
Every role carries an explicit list of permissions, set in one place and checked on the server.
One library for the team
Publish a file as a library, and the whole team designs from the same components and variables.
You decide who can do what
The six things a security review asks about. Each one is a setting in the product, checked on the server.
- Roles & permissions
Every role carries an explicit list of permissions, set in one place and checked on the server.
- Sharing you can audit
A link is off, company-only or open to anyone, and grants viewing or editing. Requests for access wait for the owner or an editor, and every change is logged.
- An AI switch
An admin can turn AI off for the whole company. Requests in flight stop, new ones are refused on the server, and the change is logged.
- Version history
Every file keeps its own history, with checkpoints you name. Restoring an old version saves the current one first, so nothing is lost.
- Branch & review
Try a change on a branch of the file, ask for a review, and merge it back when it is ready. The original is untouched until then.
- Whitelabel
Lindi under your brand and domain, with your design system built in and only the tools your teams use. We set it up and run it with you.
Built and shipped with
National institutions, and the teams that build for them.
Put your app on the canvas.
Lindi is free for its early users. Sign up, open your project, and your screens are on the canvas.
- 1Sign up, free
- 2Open your project folder in Lindi Desktop
- 3Connect the agent you code with
- 4Push your first change into your code
Already in production,
at national scale.
Lindi came out of Nacew, an agency that delivered government software used by tens of millions of people. We met the handoff on every engagement, and built Lindi to remove it.
- 35M+
- citizens servedthe end users of applications built on Lindi
- Live
- government deploymentsrunning in production, in daily use today
Nacew · Riyadh & Prishtina
