404
The link may be old, or the address may be incomplete.
About the project
Layntra was created by Haozi to give product managers and nontechnical builders a controlled path from Codex intent to editable Figma work.
AI can describe a design, generate an image, or suggest code. Those are useful outputs, but they do not automatically create a trustworthy workflow inside the design file. When an AI can write, the user needs to know which file and selection it will touch, whether the current action is read-only, and how to recover.
+Layntra treats “AI to Figma” as infrastructure rather than a poster generator. Its core contract is inspect → plan → apply → undo. Poster creation can be an example skill, but the bridge and control model are generic.
+The primary audience is product managers, founders, researchers, writers, operators, and other people who can describe product intent but do not want to learn an integration protocol before they can work. Installation is documented step by step; normal use happens through explicit commands and plain-language instructions in Codex.
+Layntra is released under the MIT License. The source, architecture decisions, security policy, roadmap, tests, and current limitations are public on GitHub. Contributions and critical feedback are welcome through GitHub Issues.
+ +Straight answers
What it is, what it costs, what stays local, what Figma still controls, and what a nontechnical user needs to install.
Layntra is an open-source Codex plugin and local Figma companion. It lets you inspect a Figma target, review a plan, explicitly apply supported editable changes, and undo the last guarded write.
Yes. Layntra is free and open source under the MIT License. Version 0.1.0 has no hosted Layntra account or paid Layntra plan.
No. Layntra does not bypass Figma permissions, organization policies, seat types, or plan restrictions. Its companion must run where Figma Design plugins are permitted.
No. Layntra uses a Figma companion plugin and a bridge bound to local loopback, so it does not ask for a Figma API token.
No. The Layntra bridge between Codex and Figma is local, but Codex model access and data handling follow your Codex configuration.
After installation, the normal workflow uses explicit natural-language commands in Codex. Initial setup requires cloning the repository, running one install script, and importing a manifest file in Figma Desktop. The illustrated guide shows the exact path.
Yes. Supported output is created as editable Figma nodes rather than a flattened screenshot.
$layntra?The explicit command makes activation, target, mode, and write intent visible. Regular conversation stays regular conversation; it does not silently become permission to modify Figma.
Version 0.1.0 supports bounded creation and updates for common editable nodes, with batches limited to 100. It does not expose deletion or arbitrary code execution.
Layntra refuses the write. Run status or plan again against the new target instead of letting the system guess.
Open a public GitHub issue with the command you ran, what you expected, and any safe-to-share error text.
A practical comparison
Layntra is for people who want Codex to inspect and change editable Figma layers through a local companion—with an explicit plan and write command.
“Figma MCP” can describe different products. The useful comparison is not a brand claim; it is where the bridge runs, what credentials it needs, what can write, and how you recover.
| Question | Layntra v0.1.0 | Typical hosted integration |
|---|---|---|
| Where is the bridge? | On your Mac, bound to local loopback | Often on a remote service |
| What account is required? | No hosted Layntra account | May require a provider account |
| Figma API token? | Not required | Depends on the integration |
| Write boundary | Separate plan and apply commands | Varies by product |
| Stale target protection | Page and selection are checked before writing | Varies by product |
| Output | Supported editable Figma nodes | May be read-only, image-based, or editable |
| Recovery | Guarded Figma undo checkpoint | Varies by product |
| License and price | MIT licensed; free | Depends on the provider |
Layntra does not bypass Figma plans, organization policies, seat types, or plugin permissions. The companion must run in a Figma Design file where your account is allowed to use plugins. If an organization seat blocks Design plugins, a personal Starter workspace may be suitable for testing.
+Layntra also does not claim every hosted workflow needs a token or lacks controls. Integrations change. Check the current documentation of any product you compare.
+Architecture and control model
A Codex skill defines the interaction. A bridge carries bounded commands over local loopback. A Figma companion applies supported changes only after an explicit write instruction.
Codex skill
+ ↓ local stdio / MCP
+Layntra bridge
+ ↓ WebSocket on 127.0.0.1:3846
+Figma companion plugin
+ ↓ supported Figma Plugin API operations
+Editable Figma nodesThe bridge binds to 127.0.0.1, so it accepts connections from the same machine rather than exposing a hosted Layntra endpoint. You do not create a Layntra account or provide a Figma API token.
Codex is still the model-facing part of the workflow. Its data handling follows your Codex configuration. “Local bridge” describes the connection between Codex and Figma; it does not mean the model runs offline.
+ +$layntra status, inspect, and reviewThese are read-only. They can report the active companion, file, page, selection, and supported node structure, but they do not modify Figma.
+$layntra planPlanning converts your intent into a proposed change set tied to the current target. It remains read-only and reports “No Figma changes made.”
+$layntra applyApply is the explicit write boundary. Before writing, Layntra checks that the page and selection still match the planned context. A stale target is rejected instead of guessed.
+$layntra undoUndo is available after a successful write and is guarded against the expected target. Layntra uses a Figma undo checkpoint rather than trying to reconstruct the previous design.
+ +Layntra can inspect supported nodes, create editable frames, text, rectangles, ellipses, lines, and groups, and update a bounded set of properties. A write batch is limited to 100 nodes.
+Version 0.1.0 exposes neither node deletion nor arbitrary code execution. It does not bypass Figma workspace, seat, plan, or plugin permissions. Use it only in files where your Figma account is allowed to run Design plugins.
+ +The project includes automated contract and bridge tests plus a real Figma end-to-end run covering connection, reading, creation, update, stale-target rejection, invalid input, reconnection, and guarded undo. The test scope is documented in the public E2E report.
+ +Open source · Codex plugin + Figma companion
+Layntra helps product managers and nontechnical builders inspect, plan, apply, and undo editable Figma changes from Codex. The bridge stays on your machine. No Figma API token. No hosted Layntra service.
+ +Free under the MIT License · macOS · Node.js 20+ · Codex Desktop or CLI · Figma Desktop
+Control before automation
+Ordinary chat is vague. Layntra uses an explicit command, target, mode, and write boundary so you can see what Codex is about to do.
+Check the active file, page, selection, and editable node structure without changing Figma.
Review the intended changes before any write. A plan is not hidden inside a chat response.
Layntra refuses the write if the page or selection changed after planning.
Undo is guarded against the same target, then the result is read back for verification.
One local path
+$layntra in Codex.Why Layntra exists
+Figma access can vary by plan, workspace, and seat. Some organization seat types cannot run Design plugins. Layntra provides a free, open-source local workflow where plugins are permitted; it does not bypass Figma permissions or plan restrictions.
+There is no Layntra cloud account, telemetry service, or Figma API token. Codex still follows your own Codex configuration and data controls—the local bridge does not make the model offline.
+Read the detailed comparison with hosted Figma MCP workflows →
+The first five minutes
+You install one Codex plugin and import one Figma companion. The beginner guide shows every menu and the exact file to choose.
+Clone the repository and run ./scripts/install.sh.
Download the ZIP, unzip it, and import the included manifest.json.
Keep the companion open and enter $layntra status in a new Codex task.
Version 0.1.0
+Layntra is early and intentionally bounded: supported editable nodes, batches of at most 100, no deletion, and no arbitrary code execution.
+ +Last updated August 1, 2026
Layntra is an open-source local tool, not a hosted account service. This page separates the website, local bridge, Codex, Figma, and GitHub boundaries.
+The Layntra website is a static GitHub Pages site. It does not set Layntra cookies, run Layntra analytics, show ads, or contain a Layntra contact form. GitHub may process request and security data when it serves GitHub Pages; refer to GitHub’s own privacy statement for that platform processing.
+The bridge binds to 127.0.0.1:3846 on the user’s machine. Layntra v0.1.0 does not send bridge telemetry to a hosted Layntra service and does not require a hosted Layntra account.
Layntra is not an offline AI model. Prompts, context, and model data handling are governed by the user’s Codex product, account, settings, and applicable OpenAI terms. Users should avoid sending secrets or sensitive design content unless their configuration and organizational policy permit it.
+The companion runs through the Figma Plugin API in Figma Desktop. Figma files, accounts, workspace rules, and product telemetry remain governed by the user’s relationship with Figma.
+Downloads, repository activity, stars, issues, pull requests, and discussions occur on GitHub and are governed by GitHub. Public issues and pull requests are visible to others. Do not include credentials, private file identifiers, or confidential screenshots.
+For a Layntra privacy or security question, open a private security report when the topic is sensitive, or a public GitHub issue for general questions.
+Last updated August 1, 2026
Layntra is an open-source software project, not a hosted design service. These notes summarize the project boundary; the repository license is controlling.
+Layntra source code is offered under the MIT License. You may use, copy, modify, merge, publish, distribute, sublicense, and sell copies subject to that license’s conditions.
+The MIT License provides the software “as is,” without warranty. You are responsible for reviewing planned changes, protecting your files, maintaining backups or version history, and deciding whether Layntra is appropriate for your environment.
+Codex, GitHub, Figma, Node.js, and operating-system services are third-party products with their own terms, privacy policies, availability, and technical requirements. Layntra does not change or override them.
+You must use Layntra only with files, workspaces, accounts, and systems you are authorized to access. The project does not grant additional Figma permissions or bypass plan, seat, organization, or plugin restrictions.
+Layntra is an independent open-source project and is not affiliated with, endorsed by, or sponsored by Figma or OpenAI. Figma, Codex, OpenAI, GitHub, and other names may be trademarks of their respective owners.
+The project may change, add, or remove capabilities in future releases. No uptime or support-level commitment is offered. Current source, releases, and support channels are available on GitHub.
+