Figma MCP opens link in agent window browser - misleading next step

[jo-oikawa]

Expected:

1. I connect/start the Figma MCP server in VS Code
2. I send a chat in the Agent Window referencing a frame or page in Figma with a link
3. The Figma MCP uses that link to reference the right assets associated with my request

Actual:
3. Agent window first opens the link itself in the integrated browser, which prompts me to sign into Figma to access. Meanwhile, the Figma MCP is working on the query as expected.

While the 'fix' is to just ignore the integrated browser, users see a big sign in page pop up and assume this is the next step. Signing in via the integrated browser can be difficult, and even when successful this doesn't 'fix' anything else.

Here's an example of copying the link from Figma to reference:

[connor4312]

Can you take a quick recording? I'm not sure I fully understand your workflow / where the agent window open trigger kicks in

/gifPlease

[vs-code-engineering]

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.

If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.

Happy coding!