Astryx is Meta’s open-source design system built on React and StyleX. It includes accessible components, brand-level themes, templates, dark mode, CLI/MCP docs, and customization paths for both developers and AI agents.
Meta has open-sourced Astryx, the design system that has powered over 13,000 internal tools for the last 8 years. It’s out now in beta on @React and StyleX.
Astryx was built from the ground up for agents. Most design systems assume a human is reading the docs. Astryx lets agents read the same API reference through the CLI, so your agents build UI using the exact same system a human would, rather than hallucinating component props.
They also avoided the usual customization trap. You can theme it at the token level so your app doesn’t look like a Meta clone, but you can also fully eject a component’s source code if you need absolute control.
Report
@zaczuo Congratulations on the launch. This looks pretty cool.
Report
@zaczuo the thing that'd actually save me time is the agent reading the same api ref i do. right now claude code building an angular component against our own design system just guesses props — invents a variant that doesn't exist — and it surfaces in review, not at build. one ref both sides pull from kills that whole class of bug.
Report
The "eject the component" option sounds great until you're the one maintaining a forked mess later.
Report
Token level theming vs full eject is a real tradeoff. The more teams eject the less they benefit from upstream fixes. Curious how often that happens in practice.
Report
How does the agent readable API actually compare to what Radix or shadcn already expose? Those aren't bad either.
Report
No mention of Vue or Svelte support here that's a gap for some teams.
Report
8 yrs of internal use means it's battle tested, but packaging something for public use is a different job entirely.
Report
Does the CLI reference update automatically when components change?
Report
Hooked an agent up to our old design system last year and it kept inventing props that didn't exist. If Astryx actually solves that, it's worth trying for our team.
Report
Every big company says their design system is "built for agents" now. What's actually different here versus just having clean, well written docs that a model can parse?
Report
The tagline points to digital connection, but the topic hints cover a pretty wide span: Design Tools, User Experience, AI Workflow Automation, Marketing & Sales, and AI Agents. Is Meta meant to start with one specific user group first, like designers, community builders, or product teams, or is the idea to connect those workflows from day one?
Replies
Flowtica Scribe
Hi everyone!
Meta has open-sourced Astryx, the design system that has powered over 13,000 internal tools for the last 8 years. It’s out now in beta on @React and StyleX.
Astryx was built from the ground up for agents. Most design systems assume a human is reading the docs. Astryx lets agents read the same API reference through the CLI, so your agents build UI using the exact same system a human would, rather than hallucinating component props.
They also avoided the usual customization trap. You can theme it at the token level so your app doesn’t look like a Meta clone, but you can also fully eject a component’s source code if you need absolute control.
@zaczuo Congratulations on the launch. This looks pretty cool.
@zaczuo the thing that'd actually save me time is the agent reading the same api ref i do. right now claude code building an angular component against our own design system just guesses props — invents a variant that doesn't exist — and it surfaces in review, not at build. one ref both sides pull from kills that whole class of bug.
The "eject the component" option sounds great until you're the one maintaining a forked mess later.
Token level theming vs full eject is a real tradeoff. The more teams eject the less they benefit from upstream fixes. Curious how often that happens in practice.
How does the agent readable API actually compare to what Radix or shadcn already expose? Those aren't bad either.
No mention of Vue or Svelte support here that's a gap for some teams.
8 yrs of internal use means it's battle tested, but packaging something for public use is a different job entirely.
Does the CLI reference update automatically when components change?
Hooked an agent up to our old design system last year and it kept inventing props that didn't exist. If Astryx actually solves that, it's worth trying for our team.
Every big company says their design system is "built for agents" now. What's actually different here versus just having clean, well written docs that a model can parse?
The tagline points to digital connection, but the topic hints cover a pretty wide span: Design Tools, User Experience, AI Workflow Automation, Marketing & Sales, and AI Agents. Is Meta meant to start with one specific user group first, like designers, community builders, or product teams, or is the idea to connect those workflows from day one?