Figloo 0.5.0

Figloo now says what a tab cannot do and what to do about it: get_status lists each tab's limitations, tool errors say whether a retry can help, and figloo-mcp doctor checks the setup before an agent session is involved. Update the extension and the MCP server together for all of it; the bridge protocol is still 0.3.0, 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.5.0.zip	41a520666879fc08f08ab02627656fc8e75ccf6e877fa0db481841f0e047c1d6
figloo-mcp-0.5.0.mjs	f6c36ebd1b02ce01228b8eb5e1ad15659c8751946a84eb8c319f1d3e4f7a3fc2
figloo-mcp-0.5.0.mcpb	62c380aa29c6295429a70fd0a8bbb406f5f5529a54325bf291c90901d27f2f74

Install

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

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

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

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

Fixed

• A signed-in page without the right sidebar was reported as a guest session, which has none; now Figloo says it cannot find the sidebar and that Figma may have changed its UI.

Added

• get_status lists each tab's limitations: what Figloo cannot do there, such as in a guest session, with edit access, with a minimized UI, with Figma's screen reader mirror off, or with a non-English UI, the tools that fail or do less, and what the user can do. When the one open file is READY but limited, the hint says so too; before, a missing screen reader mirror went unmentioned.
• Tool errors carry a category and retry advice: yes when the same call can work as it is, after_user once the user did what the hint asks, and no when the agent should do something else first. docs/mcp-tools.md lists both for every error code.
• figloo-mcp doctor checks, without starting a server or taking the port from anyone, Node.js, the config file and its pairing token, and who holds the port: nobody, a Figloo session with its version and whether an extension is connected to it, an older Figloo that cannot hand over, or another program. Each problem comes with its fix, and the command exits with 1 while any is left. docs/agent-install.md has agents run it after installing.
• When the server turns the extension away, get_status names both versions and which side to update, or asks to pair again when the token does not match. The extension's options page keeps the server's explanation instead of a bare close code.
• The extension checks the parts of Figma's page it depends on from one list, each marked by how stable its selector is, and reports the ones it did not find in get_status and the popup's Diagnostics. A signed-in tab without the right sidebar or the properties panel gets a UI_CHANGED limitation.
• A signed-in canary, pnpm test:canary, checks on real Figma what a guest cannot reach: the selection, the inspection panel, snapshots, exports, and putting the view back. It runs on the maintainer's machine with a browser profile signed in to a dedicated test account that only views the test file, and tests/canary/login.mjs opens that profile for signing in by hand.