Skip to content

Figloo 0.4.2

Choose a tag to compare

View all tags
@github-actions github-actions released this 07 Oct 02:20
· 19 commits to main since this release
v0.4.2
198ad01

The fix is in the extension, so load the new one after updating. The bridge protocol is still 0.3.0, so the extension also works with the 0.4.1 MCP server.

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.2.zip 86db5b96b61a8b02c7569184091eb8ddd218ae047542f3bde7ccc60c0e34dbd1
figloo-mcp-0.4.2.mjs 21de0efeb7b841f5a9530710880c752c7d3dd815be9c9e1f2c999da71ba94bee
figloo-mcp-0.4.2.mcpb 276230cd2f567792a71091fe54f3df6e87045a7c66e9576331196fe18af2b23d

Install

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

  • A GitHub Actions workflow runs the integration tests every day against a public Figma file as a guest, to notice changes in Figma's web UI before users run into them.
  • SECURITY.md describes the local bridge, the extension's permissions, the data Figloo keeps and where design content goes, and how to report a vulnerability. ROADMAP.md lists what comes next.

Changed

  • The README starts with what Figloo is for and how it works. Installation and troubleshooting moved to docs/installation.md and docs/troubleshooting.md, each also in Traditional Chinese.

Fixed

  • For a frame with layers that stay put while it scrolls, Figma's layers panel lists its children under "Fixed" and "Scrolls" header rows. Figloo stopped at the first header: get_neighbors returned no children, siblings, or ancestors for the layers of such a frame, only hasMore: true and a cursor, and snapshot_layer could not read it. Header rows are now passed over, and since they are shorter than layer rows, the rows of the panel are counted and scrolled to from where Figma draws them. The daily canary found this, and the integration tests now fail when a read stops early instead of passing with fewer layers.
Assets 5
Loading