Meta’s Astryx Brings a CLI and MCP Server to an Open-Source React Design System Agents Can Read
Meta released Astryx this week. It is an open-source design system, currently in Beta. The project grew inside Meta’s monorepo over eight years. Astryx is built on React and StyleX. StyleX is Meta’s compile-time CSS engine. TL;DR Astryx is Meta’s open-source, agent-ready React design system, now in Beta. It pairs StyleX styling with a CSS-variable theme cascade and ten themes. A CLI and MCP server lets AI agents scaffold and document UIs. It is production-teste
Get smart on it
Meta released Astryx, an open-source React design system currently in Beta that has been developed internally over eight years. The system includes over 90 components, foundations for typography and layout, templates for full pages, and ten customizable themes, all built on React and StyleX, a compile-time CSS engine. What distinguishes Astryx from similar design systems is its agent-ready tooling: it ships with a CLI and MCP server that allow AI agents to read structured documentation, scaffold components, and automate UI building through a self-describing JSON manifest rather than parsing help text. This makes Astryx particularly useful for internal dashboards, agent-built user interfaces, and multi-brand products that need to share components across different themes.
Related news
The fittest founder in the room got cancer. Here’s how he used AI to fight back.
When confronted with cancer, Connor Christou fed everything tied tied to his regime — blood results, scan data, wearable output, journal entries — into Claude.
Building Supervised Fine-Tuning Data from NVIDIA Open-SWE-Traces: Trajectory Parsing, Patch Analysis, Token Budgets, and Tool-Use Metrics
In this tutorial, we explore the Open-SWE-Traces dataset as a practical resource for studying and preparing agentic software-engineering trajectories for fine-tuning. We stream the dataset directly from Hugging Face, so we can work with a large dataset efficiently in Google Colab without downloading everything locally. We inspect individual records, normalize multi-turn agent conversations, parse final code patches, extract useful metadata, and build an analysis DataFrame to understand trajecto
