Notes from
the file.
What we are building, why, and what we learned building it.
More posts
- Engineering
How a generated screen lands as real layers
Ask Lindi Code for a screen and what reaches the canvas is frames with auto layout, real component instances and prototype links — editable like anything you drew. Here is how the generation is built so that is true.
- Product
Your coding agent can read the file now
Claude Code, Codex, Cursor — any agent that speaks MCP can now connect to a Lindi file and fetch its structure, its variables and its full context, with a token you issue and can revoke.
- Design
Branches, for people who never wanted them
Engineers have had a safety net for decades: work on a copy, ask for a review, merge it back. Designers mostly have not. Here is how branches work on the canvas, and why they show you conflicts instead of resolving them for you.
- Engineering
Where did my chat history go? A post-mortem
For a while, a Build thread with Lindi Code could vanish between a reload and a return. It had four causes, all real. This is what they were, and the rule we now hold everything to: the database is the source of truth.
- Product
Who can see the file, and who can change it
Owner, editor, viewer. A link for your company, or for anyone who holds it. Access requests that grant nothing until someone says yes. How sharing works on the canvas, and the one rule under all of it.