Skip to main content

Connect. Design.
Push to code.

Connect your repo or project folder, design on its real screens, and push. Then build the rest with Lindi Build or your own agent.

A designer working at a studio desk, a colleague behind them
Your code, on the canvas

An intelligent canvas, connected to your code.

  • Your screens, from your code.

    Connect a repository or a folder on your machine, and Lindi puts the app’s screens on the canvas.

  • Design built like code.

    Auto layout behaves like real layout, and variables are the values your code reads, so there is nothing to translate later.

  • Push, and the code changes.

    A push writes the design change into your code, through Lindi Build or the coding agent you already use.

  • Lindi Build, in the Code tab.

    Describe what you need, and build it with Lindi Build. It shows you each edit before it makes it.

  • Your coding agent, connected.

    Claude Code, Codex, Cursor or any agent that speaks MCP reads the design as data and builds with you.

  • Dev Mode for the details.

    Measurements, annotations, variables and code for any selection, and a list of every screen ready to build.

Open the app
you already have.

Choose your project folder in Lindi Desktop and its screens are on the canvas, read from the code they are written in. This is what it reads today.

  • SwiftUIiOS

    Read from your Swift, with nothing run. Lindi finds the screens and draws them at iPhone size, in your asset-catalog colours.

    Text, colours and fonts publish back into the Swift.

  • React / Next.jsWeb

    Lindi runs your app and captures each page as it renders. Next.js pages are found for you.

    Words and tokens publish back into the source.

  • AngularWeb

    Pages are found from your routes and drawn from the code, with nothing run.

  • Jetpack ComposeAndroid

    Read from your Kotlin, with nothing run. Screens are drawn at phone size, in your Material theme.

    Colour and size tokens publish back into the Kotlin.

  • HTML/CSSWeb

    A plain site, no framework needed. Every .html file in the folder is a page.

  • Other web appsWeb

    A web app on a dev server, such as a Vite app. Lindi runs it, and you add the paths to capture.

NextFlutter, React Native

Your design tokens come with the screens: CSS variables, your Tailwind theme, asset-catalog colours and Compose colour schemes.

Three ways to work.
One canvas, on your code.

Design on your real screens.

The screens come from your code, so what you design is the app. You get frames, auto layout, components and variables, and your team on the canvas beside you.

  • Screens extracted from your project
  • Auto layout that behaves like real layout
  • Variables with light, dark and brand modes
  • Live cursors, comments and follow

Describe it. Lindi Build builds it.

In the Code tab, say what you need in plain words, and build it with Lindi Build. It asks before each edit, unless you let it edit on its own.

  • Every edit shown to you, with its diff
  • A plan first, when you ask for one
  • New screens and changes, written as code
  • Publish sends your design changes to it

Push, and the code changes.

Push from the canvas and the change is written into your code, by Lindi Build or by Claude Code, Codex or Cursor. Your team reads it and ships it the way it ships everything.

  • The change, as code in your project
  • Written by Lindi Build, or by your own agent
  • Design context in React, HTML and CSS, SwiftUI or Compose
  • Your codebase, your review, your rules

From your code to the canvas.
And back, as code.

AgentsLindi BuildCheck designsMCP → Claude Code · Codex · Cursor
Repositorytavola/storefront · mainconnected, screens extracted
Project folder~/projects/tavolarun on your own machine
TavolaMenu · iPhone 15shipped from your codebaseyour review
Add a tip step before Place orderbella · in plain words, to Lindi Build
  • Designersthe lookDish cardradius/lgauto layout
  • Product peoplethe screensCheckout flowTip stepiPhone 15
  • Developersthe codeDishCard.tsxDev ModeMCP token
The pushDishCard.tsx+14 −6 · 2 fileswritten to code
Reviewdana approvedyour tests · your reviewa person signed off
the next change starts on the canvas
A repository, a project folder and a sentence to Lindi Build come into one file. Designers, product people and developers work in it at once, each in their own lane, with the agents docked above. The change leaves as a push written into the code, is reviewed and approved by a person, ships from your codebase, and the next change starts on the canvas again.
  • Designersthe look
  • Product peoplethe screens
  • Developersthe code

One change, start to finish.

A designer changes a real screen and pushes, the team builds the rest with Lindi Build, and ships it the way it always does. Nobody redraws, respecifies or retypes anything.

  1. 12 Aug · 14:02SofiadesignRestyled the dish card: rounder corners, bolder priceDesign
  2. 12 Aug · 14:05SofiacodePushed it; built DishCard.tsx and menu.css with Lindi Buildpush
  3. 12 Aug · 14:20BellabuildAsked Lindi Build for a tip step at checkoutBuild
  4. 13 Aug · 09:41MarcoreviewReviewed both changes in the code and shipped themyour review

Your code changes
only when you ask.

  • Nothing changes until you ask.

    Editing the design does not change your code. It changes when a developer accepts a design you push, or when you ask Lindi Build to build. Opening a web app adds a small lindi-library folder to it, and you see that edit first.

  • Your review still decides.

    A push lands as ordinary changes in your project, so your usual review covers it before anything ships.

  • AI on your terms.

    An owner can switch AI off for the whole company, and every change to that setting is recorded.

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.

  1. 1Sign up, free
  2. 2Open your project folder in Lindi Desktop
  3. 3Connect the agent you code with
  4. 4Push your first change into your code