Agents

Open Design

Local-first open-source design agent for prototypes, decks, dashboards, images, video, and agent-driven design systems.

58K Stars
6.5K Forks
Apache-2.0 License
nexu-io Maintainer
2026-06-03 Verified
Overview

What is Open Design?

Open Design is a local-first, open-source design agent and desktop studio from nexu-io. It turns coding agents and model routers into a design workflow for web, desktop, mobile prototypes, live dashboards, slide decks, images, videos, and reusable design systems.

Agent-native design workflow

Open Design connects coding agents, model routers, skills, design systems, and previews into one studio for generating artifacts.

It lets teams evaluate AI design as an engineering workflow instead of a closed black-box canvas.

Many artifact types

The project targets prototypes, dashboards, decks, images, videos, HyperFrames, HTML, PDF, PPTX, MP4, and ZIP exports.

That breadth makes it useful for product, marketing, design systems, demos, and internal reporting.

Local-first and open source

The Apache-2.0 repository, desktop app, Docker path, MCP support, and BYOK/API options give teams several ways to inspect and run it.

Design agents touch brand assets, code, prompts, and credentials, so deployment control is part of the product value.
Use cases

What Open Design is built for

01

Claude Design alternative

Use Open Design when you want an open-source AI design agent that can run through local coding agents instead of only a hosted assistant.

02

Design-system-driven prototypes

Pair a DESIGN.md-style brand contract with a design skill to generate web, mobile, dashboard, or deck artifacts.

03

Agent workflow testing

Evaluate how Codex, Claude Code, Cursor, OpenCode, OpenClaw, or other agents perform when the target output is visual and exportable.

04

Self-hosted design automation

Run the Docker or local dev path when you need more control over preview, storage, model access, and artifact generation.

Quick start

Get started in seconds

terminal
$ git clone https://github.com/nexu-io/open-design.git && cd open-design && corepack enable && pnpm install && pnpm tools-dev run web
$ od mcp install codex
$ cd deploy && cp .env.example .env && docker compose up -d
Comparison

How it stacks up

Open Design

vs Claude Design

Claude Design is the closed, polished reference point; Open Design is the open-source local-first alternative for teams that want inspectability, agent choice, and exportable artifacts.

Open Design

vs Figma

Figma remains the mature collaborative visual design canvas. Open Design is better framed as an agent-era artifact generator and design-system workflow, not a total Figma replacement yet.

Open Design

vs AI UI generators

Open Design differentiates through skills, plugins, design systems, coding-agent integrations, local preview, and multi-format export rather than a single prompt-to-screen flow.

FAQ

Frequently asked questions

Is Open Design open source?

Yes. The GitHub repository is published under Apache-2.0 as of the June 3, 2026 verification for this profile.

Is Open Design a Figma replacement?

Not for every workflow. It is better described as an open-source design agent and artifact generator, while Figma remains the mature collaborative visual canvas.

What community feedback should teams watch?

GitHub issues show fast iteration and early-stage bugs, including AMR instruction hallucination, macOS CPU usage, conversation startup, billing/invoice, and model/attachment problems. Public Reddit/X feedback was limited in searchable results at verification time, so GitHub remains the strongest visible feedback channel.

Decision brief

Should you use Open Design?

JSON
Best for
  • Developers and designers who want an open-source Claude Design alternative
  • Teams prototyping web apps, dashboards, mobile flows, decks, and branded artifacts with AI agents
  • Agent builders who want design skills, design systems, plugins, MCP integration, and local-first artifact generation
Not for
  • Teams that need a mature visual canvas replacement for every Figma collaboration workflow today
  • Non-technical users who do not want to manage local apps, agent CLIs, model accounts, or self-hosted services
  • Production teams that cannot tolerate early-stage issues around model behavior, CPU usage, onboarding, or fast-moving releases
Trust and freshness
  • Verified 2026-06-03
  • License: Apache-2.0
  • Repo: nexu-io/open-design
  • Open-source signal
Deployment

cloud

Permission surface

shell/files, external services

Decision signals

MCP

Agent packet

Structured decision data for Open Design

This packet is the compact machine-readable view agents should use before following source links or taking action.

Capabilities

mcp, workflow orchestration

Constraints

open source, mcp compatible

Deployment

cloud

Permission surface

shell/files, external services

Recommended workflows

Coding agent workflow, Connector or protocol layer, Local or private AI stack, Reusable skill workflow

Overview

What Open Design does

What it is

Open Design combines a desktop/web studio, design skills, brand-grade design systems, plugins, MCP tooling, sandboxed preview, and export paths for HTML, PDF, PPTX, MP4, and ZIP artifacts. The public repository describes support for Claude Code, Codex, Cursor, OpenCode, OpenClaw, Copilot, Qwen, Hermes, Kimi, and other agent CLIs.

Why it matters

The product is important because design agents are becoming part of the software delivery loop. Instead of treating design as a closed prompt UI, Open Design exposes the workflow as files, skills, templates, plugins, agent adapters, previews, and exports.

How to evaluate it

A typical Open Design workflow starts with a skill, a design system, and a prompt. The selected agent streams an artifact into the studio, Open Design previews it in a sandbox, and the user can save or export the result. Version 0.9.0 also emphasizes Open Design AMR, an official model router intended to reduce first-run setup.

Facts

Known metadata and operating surface

These fields are separated from editorial interpretation so agents can reason over facts and missing checks.

Resource type agent
Category Agents
Maturity active
Difficulty Unknown
License Apache-2.0
Pricing open source
Verified 2026-06-03
Source confidence high
Risk level elevated
Fit matrix

Where Open Design fits in an agent stack

strong

Coding agent workflow

Open Design has multiple signals for coding agent workflow, including matching tags, capabilities, category, or positioning.

  • Run a small repository change and inspect the diff, tests, and rollback path.
  • Confirm official docs, current maintenance, license, and runtime constraints before production use.
strong

Connector or protocol layer

Open Design has multiple signals for connector or protocol layer, including matching tags, capabilities, category, or positioning.

  • Connect one low-risk service, then inspect schemas, auth scope, errors, and logs.
  • Confirm official docs, current maintenance, license, and runtime constraints before production use.
strong

Local or private AI stack

Open Design has multiple signals for local or private ai stack, including matching tags, capabilities, category, or positioning.

  • Verify hardware requirements, data path, storage, and whether all calls stay in your environment.
  • Confirm official docs, current maintenance, license, and runtime constraints before production use.
strong

Reusable skill workflow

Open Design has multiple signals for reusable skill workflow, including matching tags, capabilities, category, or positioning.

  • Run one skill end to end and check whether it produces evidence or structured output.
  • Confirm official docs, current maintenance, license, and runtime constraints before production use.
partial

Browser automation

Open Design has at least one signal for browser automation, but should be checked against a real task before adoption.

  • Run one non-sensitive website task and inspect clicks, waits, retries, and changed URLs.
  • Confirm official docs, current maintenance, license, and runtime constraints before production use.
weak

Evaluation and observability

Open Design is not primarily positioned for evaluation and observability in the current metadata.

  • Add one repeatable test case and confirm results can run again in review or CI.
  • Confirm official docs, current maintenance, license, and runtime constraints before production use.
Inputs and outputs

What an agent should inspect

Likely inputs

  • Repositories, files, issues, terminal output, and test results
  • Tool schemas, API requests, service resources, and auth scopes
  • Prompts, messages, documents, images, or model inputs
  • Official setup instructions and a small real workflow

Likely outputs

  • Diffs, commits, explanations, test results, or review notes
  • A decision on whether this resource fits the target workflow
Evidence

Sources, claims, and missing checks

Claims are marked separately from source links so future crawlers and reviewers can update them without rewriting the page.

Next action

How to start evaluating Open Design

Inspect repository

Check license, recent activity, issues, examples, and security-sensitive code paths.

Open source

Open Homepage

Start from the official source before adopting third-party instructions.

Open source

Inspect repository

Check license, recent activity, issues, examples, and security-sensitive code paths.

Open source

Run Open Design in dev mode

The official quickstart requires Node 24 and pnpm through Corepack for the local development path.

git clone https://github.com/nexu-io/open-design.git && cd open-design && corepack enable && pnpm install && pnpm tools-dev run web

Install the MCP server for Codex

The README documents one-line MCP install commands for supported coding agents, including Codex.

od mcp install codex
Compare

Alternatives and nearby resources

Use related resources to compare category fit, license, deployment model, and first-workflow behavior.

FAQ

Common questions about Open Design

Is Open Design open source?

Yes. The GitHub repository is published under Apache-2.0 as of the June 3, 2026 verification for this profile.

Is Open Design a Figma replacement?

Not for every workflow. It is better described as an open-source design agent and artifact generator, while Figma remains the mature collaborative visual canvas.

What community feedback should teams watch?

GitHub issues show fast iteration and early-stage bugs, including AMR instruction hallucination, macOS CPU usage, conversation startup, billing/invoice, and model/attachment problems. Public Reddit/X feedback was limited in searchable results at verification time, so GitHub remains the strongest visible feedback channel.