Figloo 0.4.1

Upgrading

• Replace the extension with the new zip and press the reload button on its card in chrome://extensions or arc://extensions.
• Update the Claude Code plugin, or the .mjs file you registered, then start new agent sessions so they run the new server.
• The extension and the MCP server speak bridge protocol 0.3.0. A pair that speaks different versions does not connect, and get_status reports PROTOCOL_MISMATCH.

Files

File	SHA-256
figloo-extension-0.4.1.zip	04aade5bcd7c177f9c9798ed7e689290245336b403f78cf3dbe49704a28853ba
figloo-mcp-0.4.1.mjs	fb49e4376d06442a74f127f28cca5f018c20675141ad786b2372129da76c89c4
figloo-mcp-0.4.1.mcpb	1869c16dd4018bb7df5133f3f12a2057cf0c6f5d84c1aa01fd289fa9738994f3

Install

1. Unzip figloo-extension-0.4.1.zip into a folder you keep. On chrome://extensions or arc://extensions, turn on Developer mode, click "Load unpacked", and select that folder.
2. Register the MCP server. In Claude Code, install the plugin, which downloads figloo-mcp-0.4.1.mcpb from this release:

   /plugin marketplace add g761007/figloo
   /plugin install figloo@figloo
   

   Without the plugin, keep figloo-mcp-0.4.1.mjs anywhere (it needs only Node.js 24), register it, then start a new session:

   claude mcp add -s user figloo -- node /absolute/path/to/figloo-mcp-0.4.1.mjs

3. Pair once: run node figloo-mcp-0.4.1.mjs pair and paste the token and port into the extension's options page. The plugin's server reads the same ~/.figloo/config.json, so this works for the plugin too.
4. In Figma, sign in (view access is enough), use the English UI, keep the UI expanded, and turn on "Adapt content for screen readers" under Main menu, Preferences, Accessibility settings. Keep the Figma tab on screen while the agent works.

Or let your agent do it: the README's Quickstart has one sentence to paste into Claude Code or Codex, which installs Figloo by following docs/agent-install.md and walks you through the steps only you can do.

The README has the details and troubleshooting.

Changes

Fixed

• export_asset and export_assets failed every time with UI_NOT_READY: Figma did not add an export setting after Figma replaced the file type control of export settings with a new select. Each failed call left a PNG setting behind in the tab, and a layer's own settings were ignored, so a call without format exported SVG. snapshot_layer reported no export settings for any layer, so retake snapshots made since then. Figloo now reads both the new select and the old control, names Figma's JPEG JPG as the tools do, and says so when Figma added a setting that Figloo cannot read instead of reporting that Figma added none.
• export_asset with format and scale returned two files when the layer's own settings use that format at another scale, such as the designer's PNG 1x next to a requested PNG 3x, and a saveTo file name then failed with EEXIST because it was taken for a folder. For PNG and JPG only the file at the requested scale comes back now, told apart by its size since Figma names the extra file inconsistently, such as -1 or @3x. When several files still come back, a saveTo with a file extension is refused before anything is written and the message lists the files; a folder ending with / saves them all. export_assets keeps the requested scale the same way. Keeping one scale needs the extension and the MCP server of this release together; the saveTo check needs only the server.