Skip to content

Figloo 0.4.3

Choose a tag to compare

@github-actions github-actions released this 07 Oct 02:48
· 17 commits to main since this release

Update the extension and the MCP server together: the extension finds what it cannot read, and the server reports it. The bridge protocol is still 0.3.0 and the new fields are optional, so an older half keeps working without the new reports.

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.3.zip 4bae3df383a9e50c7a4abbf8394c8389e453300679df98fc4ba86858ebe5c3bf
figloo-mcp-0.4.3.mjs ce933c6420f6ae8440158decfd05e01ad958e818954ad93f55b48393bf0d6c00
figloo-mcp-0.4.3.mcpb 05370dd07f77f4e602fd71847aca583647c78e8cd30dc70a3d669992a1c6266a

Install

  1. Unzip figloo-extension-0.4.3.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.3.mcpb from this release:
    /plugin marketplace add g761007/figloo
    /plugin install figloo@figloo
    
    Without the plugin, keep figloo-mcp-0.4.3.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.3.mjs
  3. Pair once: run node figloo-mcp-0.4.3.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 docs/troubleshooting.md the common problems.

Changes

Added

  • get_status reports access: "edit" for a file opened with edit access, which Figloo tells by the Design and Prototype tabs Figma shows in the right sidebar in place of Properties. Such a tab is DEGRADED, and its detail says that properties, snapshots, and exports do not work there while layers and screenshots do.
  • A section of the inspection panel that shows values Figloo cannot read, as after Figma changes its markup, comes with unreadable: true in inspect_nodes, snapshot_layer, and query_snapshot. Snapshot outlines mark such layers [unreadable: …], and snapshot_layer and summarize_snapshot count them in unreadableLayers.

Fixed

  • With edit access, inspect_nodes, snapshot_layer, export_asset, and export_assets waited for an inspection panel Figma does not show there: a snapshot took about 1.5 seconds per layer and saved every layer without properties or export settings. They now fail at once with UI_NOT_READY and say why.
  • When the export section shows settings Figloo cannot read, as after Figma's change between 0.4.0 and 0.4.1, export_asset stops before it changes anything, instead of adding a setting it could not take out again, and snapshot_layer saves the layer's export settings as unreadable instead of as none. A snapshot whose root shows no section Figloo can read fails instead of saving layers without properties.