Meta open-sources Astryx, the design system behind 13,000 internal apps, with a CLI built for coding agents
Meta has released Astryx, the React design system it has used internally for eight years, under the MIT licence. It ships 150+ components, seven themes and a CLI that coding agents can query for component docs, templates and codemods.
Updated November 20, 2026: Expanded with setup steps, the CLI commands agents use, theming and the beta limits.
Meta has open-sourced Astryx, a React design system that, according to its README, grew inside the company over eight years to become its most-used and largest, powering more than 13,000 internal apps. It is released under the MIT licence, is labelled beta, and is built on React 19 and StyleX. The GitHub repository had more than 30,000 stars when we checked on November 20, 2026. Before installing anything, you can browse the components in the live Storybook and try them in the Sandbox linked from the docs site.
What is in it
- 150+ accessible React components with full TypeScript types, plus dark mode, ready-made templates and patterns for common pages such as tables, detail layouts and form wizards.
- Seven themes: neutral, butter, chocolate, matcha, stone, gothic and y2k. Each theme is a set of CSS custom property overrides, so a brand can restyle Astryx without forking or wrapping component code.
- Styles authored with StyleX but shipped as pre-built CSS, so there is no build plugin or styling library to adopt. You can override with className using Tailwind, CSS modules or plain CSS.
- Open internals: the building blocks inside components are exported, and a swizzle command copies a component's full source into your project when you need to own it.
The part aimed at coding agents
Meta's stated principle is one system for humans and AI: the API, conventions, docs and CLI are designed together so a person and an assistant build from the same reference. In practice that means the astryx CLI is the main way to learn the library. It prints component docs, design tokens, page templates, theming tools and upgrade codemods from the terminal, where coding agents already work. Commands can return typed JSON with --json; astryx manifest --json reports which commands support it.
A few commands stand out for agent use:
- astryx search button ranks matching components, hooks, docs, templates and themes, and prints the follow-up command for each result.
- astryx component Button prints that component's documentation; --dense gives a token-efficient version.
- astryx manifest --json returns every command, option and response type, which the README compares to an OpenAPI spec for the CLI.
- astryx mcp serves every command as an MCP tool over stdio, for AI tools that cannot run shell commands.
- astryx doctor runs health checks on a project without changing anything in it. Each check prints a status, a message and, when one is available, an actionable fix; the sample output includes a Node version check against a minimum of 22.13.0.
- astryx upgrade updates your code after you upgrade Astryx, astryx theme adds and switches themes, and astryx gap-report sends a report about a missing component or feature to the package that owns it.
The setup step is agent-aware too: astryx init saves the Astryx guide to AGENTS.md or CLAUDE.md, so an agent reads it before writing UI instead of guessing the API from training data.
How to try it
Install the core package, a theme and the StyleX peer dependency, add the CLI as a dev dependency, then run init once before writing UI:
npm install @astryxdesign/core @astryxdesign/theme-neutral @stylexjs/stylex
npm install -D @astryxdesign/cli
npx @astryxdesign/cli init
npx @astryxdesign/cli component --listSetup is a few CSS imports plus a theme provider, with guides for Next.js, Tailwind, Vite and a CDN. Two practical tips from the README: add an npm script that points at the project's own copy of the CLI, so agents and new developers avoid path errors, and never run the bare name astryx through npx before installing, because that resolves to an unrelated npm package. You can also install the CLI globally; inside a project it still runs that project's version.
Limits
It needs React 19 or later. The project is labelled beta and the README makes no promise of API stability, so check the migration notes (astryx docs migration) before upgrading. Chart components and the Vega chart wrapper are published only under a canary tag with no stable release yet, and the experimental lab package is not published at all. Theme editing sits under the experimental command, which may change in a patch release. Contributors need Node 22 or later and pnpm.
Related on claudefox
- stack-diagram: an unofficial agent skill that turns one sentence into an architecture diagram with official logo files
- Univer: embed a spreadsheet and document editor in your own app
Our take
Plenty of component libraries are good; what makes Astryx notable is that the same system is designed for people and for AI assistants. In our view, a CLI that answers with the installed version's own component docs targets a familiar failure of AI-written frontend code: inventing props that do not exist. If you already let an agent build UI, that makes it worth a trial in a side project. For production, the beta label and the unreleased chart packages argue for waiting or pinning versions.
Source: meta/astryx (GitHub), @astryxdesign/cli README (GitHub), Astryx documentation
This story first appeared in the claudefox daily briefing for November 12, 2026.