Designers usually accept that leaving Figma means leaving their work behind. But a 7MB open-source desktop app called OpenPencil just fixed the biggest barrier to migration: proprietary file formats. The project started directly out of developer frustration. On February 27, 2026, Figma silently removed a remote debugging flag that automation tools relied on. In direct retaliation that very same day, OpenPencil launched as a local-first application designed specifically to bypass the restricted debugging access.
Unlike competitors like Penpot that rely on clunky SVG exports, OpenPencil reads and writes Figma’s .fig files natively using the exact same Kiwi binary codec. Fills, strokes, text layers, and complex auto-layouts transfer perfectly without any data loss. You just open the file and start working.
The tool also builds an AI assistant straight into the canvas using a “Bring Your Own Key” model. Users can connect their own endpoints from Anthropic, OpenAI, or OpenRouter to generate UI elements. This sidesteps the restrictions of Figma’s credit-capped paid AI features entirely.
The entire application ships as a tiny Tauri desktop app that runs locally across macOS, Windows, and Linux. As of June 2026, the GitHub repository has accumulated over 5,400 stars.
How Headless CLI Support Alters the UI Design Workflow
The most fascinating feature of OpenPencil is its included Model Context Protocol (MCP) server. This addition opens up true “Design-as-Code” capabilities. Instead of clicking through a graphical interface, developers can now use AI coding agents like Claude Code or Cursor to read, write, and natively manipulate proprietary .fig files headlessly via terminal commands.
By removing the need for a GUI entirely, OpenPencil allows external logic engines to interact with visual design systems directly. This functionality directly challenges the core business model of closed-ecosystem platforms like Figma and Plasmic, proving that local, open-source automation can compete with enterprise cloud tools.