🔥 Open Design 0.8.0-preview — Design's old world ends here. Help us build the new one. #1727
Replies: 16 comments 4 replies
-
|
Let's friggin go! Keep up the good work |
Beta Was this translation helpful? Give feedback.
-
|
Congrats !!! |
Beta Was this translation helpful? Give feedback.
-
|
I'm running on an Android only |
Beta Was this translation helpful? Give feedback.
-
|
?? There already is a Windows app 😂
All the best,
Shaya Kutnowski
…On Sun, May 17, 2026, 5:21 p.m. ELMAHDI SNIDI ***@***.***> wrote:
will there be a windows app ?
—
Reply to this email directly, view it on GitHub
<#1727 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABHZPPRLQTDJFSKKMIZ54ND43HDF5AVCNFSM6AAAAACY6GH23SVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMOJVGA3DIMI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I agree with the #DeFigma direction: users should interact through the AI agent, not manipulate a canvas manually. But removing the canvas creates a new UX requirement: users still need to understand the generated layout before they can confidently edit it. I think 0.8.0 needs a “Layout Understanding Layer”: every generated artifact should include stable semantic IDs, a layout map, section intent, editable aspects, and suggested edit intents. The UI can render this as a layout navigator / review surface, while headless users get the same structure as JSON/text. This keeps Open Design agent-native while preserving the spatial clarity people used to get from canvas tools. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, honestly, the Canvas is one of the favourite things designers love
about Figma and other tools.
…On Mon, May 18, 2026 at 7:59 AM huyhoangnhh98 ***@***.***> wrote:
I agree with the #DeFigma direction: users should interact through the AI
agent, not manipulate a canvas manually. But removing the canvas creates a
new UX requirement: users still need to understand the generated layout
before they can confidently edit it. I think 0.8.0 needs a “Layout
Understanding Layer”: every generated artifact should include stable
semantic IDs, a layout map, section intent, editable aspects, and suggested
edit intents. The UI can render this as a layout navigator / review
surface, while headless users get the same structure as JSON/text. This
keeps Open Design agent-native while preserving the spatial clarity people
used to get from canvas tools.
—
Reply to this email directly, view it on GitHub
<#1727 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABHZPPQNOLE6BYC5C6J4FNL43KKDNAVCNFSM6AAAAACY6GH23SVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMOJVGYYTOMY>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
All the best,
Shaya Kutnowski
|
Beta Was this translation helpful? Give feedback.
-
|
"🚧 Not in 0.8.0 yet: we're still finalizing the cut line — the full list lands as an update to this thread shortly." any news on this one? |
Beta Was this translation helpful? Give feedback.
-
|
I feel the current interface changes are somewhat disorganized. Compared to earlier versions, there are many new features now, and I'm not sure how to use them. I still follow the same process of creating a project and adding files to input requirements. Is there a link to product feature demos or instructions? |
Beta Was this translation helpful? Give feedback.
-
|
Will 0.8.0 be usable in web browser instead of an OS daemon as 0.7.0 is? |
Beta Was this translation helpful? Give feedback.
-
|
Confused about taking an existing design and asking open code to improve tweak - seems more focused on starting from scratch? |
Beta Was this translation helpful? Give feedback.
-
|
Keep up the good work guys :) |
Beta Was this translation helpful? Give feedback.
-
|
Impressed 🙏🎇 |
Beta Was this translation helpful? Give feedback.
-
|
I hope the following functions can be enhanced in future versions:
|
Beta Was this translation helpful? Give feedback.
-
|
很棒，我准备写一个插件 |
Beta Was this translation helpful? Give feedback.
-
|
8.0我检测出木马，你没遇到这个情况么？ |
Beta Was this translation helpful? Give feedback.
-
|
It's worth adding more initial design templates. You can take it from |
Beta Was this translation helpful? Give feedback.
-
|
Regarding the plug-in registry, there exists open infrastructure to facilitate a more decentralized architecture without too much complexity. I highly recommend reading up on fair.pm https://github.com/fairpm/fair-protocol/blob/main/docs/start-here.md It enables more democratically operated alternatives to registries like that of wordpress.org Most recently FAIR and its underlying primitives from the AT protocol (which pairs very well with agents) have been adopted for use in the upcoming plugins registry of EmDash. |
Beta Was this translation helpful? Give feedback.
-
|
I truly believe in this🙏🎇 This is Life Code and Sacred to all of us thief stop steeling create is more Life to Create 🙏🎇 |
Beta Was this translation helpful? Give feedback.
-
|
https://github.com/nextlevelbuilder/ui-ux-pro-max-skill need add |
Beta Was this translation helpful? Give feedback.
-
|
No flower will ever open unless is free. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
✊ This is not a release. It's a starting gun.
For the last decade, designers have been doing the same thing every morning: open Figma, push pixels, drag rectangles, name layers, sync tokens, ship a spec, watch engineering reinterpret half of it, redo the spec. Five years of this. Ten years for some of you. An entire profession turned into a click farm for a single tool.
We think that era is over. Two things have to be true for it to actually end — and 0.8.0 is the first release where both are real in the same engine:
🥊 Movement 1 — #DeFigma: kill the canvas, keep the craft.
Figma isn't broken. It's just the wrong unit of work in an agent-native world. A design system shouldn't be a file you maintain. A prototype shouldn't be 200 frames you nudge by hand. A slice export shouldn't be a human ritual. The canvas was a workaround for not having a real engine. We have an engine now.
🤖 Movement 2 — Agent-Native Design: the designer becomes the director.
Claude Design, Open Design — agent-driven design is no longer a demo. It's shipping production-grade design systems, world-class UI, decks, prototypes — for people who cannot draw a rectangle. Not in five years. Today, in this preview. The 10×–100× productivity jump people kept promising for AI tooling? It's here, and it's not coming from a chat box bolted onto Figma. It's coming from an engine where the agent is a first-class citizen and the human gives intent, not coordinates.
We're young. We're rough. We're 40k stars in and accelerating. We need you to help us push the rest of the way. 🚀
🧱 Why we rebuilt the core (and why it matters for the movement)
The last two weeks of 0.7 made one thing clear: the research-preview architecture we started with couldn't carry where the community wanted to take it. So instead of patching around it, we rebuilt the foundation — because a movement needs a kernel that other people can build on, not a demo that only its authors can extend.
0.8.0-preview is that rebuild. Three things are different underneath:
The bigger bet behind all of this: an agent-driven design engine the whole industry can build on — open source, vendor-neutral, agent-runtime-neutral. Not another AI design tool. The substrate the next decade of design sits on top of.
🛠️ How to try it (5 minutes, side-by-side with your 0.7)
Option A — Pre-built installer (recommended)
Latest release build:
0.8.0Option B — Build from source
git clone https://github.com/nexu-io/open-design.git cd open-design git checkout main pnpm install pnpm tools-dev0.7 stable and 0.8 preview don't share runtime data — keep both around, switch as you go.
🙏 We need you. Specifically you. Three ways to enlist.
This is the part that matters. A movement doesn't ship from one team's laptops; it ships from the people who showed up early and built the missing pieces.
1. 🐛 Break it. Loudly.
Anything counts — crashes, "this feels off", "I wish I could…", confusing copy, slow loads. Small reports are the most useful. Don't sit on a half-formed thought; we want it.
→ Open a 0.8.0 preview feedback issue — bugs, suggestions, first impressions, all welcome. The team watches all open issues.
For open-ended thoughts that aren't really a bug — reply on this thread. Every reply is read.
2. 🧩 Write a plugin. Port a piece of the old world.
This is the highest-leverage thing you can do for the movement. The engine is small on purpose — because the plugin surface is where the industry gets ported in. If your team has a Figma workflow, a token sync, an export pipeline, a brand kit, a deck template, a prototype recipe — wrap it as an OD plugin and that workflow becomes agent-native overnight. For your team, and for everyone else.
We will personally help you ship your first plugin. Open an issue titled
Plugin idea: <thing>or ping us on Discord.If you want to send a fix instead, open a PR against
mainas usual — 0.8.0 work now lives there. See what's open.3. 📣 Tell one person.
One designer who's tired of pushing pixels. One PM who's tired of waiting on specs. One engineer who's tired of rebuilding the same component for the fifth time. Send them this thread. The movement scales at the speed of word-of-mouth.
📦 What's in 0.8.0, and what's not
✅ In the preview today: the plugin engine, the official atomic plugins (Todo, direction-pick, question, Figma export, …), the bundled scene plugins (design-system templates, slice, prototype), and the official Plugin Registry source.
🚧 Not in 0.8.0 yet: we're still finalizing the cut line — the full list lands as an update to this thread shortly.
🎯 A few things we'd genuinely like your read on
We can guess where 0.8 is solid. These are the parts we can't:
💬 Discord — the war room
Want rapid back-and-forth with the team and a heads-up on every new build?
→ Join the Open Design preview Discord
This thread stays the primary record. Discord is where the live work happens.
The old world of design is not going to migrate itself. We're writing the engine; you're writing the plugins; together we're porting an entire industry into agent-native ground. Hit Subscribe — the next update is coming fast. 🌅
See you in the PRs. 🫡
🇨🇳 中文版本 · Chinese version (点击展开)
🔥 Open Design 0.8.0-preview —— 设计的旧世界，到此为止。新世界，和我们一起造。
✊ 这不是一次发布。这是发令枪。
过去十年，设计师每天清晨做的是同一件事：打开 Figma，推像素、拖矩形、命名图层、同步 token、交付一份 spec、看着工程师把一半重新解读、再返工 spec。五年这么过来。有人十年这么过来。整个职业，被一款工具变成了一座点击工厂。
我们相信那个时代该结束了。要真正结束，需要两件事同时成立——而 0.8.0 是第一个把这两件事装进同一个引擎的版本：
🥊 运动一 —— #去 Figma：拆掉画布，留下手艺。
Figma 没有问题。它只是在 agent-native 的时代里，成了错误的工作单元。设计系统不该是一份你天天维护的文件。原型不该是 200 个你一帧一帧推的画板。切图导出不该是一种人类仪式。画布，曾经只是"没有真正引擎"时的临时方案。 现在，我们有引擎了。
🤖 运动二 —— Agent-Native Design：让设计师成为导演。
Claude Design、Open Design —— agent 驱动的设计已经不是 demo。它正在产出生产级的设计系统、世界级的界面、PPT、原型——服务于那些连一个矩形都画不出来的人。不是五年后。就是今天，就在这个预览版里。 大家盼了很久的 10×–100× 生产力跃迁？它来了，而且它不是来自某个粘贴在 Figma 上的对话框。它来自一台把 agent 当作一等公民、让人类只输出"意图"而不再输出"坐标"的引擎。
我们还年轻。我们还粗糙。我们 40k stars 在身，且仍在加速。剩下的路，需要你和我们一起推完。 🚀
🧱 我们为什么重写了内核（以及它为什么是这场运动的关键）
0.7 的最后两周让一件事彻底清晰：当初那套 research-preview 架构，已经撑不起社区想把它推到的地方。所以我们没有继续打补丁，而是重铸地基——一场运动，需要的不是一份"只有作者能扩展的 demo"，而是一颗别人可以在上面盖楼的内核。
0.8.0-preview，就是这次重铸。底层有三件事彻底变了：
底层赌注是：一台 agent 驱动的设计引擎，让整个行业都能站上去——开源、厂商中立、agent runtime 中立。 不是"又一个 AI 设计工具"。是未来十年设计行业所依赖的那块基石。
🛠️ 怎么试（5 分钟，和你的 0.7 并存）
方式 A —— 预编译安装包（推荐）
最新正式版本：
0.8.0方式 B —— 从源码构建
git clone https://github.com/nexu-io/open-design.git cd open-design git checkout main pnpm install pnpm tools-dev0.7 稳定版和 0.8 预览版不共享运行时数据——两个都留着，随时切换。
🙏 我们需要你。具体到"你"。三种参战方式。
这一段，才是真正重要的。一场运动不可能只从一个团队的笔记本里发出去；它从那些早早出现、补上缺失拼图的人手里发出去。
1. 🐛 把它弄坏。大声地。
什么都算——crash、"感觉怪怪的"、"我希望它能……"、文案令人困惑、加载慢。小报告反而最值钱。 别按住一个半成形的想法不发，我们想要它。
→ 提交一个 0.8.0 preview 反馈 issue——bug、建议、第一印象都欢迎。团队盯着所有开着的 issues。
如果不算 bug、只是开放式的想法——直接回复这个 thread。 每一条回复都会被读到。
2. 🧩 写一个插件。把旧世界的一块拼图搬过来。
这是你能为这场运动做的最高杠杆的事。引擎刻意保持小——因为插件层才是行业迁移进来的入口。 如果你的团队有一套 Figma 工作流、一套 token 同步、一条导出流水线、一份品牌包、一套 PPT 模板、一种原型套路——把它包成 OD 插件，那个工作流就一夜之间变成 agent-native 的。 为你的团队，也为所有人。
我们会亲手帮你把第一个插件发出来。开一个标题为
Plugin idea: <thing>的 issue，或者在 Discord 找我们。如果你想直接发修复，按惯例提 PR 到
main即可——0.8.0 的代码现在就在那里。看看正在飞行中的 PR。3. 📣 告诉一个人。
一个被推像素推到厌烦的设计师。一个被 spec 拖到崩溃的 PM。一个把同一个组件重写了第五遍的工程师。把这个 thread 发给他。运动的传播速度，等于口耳相传的速度。
📦 0.8.0 里有什么，没什么
✅ 这次预览已经在的： 插件引擎、官方原子插件（Todo、direction-pick、question、Figma 导出……）、内置场景插件（设计系统模板、切图、原型）、官方 Plugin Registry source。
🚧 0.8.0 还没进来的： 仍在敲定边界——完整清单会作为 thread 更新尽快补上。
🎯 几件我们真的想听你怎么看的事
哪里稳，我们自己能猜。这几个地方，我们猜不了：
💬 Discord —— 作战室
想和团队实时来回、第一时间收到每个新构建的提醒？
→ 加入 Open Design preview Discord
主战线还在这个 thread。Discord 是实时活儿发生的地方。
旧世界的设计不会自己迁过来。我们在写引擎；你在写插件；我们一起把一整个行业搬到 agent-native 的土地上。点 Subscribe——下一次更新很快。 🌅
PR 里见。 🫡
Beta Was this translation helpful? Give feedback.
All reactions