Figloo 0.3.1

Figloo 0.3.1 fixes list_pages, which could return only some of a file's pages on its first call. It is also the first published release since 0.1.0, so it brings the changes of 0.2.0 and 0.3.0: several agent sessions can share the extension, snapshot_layer shows its progress with a Stop button, and Claude Code can install Figloo as a plugin together with the figloo-implement skill.

Upgrading from 0.1.0

• Replace both the extension and the MCP server. The bridge protocol is still 0.2.0, but servers from 0.1.0 cannot hand the extension over to another session, so restart every agent session that still runs one. Reload the extension on chrome://extensions or arc://extensions.
• For Claude Code, you can switch to the plugin, which installs the server and the skill: /plugin marketplace add g761007/figloo, then /plugin install figloo@figloo. Remove a server you registered by hand with claude mcp remove figloo -s user, or both would run in every session.

Files

File	SHA-256
figloo-extension-0.3.1.zip	e359b35f04f6a496360372ed8e288983bb8c91fd77081aa6e44173899e460758
figloo-mcp-0.3.1.mjs	308bd0aaa92cb9c1961bf48440a69b20e21b6192627c1fc09dd1e8b79fa13c20
figloo-mcp-0.3.1.mcpb	f788a8f9cb8c19b72a0e2af1c7752d92980b1d6bd354b529e6a695043c6f107c

Install

1. Unzip figloo-extension-0.3.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.3.1.mcpb from this release:

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

   Without the plugin, keep figloo-mcp-0.3.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.3.1.mjs

3. Pair once: run node figloo-mcp-0.3.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.

The README has the details and troubleshooting.

What's new since 0.1.0

• Several agent sessions can use Figloo, one at a time. One session's server serves the extension and the others stand by. A standby session takes the extension over when one of its tools needs Figma and the serving session has been idle for 10 seconds; while that session is working, the tool returns BUSY with its name. When the serving session exits, a standby one takes over within a few seconds. get_status, the toolbar icon, the popup, and the options page name the session Figloo serves, for example Claude Code · shop (started 09:15).
• While snapshot_layer reads, Figma shows an overlay with the progress and a Stop button. Stop or Esc ends the read and puts the layers panel and the selection back. If the Figma tab goes to the background, the read pauses and continues once the tab is back, instead of failing.
• The figloo-implement skill guides an agent through implementing a Figma page or component: take a snapshot, map the design onto the project's tokens and components, read the details section by section, build, and compare the result with the screenshot. It also covers looking at a design and exporting assets.
• A Claude Code plugin and marketplace install the MCP server and the skill together. The server also ships as an MCP bundle, figloo-mcp-<version>.mcpb.

Fixes

• list_pages waits until Figma's pages list stops changing, up to two seconds, before it answers. Once, its first call returned 8 of a file's 20 pages. The result now includes complete, which is false when the list kept changing or showed signs of pages it had not drawn. Each call takes about 200 ms longer.