An open-source project launched to counter Anthropic’s subscription-locked Claude Design tool has accumulated more than 40,000 GitHub stars in approximately two weeks, one of the fastest traction curves for a developer tool so far this year. The repository, nexu-io/open-design, built by the team at nexu-io, positions itself as a free, locally operated alternative to Claude Design — the AI-powered visual creation tool Anthropic released on April 17 — and the speed of its uptake reflects documented frustration with Claude Design’s usage caps and pricing model.

The urgency is concrete. A PCWorld reporter testing Claude Design on a $20-per-month Pro subscription exhausted 80 percent of the weekly Claude Design allowance in roughly 25 minutes of prototyping, then burned through the remainder in five minutes after switching AI models. That episode, widely circulated among developers on Reddit and X in late April, crystallized a concern that had been building since the April 17 launch: Claude Design’s separate weekly usage limits sit inside an already-subscription-gated product, and on the entry-level plan, they run out fast.

Claude Design’s Subscription Wall Fueled the Push for an Open Alternative

Anthropic launched Claude Design on April 17 as a research preview for Pro, Max, Team, and Enterprise subscribers, built on top of Claude Opus 4.7, the company’s most powerful publicly available vision model. The tool generates interactive prototypes, pitch decks, slides, and one-pagers from text prompts, and can ingest a team’s existing codebase to apply its design system to every output automatically. Figma’s stock fell roughly seven percent on the day of the announcement.

The product is excluded entirely from Claude’s free tier. On the entry Pro plan, priced at $20 per month, Claude Design runs its own separate weekly allowance that does not draw from a user’s chat or Claude Code quotas — but that allowance is finite and opaque. Users who exceed it can pay additional fees at API rates. The community response at r/ClaudeAI landed closer to a “resounding meh” than enthusiasm, with token limits and generic visual output as the two dominant complaints.

40,000 Stars, 31 Skills, 72 Design Systems

Into that gap stepped nexu-io/open-design. The project auto-detects 16 AI coding-agent command-line tools already installed on a user’s machine — including Claude Code, OpenAI Codex, Gemini CLI, Cursor Agent, GitHub Copilot CLI, Hermes, Kimi, DeepSeek TUI, and eight others — and routes design generation tasks through whichever agents are available. The orchestration layer ships with 31 composable design-generation skills and 72 brand-grade design systems, and exports finished work as HTML, PDF, PPTX, or MP4, with a sandboxed live preview before any file is committed.

The project crossed 40,000 stars in approximately two weeks — a figure the maintainers have put directly in the repository’s README as a rallying call for further contributions, with version 0.8.0 in active development. As of this writing, the most recent commit landed three days ago.

Unlike Claude Design, the project requires no Anthropic account and imposes no usage limits beyond what the underlying AI provider applies to its own API. The entire pipeline runs locally via Node.js and pnpm, and a one-click Vercel deployment option is available for teams that want web access without running a local server. The project also ships a Model Context Protocol server, allowing any MCP-compatible editor — Cursor, VS Code, Zed, Windsurf — to read Open Design project files directly, eliminating the export-then-reattach loop that slows iteration when moving between a design tool and a coding agent.

Bring Your Own Key — But Not Necessarily Your Own Privacy

The project is transparent about its privacy model, which is more nuanced than “fully local.” Open-design follows a strict bring-your-own-API-key architecture at every layer: there is no telemetry baked into the project itself, and the project’s maintainers receive no data from user sessions. However, design prompts and generated content are routed to whichever AI provider a user has configured. A user running Claude Code as the design engine is subject to Anthropic’s data policies; a user running Codex is subject to OpenAI’s. The project documents this trade-off explicitly in its repository.

This distinction matters for the enterprise and developer users that open-source advocates argue are most poorly served by cloud-only AI tools. The 2026 State of Open Source Report, produced by Perforce in collaboration with the Open Source Initiative and the Eclipse Foundation, found that 55 percent of organizations now cite avoiding vendor lock-in as a driver of open-source adoption — a 68 percent increase year-over-year. “This year’s findings confirm what the open source community has long understood: the freedom to choose your own technology path is a strategic necessity,” said Deb Bryant, interim executive director of the Open Source Initiative. For teams operating under strict data-handling policies, the ability to run the generation pipeline on local hardware — and to swap the underlying model — addresses a structural limitation that cloud-only tools cannot resolve by design.

Anthropic’s Defensive Moves Confirm the Competitive Pressure

Anthropic has not publicly commented on open-design, but its recent product moves suggest it is acutely aware of the cost-competitiveness problem that open-source alternatives exploit. On May 13, 2026, the company raised Claude Code weekly usage limits by 50 percent for all Pro, Max, Team, and seat-based Enterprise users, effective through July 13. That followed a doubling of hourly limits on May 6 and the removal of peak-hour throttling in April — three capacity expansions in five weeks. One analysis attributed the May 13 increase directly to competitive erosion from OpenAI’s Codex, which reportedly consumes 4.2 times fewer tokens for equivalent tasks.

John Breitenfeld, chief revenue officer of Percona, an open-source database infrastructure firm, told LinuxInsider in January 2026 that “in every downturn, open source has been an accelerator of innovation and growth, and 2026 will be no different.” The analyst Violetta Bonenkamp, writing in May 2026, put the structural argument in sharper terms: “If you depend on closed vendors for your product logic, your margin, or your customer relationship, you are building on rented land.”

Early Instability and Unsigned Installers

The project’s rapid growth has not been problem-free. Version 0.4.0 shipped with a confirmed startup-blocking bug — the bundled daemon crashed on first import due to a packaging error — and had to be immediately superseded by version 0.4.1. The Windows installer is unsigned, triggering SmartScreen security warnings on first launch, with code signing flagged for a future release. Linux users on the 0.4.0 stable build were directed to run from source while desktop packaging was hardened. These are the growing pains of a project that shipped its first public release and immediately attracted hundreds of contributors, but they are relevant for teams evaluating it for production use.

The project is licensed under Apache 2.0 and MIT, and is available at github.com/nexu-io/open-design. TechTimes has not independently audited the codebase.

For Claude Design subscribers who have hit their weekly limit before a project is finished: open-design is free, local, and receiving a new commit roughly every three days. Whether it sustains that pace depends on whether the more than 40,000 people who starred it in the first two weeks decide to contribute — not just watch.