* fix(vue): update instance text properties while typing Instance text property edits only reached the canvas on Enter or blur, so the canvas and layer tree lagged behind the field. Emit model updates as the text changes, commit on blur or Enter, and route bursts through the existing interactive-edit lease and undo batch so rapid edits collapse into one transaction. * fix(vue): present the canvas in sRGB to keep P3 blends correct CanvasKit 0.41 wraps sRGB on-screen surfaces as RGBA8 but every other color space as RGBA16F, while browser drawing buffers stay RGBA8 when their color space changes. Requesting DISPLAY_P3 therefore produced invalid destination copies and broken blends: black rectangles and brown Overlay fills over Display-P3 documents. Keep presentation in sRGB and read the buffer back rather than trusting the setter, leaving the document color space and its stored colors untouched. * perf(fig): encode glyph path commands without per-coordinate allocation Glyph outline encoding allocated an ArrayBuffer, DataView, and Uint8Array for every coordinate and spread each byte into a number array, so recovery snapshots and text-heavy exports blocked the main thread for 159-167ms. Size the output once and write through a single DataView; encoded bytes are unchanged. * refactor(vue): separate component property edit resolution from batching The live text path had grown a boolean flag through a single applyValue that resolved the edit, chose the batch, and mutated instances, which made the two entry points differ only by that flag. Resolve an edit once, keep a named batch key, and let setValue and setTextValue state their own batching policy. Watch the page and selection sources directly now that selection is replaced by identity, drop the redundant scene dependencies the useSceneComputed wrapper already tracks, move the variant option projection next to the swap projection, and resolve the swap candidate list once per controls pass instead of once per control. * feat(vue): restore wide-gamut P3 presentation where the renderer supports it CanvasKit wraps sRGB on-screen surfaces as RGBA_8888 and every other color space as RGBA_F16, with the pixel format deliberately not exposed, so a Display-P3 surface only matches the browser buffer when that buffer is floating point. Chromium 122+ provides drawingBufferStorage for that; this negotiates the pairing, keeps the sRGB fallback everywhere else, and warns with the existing dismissible banner when a Display-P3 document cannot be presented in wide gamut. Software rasterizers advertise the float extensions but fail an offscreen framebuffer attach on the first content frame, so they stay on sRGB, as do WebKit and Firefox, which have no drawingBufferStorage. A new document:color-space-changed event recreates the surface when a P3 document arrives after mount, which previously kept whatever surface the first document created. * refactor(web): report the canvas presentation instead of re-deriving it The wide-gamut notice decided availability from a capability probe, which can disagree with the surface: configurePresentation also falls back when the float storage install is rejected or the color space setter is ignored. Pass the surface's actual result through a new onPresentation option, mirror the document color space into app state, and let the notice read both, so it appears exactly when a Display-P3 document is really presented in sRGB. That also removes two editor-event subscriptions and a tab watcher. Rename SafariBanner to FileApiBanner, since the condition is the File System Access API rather than Safari, and move the availability check and picker call into one capability module instead of repeating them at each save site. * refactor(web): point capability notices at one neutral support reference The file API notice linked "Use Chrome" to a Chrome download page while naming Edge as inert text, and the wide-gamut notice offered no browser guidance at all. Both now link to the caniuse support table for the API that decides the capability, so the advice is vendor-neutral and stays correct as versions move. External link behavior moves into one primitive: SettingsLink and both notices share it, gaining rel="noopener noreferrer" and the desktop opener path, which the notices need because the wide-gamut notice also renders in Tauri where a raw anchor cannot open an external page. * fix(fig): stop failing .fig export on unencodable OpenType feature tags The Kiwi schema types toggledOn/OffOTFeatures as its OpenTypeFeature enum, which has no PNUM, TNUM, LNUM, ONUM, FRAC, SMCP, C2SC, SUPS, or SUBS member. Features that map to a typed axis were only written when enabled, so a disabled one fell through to a raw tag, and encoding then rejected it: `Invalid value "PNUM" for enum "OpenTypeFeature"`. Because save and recovery snapshots share that export path, any text using those features could not be written to a `.fig` file at all — the demo's own typography comparison hit it in every run. Disabled mapped tags now clear their axis to the schema's neutral NORMAL value, an enabled tag on the same axis wins over a disabled sibling so "TNUM on, PNUM off" still means tabular figures, and tags with no Kiwi representation are dropped instead of poisoning the whole export. * perf(core): recompute layout only for the pages a component edit affects Editing a component recomputed layout for the entire graph, which cost tens of milliseconds per edit in documents with several populated pages. Layout now runs once per affected page: the pages of the edited subtrees, their components, and every instance of those components, which may live on another page. The layout function is injected so the scoping contract is testable, and the existing behaviour is kept when no page can be resolved. * feat(core): follow the document colour profile when painting Numbers in a document are coordinates in the profile that document declares, so painting into a surface with a different profile has to convert them. Nothing did: stored values were handed to the GPU as-is, which is why a Display-P3 document looked more saturated on a wide-gamut display than on an sRGB one, and why export labels and stored values disagreed. Rendering now resolves each colour from the document's profile into the surface's profile, reporting clipping when a wider profile does not fit, and OKHCL colours resolve into the requested target instead of being baked to sRGB. New documents also default to sRGB, matching Figma, so Display P3 is reserved for documents that declare it rather than being assumed for everything OpenPencil creates. * test(canvas): exercise the P3 spec on the paint page The P3 rendering spec used the demo's reference page and the shared `selectDemoReferencePage` helper. The paint page covers the same ground — gradients, shadows, blurs, multiply and screen blends, an alpha mask — and the helper is going away with the reference page, so this keeps the spec independent of that demo content. The card specs now follow whichever page owns the card instead of switching by page name, which works for either demo layout. |
||
|---|---|---|
| .claude | ||
| .devcontainer | ||
| .github | ||
| .storybook | ||
| .vscode | ||
| assets/brand | ||
| desktop | ||
| lint | ||
| packages | ||
| public | ||
| scripts | ||
| skills/open-pencil | ||
| src | ||
| tests | ||
| tools | ||
| vite | ||
| .coderabbit.yaml | ||
| .gitattributes | ||
| .gitignore | ||
| .gitleaks.toml | ||
| .lfsconfig | ||
| .oxfmtrc.json | ||
| AGENTS.md | ||
| bun.lock | ||
| bunfig.toml | ||
| CHANGELOG.md | ||
| commitlint.config.ts | ||
| CONTRIBUTING.md | ||
| index.html | ||
| knip.json | ||
| LICENSE | ||
| oxlint.json | ||
| package.json | ||
| playwright.config.ts | ||
| portless.json | ||
| README.md | ||
| SECURITY.md | ||
| steiger.config.ts | ||
| tsconfig.json | ||
| tsconfig.node.json | ||
| vite.config.ts | ||
| wdio.conf.ts | ||
OpenPencil
Open-source design editor. Opens .fig and .pen design files, includes built-in AI, and ships as a programmable toolkit with a headless Vue SDK for building custom editors.
Status: Active development. Usable today, with some rough edges as features evolve.
Try it online → · Download · Documentation · Roadmap · llms.txt
Installation
macOS (Homebrew):
brew install --cask openpencil
Or download from the releases page, or use the web app — no install needed.
What it does
- Opens
.figand.penfiles — read and write native Figma files, open supported Pencil documents from the app or OS file browser, copy & paste nodes between apps - AI builds designs — describe what you want in chat, 90+ tools create and modify nodes. Connect OpenRouter, Anthropic, OpenAI, Google AI, Z.ai, MiniMax, or compatible endpoints
- Fully programmable — headless CLI, XPath queries, Figma Plugin API via
eval, MCP server for AI agents, and desktop agent integrations for Claude Code, Codex, and Gemini CLI - Lint, convert, and extract tokens — inspect documents, lint naming/layout/accessibility, convert between supported formats, analyze colors/typography/spacing/clusters, and extract design tokens
- Components and variants — create reusable components, group variants into component sets, insert local assets as instances, and switch variants from the inspector
- Image vectorization — convert image layers into editable vector layers with Recraft or fal.ai
- Design-to-code export — export selections as JSX/Tailwind, generate token outputs, and map designs into component-oriented code workflows
- Vue SDK for custom editors — headless components and composables for embedding OpenPencil into other apps or building workflow-specific editing surfaces. Read the SDK docs →
- Real-time collaboration — P2P via WebRTC, no server, no account. Cursors, presence, follow mode
- Auto layout & CSS Grid — flex and grid layout via Yoga WASM, with gap, padding, alignment, track sizing
- ~7 MB desktop app — Tauri v2 for macOS, Windows, Linux. Also runs in the browser as a PWA
CLI
npm install -g @open-pencil/cli
# or: bun add -g @open-pencil/cli
Inspect design files
Browse node trees, search by name or type, dig into properties — all without opening the editor:
openpencil tree design.fig
openpencil find design.pen --type TEXT
openpencil node design.fig --id 1:23
openpencil info design.fig
[0] [page] "Getting started" (0:46566)
[0] [section] "" (0:46567)
[0] [frame] "Body" (0:46568)
[0] [frame] "Introduction" (0:46569)
[0] [frame] "Introduction Card" (0:46570)
[0] [frame] "Guidance" (0:46571)
Query with XPath
Use XPath selectors to find nodes by type, attributes, and structure:
openpencil query design.fig "//FRAME" # All frames
openpencil query design.fig "//FRAME[@width < 300]" # Frames under 300px
openpencil query design.fig "//TEXT[contains(@name, 'Button')]" # Text with 'Button' in name
openpencil query design.fig "//*[@cornerRadius > 0]" # Rounded corners
openpencil query design.fig "//SECTION//TEXT" # Text inside sections
Export
Render to PNG, JPG, WEBP, SVG, .fig, or JSX — or export selections/pages as .fig and convert whole documents between supported formats:
openpencil export design.fig # PNG
openpencil export design.fig -f jpg -s 2 -q 90 # JPG at 2x, quality 90
openpencil export design.fig -f fig --page "Page 1" # Export a page as .fig
openpencil export design.fig -f jsx --style tailwind # Tailwind JSX
openpencil export design.fig -f html --css tailwind # Tailwind HTML fragment
openpencil export design.fig -f html --html standalone --assets external # HTML + assets
openpencil convert design.pen output.fig # Convert between document formats
openpencil import page.html --css styles.css -o page.fig # HTML/CSS → editable .fig
DOM/CSS input flows through @open-pencil/dom-css, so HTML, authored CSS, and Tailwind utility CSS can become editable OpenPencil layers:
openpencil import card.html --css card.css -o card.fig
openpencil import card.html --tailwind "flex flex-col gap-3 w-80 p-6 rounded-xl bg-white" -o card.fig
<div className="flex flex-col gap-4 p-6 bg-white rounded-xl">
<p className="text-2xl font-bold text-[#1D1B20]">Card Title</p>
<p className="text-sm text-[#49454F]">Description text</p>
</div>
Lint design files
Catch naming, layout, structure, and accessibility issues from the terminal:
openpencil lint design.fig
openpencil lint design.pen --preset strict
openpencil lint design.fig --rule color-contrast
openpencil lint design.fig --list-rules
Analyze and extract design tokens
Audit an entire design system from the terminal — find inconsistencies, extract the real palette, and spot components waiting to be extracted:
openpencil analyze colors design.fig
openpencil analyze typography design.fig
openpencil analyze spacing design.fig
openpencil analyze clusters design.fig
openpencil analyze overlaps design.fig
openpencil variables design.fig
#1d1b20 ██████████████████████████████ 17155×
#49454f ██████████████████████████████ 9814×
#ffffff ██████████████████████████████ 8620×
#6750a4 ██████████████████████████████ 3967×
3771× frame "container" (100% match)
size: 40×40, structure: Frame > [Frame]
2982× instance "Checkboxes" (100% match)
size: 48×48, structure: Instance > [Frame]
Script with Figma Plugin API
eval gives you the full Figma Plugin API. Modify the file, write it back:
openpencil eval design.fig -c "figma.currentPage.children.length"
openpencil eval design.fig -c "figma.currentPage.selection.forEach(n => n.opacity = 0.5)" -w
Control the running app
When the desktop app is running, omit the file argument — the CLI connects via RPC and operates on the live canvas. Useful for automation scripts, CI pipelines, or AI agents that need to interact with the editor:
openpencil tree # Inspect the live document
openpencil export -f png # Screenshot the current canvas
openpencil eval -c "figma.currentPage.name" # Query the editor
All commands support --json for machine-readable output.
AI & MCP
Built-in chat
Press ⌘J to open the AI assistant. It has 100+ tools that can create shapes, set fills and strokes, manage auto-layout, work with components and variables, run boolean operations, analyze design tokens, and export assets. Bring your own API key for OpenRouter, Anthropic, OpenAI, Google AI, Z.ai, MiniMax, or compatible endpoints. No backend, no account.
Not every provider works in the browser, and not every model streams tool calls correctly. See BYOK provider & model compatibility for measured results — contributions welcome.
Coding agents (desktop)
Use Claude Code, Codex, or Gemini CLI directly in the chat panel. The agent connects to the editor's MCP server and uses all 100+ design tools. Requires the desktop app and the agent CLI installed locally.
Pi is also available as an optional AI SDK Harness provider. Install its companion CLI with npm install -g @open-pencil/harness, then add a Pi model profile in Settings → AI & agents. The companion is installed separately so OpenPencil does not bundle a JavaScript runtime for users who do not enable Harness providers.
Setup (Claude Code):
- Install the ACP adapter:
npm install -g @agentclientprotocol/claude-agent-acp - Add MCP permission to
~/.claude/settings.json:{ "permissions": { "allow": ["mcp__open-pencil__*"] } } - Open the desktop app → CtrlJ → select Claude Code from the provider dropdown
MCP server
Connect Claude Code, Cursor, Windsurf, or any MCP client to inspect, modify, and export design documents headlessly. 100+ tools. Full docs →
Stdio (Claude Code, Cursor, Windsurf):
npm install -g @open-pencil/mcp
claude mcp add --scope user open-pencil -- openpencil-mcp
For other MCP clients:
{
"mcpServers": {
"open-pencil": {
"command": "openpencil-mcp"
}
}
}
HTTP (scripts, CI):
openpencil-mcp-http # Unix socket on macOS/Linux + http://127.0.0.1:7600/mcp
Local clients discover the private Unix socket automatically and fall back to localhost TCP. Set PORT=0 to disable TCP on macOS/Linux.
File access: Set OPENPENCIL_MCP_ROOT to scope file operations (open_file, new_document, export path param) to a directory. Defaults to the current working directory.
AI agent skill
Teach your AI coding agent to use OpenPencil — inspect designs, export assets, analyze tokens, modify .fig files:
npx skills add open-pencil/open-pencil
Works with Claude Code, Cursor, Windsurf, Codex, and any agent that supports skills.
For documentation-aware agents, the docs site publishes llms.txt, llms-full.txt, and per-page Markdown files generated from the VitePress docs.
Collaboration
Share a link to co-edit in real time. No server, no account — peers connect directly via WebRTC.
- Click the share button in the top-right panel
- Share the generated link (
app.openpencil.dev/share/<room-id>) - Collaborators see your cursor, selection, and edits in real time
- Click a peer's avatar to follow their viewport
Why
Figma is a closed platform that actively fights programmatic access. Their MCP server is read-only. figma-use added full read/write automation via CDP — then Figma 126 killed CDP. Your design files are in a proprietary binary format that only their software can fully read. Your workflows break when they decide to ship a point release.
OpenPencil is the alternative: open source (MIT), reads .fig files natively, every operation is scriptable, and your data never leaves your machine.
See the roadmap for product direction and current Figma compatibility gaps.
Contributing
Setup
bun install
bun run dev:portless # Web editor at https://open-pencil.localhost
bun run dev # Direct Vite server at http://localhost:1420
bun run tauri dev # Desktop app (requires Rust)
The first Portless run creates and trusts a local HTTPS certificate. Linked Git worktrees automatically receive branch-prefixed URLs such as https://fix-ui.open-pencil.localhost, so concurrent development servers do not compete for port 1420. Their development MCP bridges are exposed through matching sibling URLs such as https://fix-ui.mcp.open-pencil.localhost, with isolated TCP ports and runtime socket files. Run bunx portless doctor if local routing or certificate trust fails.
Alternatively, open the repository in any Dev Container-compatible tool. The container pins Bun, installs the workspace dependencies, and forwards the direct web editor on port 1420. Start it with bun run dev after the container is ready.
The Dev Container supports the web editor, packages, CLI, and automated checks. Native Tauri development still requires the host setup described below because desktop windows and platform WebView dependencies are not provided in the container.
Quality gates
| Command | Description |
|---|---|
bun run check |
Lint + typecheck |
bun run test |
E2E visual regression |
bun run test:unit |
Unit tests |
bun run format |
Code formatting |
Project structure
packages/
scene-graph/ @open-pencil/scene-graph — nodes, primitives, hit testing, copy/snap/undo
pen/ @open-pencil/pen — Pencil document format helpers
kiwi/ @open-pencil/kiwi — Kiwi runtime and low-level .fig container parsing
fig/ @open-pencil/fig — .fig archives, SceneGraph conversion, instances, metadata
core/ @open-pencil/core — editor engine, renderer, layout, tools, RPC, document I/O
dom-css/ @open-pencil/dom-css — HTML/CSS/Tailwind to editable design documents
vue/ @open-pencil/vue — headless Vue SDK
cli/ @open-pencil/cli — headless CLI
mcp/ @open-pencil/mcp — MCP server (stdio + HTTP)
docs/ Documentation site (openpencil.dev)
src/ Vue app (editor shell, AI, collaboration, document I/O)
desktop/ Tauri v2 desktop app (Rust + config)
tests/ E2E, visual, engine, and integration tests
Tech stack
| Layer | Tech |
|---|---|
| Rendering | Skia (CanvasKit WASM) |
| Layout | Yoga WASM (flex + grid via fork) |
| UI | Vue 3, Reka UI, Tailwind CSS 4 |
| File format | Kiwi binary + Zstd + ZIP |
| Collaboration | Trystero (WebRTC P2P) + Yjs (CRDT) |
| Desktop | Tauri v2 |
| AI/MCP | Multi-provider (Anthropic, OpenAI, Google AI, OpenRouter), MCP SDK, Hono |
Desktop builds
Requires Rust and platform-specific prerequisites (Tauri v2 guide).
bun run tauri build
Acknowledgments
Thanks to @sld0Ant (Anton Soldatov) for creating and maintaining the documentation site.
License
OpenPencil is licensed under the MIT License.
Copyright (c) 2026 Danila Poyarkov and OpenPencil contributors.
