Skip to content

01 · What OpenDesign is ​

In one line: OpenDesign takes the coding agent already installed on your machine and wires it into a design workflow that produces web pages, prototypes, decks, dashboards, posters, and video.

It doesn't train models and it doesn't host your work. What it supplies is the middle layer — skills, design systems, the discovery form, a preview sandbox, and an export pipeline. The model and the compute are yours.

The problem it's built for ​

By 2026, the AI design tools all do roughly the same thing: describe intent, get a working interface. The differences are in delivery. Hosted products lock that capability behind three doors:

  • Model lock — one vendor's models, whether or not another one suits your work better.
  • Cloud lock — generation runs on their servers, artifacts live in their store, and so does your client's material.
  • Billing lock — you already pay for a coding agent, and now design wants a second subscription.

OpenDesign's move is to lift the loop — detect intent, pick a skill, generate, preview, export — out of any one product and make it a layer that wraps whatever agent you have. The official framing puts it bluntly: the design loop is a pattern, not a moat.

The three properties that matter ​

Open source, Apache-2.0 ​

The code is at github.com/nexu-io/open-design under Apache-2.0. Fork it, edit the skills, add your own design systems, run the daemon on your own machines. It's maintained by Powerformer, Inc., with discussion on GitHub Issues and Discord.

Local-first ​

Desktop app, daemon, and skill runtime all run on your machine. Artifacts land in your project directory. Only your prompt and skill context go to whichever provider you brought a key for — OpenDesign has no server of its own in that path.

Two groups need this rather than merely like it: anyone doing client work where material can't cross a third party, and anyone working inside a corporate network.

BYOK — your key, your bill ​

Credentials live in .od/media-config.json or your shell environment. API calls go from your machine straight to the provider. Switching providers is a key swap, not a re-onboard.

There's an even lighter path: point it at a CLI you already have logged in (Codex, Claude Code, Cursor, OpenCode). Then no API key is exposed at all, and generation rides the subscription you're already paying for.

Compared with Claude Design ​

The project positions itself as the open-source, local-first Claude Design alternative. The comparison is worth having in front of you:

OpenDesignClaude Design
LicenseApache-2.0, forkableClosed
Where it runsYour machineVendor cloud
Models21 agent adapters, BYOKAnthropic only
ArtifactsFiles in your repoRecords in their store
CostApp free, you pay modelsSubscription
Cost of leavingSkills and systems are Markdown — portableMigration means rebuilding

It isn't a painless swap

The freedom has a price. You install Node 24 yourself, manage keys yourself, and judge output quality yourself — everything the hosted product did for you comes back to your desk. The desktop build erases the install problem; the other two stay.

What it can actually make ​

Not just static pages. The current release covers roughly:

  • Prototypes and web pages — landing pages, SaaS interfaces, mobile screens, dashboards.
  • Slides — HTML decks you can present full-screen, exportable to a genuinely editable PPTX.
  • Images — posters, covers, icons, avatars, including from a hand-drawn sketch.
  • Motion and video — code-driven SVG + CSS animation, plus HTML video through the hyperframes project.
  • Design systems — reverse-extract a DESIGN.md from a screenshot or a Figma export.
  • A desktop pet — yes, really. Nothing to do with output, but it says something about a project that cares how the tool feels.

Version and scale ​

The numbers as of writing (they move — check the site):

Latest stablev0.21.1 (2026-08-31)
Agent adapters21
Plugins479+ (292 templates · 23 skills · 152 systems)
Craft principles12
Contributors409

About the name

OpenDesign, Open Design, open-design, opendesign, Open Design AI, and OD are all the same project. The repo slug is open-design; the product and READMEs write it OpenDesign. Any spelling finds it, but the canonical address is always open-design.ai.

Next ​

02 · Install — three minutes for the desktop build, three commands from source, and where each one bites.

An unofficial community guide · compiled from open-design.ai public material and hands-on notes · the official docs win where they differ