Share Your Thoughts

i can not connect to the figma remote mcp server via antigravity cli.i get an error: OAuth app with client id WPj[xxxxxxxxxxx]sit7 doesn't exist.The internet suggests that the Antigravity CLI is not whitelisted as a tool. Can you confirm?If possible, please whitelist it. Gemini cli support will end in 3 days and my workflow will be broken.

There are times when having sections free of constraints is nice… but my design team has become addicted to using auto layout with frames. In many cases when using sections, it would be amazing to perfectly space the inner sections out using auto layout.

I would love the ability to set a background color in the layer list. I’d like to be able to set this on an individual layer or group of layers. I often have trouble finding important groups of layers. I’ve resorted to using emojis which helps. But imagine that we could color the background color of the label. I’d also like to edit the label name so that in my document “Blue” would represent to my developers that it’s grids.

Add the ability to add text-wrap: pretty and text-wrap: balance so that more options are available to ensure more flexibility to how text can flow/reflow and reducing hyphenations and word orphans.

With "Text-wrap: balance" headlines could be made more readable and visually appealing.Here’s how it could look: 

When marking a comment as resolved, we are now automatically moved to the next one. I’m wondering if or how we can disable this behaviour?My work flow being to go from screen to screen of user flows, and not comments to comments, this is very disrupting as it can bring me anywhere in the file, and I need to find and navigate back to where I was. I understand this might be useful for reviewers that only goes through questions left by other people, but this probably not most users, so it would be useful to have the ability to disable this feature.

The branch review window is large but not resizable. When comparing two-up web/desktop screens, it’s hard to see all the details. I know you can zoom or use the overlay mode, but I have a 27" monitor and plenty of room I just want to make the window larger so the two previews will scale.

In Korea, web development projects are typically divided into three distinct roles: Designers, Publishers (UI/UIX Developers), and Developers. Publishers implementation the design into code based on the Figma files, but they usually only have "Viewer" or limited editing permissions.The Problem:In typical Korean web projects, a single Figma page often contains dozens of frames representing all the individual web pages within a specific category. When multiple publishers collaborate on such a massive page, it is extremely difficult to track the progress of each frame/screen. Right now, there is no native, at-a-glance way to see who is working on what, or which specific frames are completed.The Suggestion:I would love to see a Page Status Label feature that helps teams manage this workflow efficiently:Status Indicators: Provide visual labels on the page list (e.g., "In Progress", "Done") so that publishers can self-report their progress. Smart Update Notification: If a publisher marks a p

Feature idea:Add keyboard shortcuts for any of these buttons at the top. This will increase user efficiency when iterating on prototypes.→ Quickly copy designs→ Quickly enter/leave annotation mode→ Quickly enter commentsetc.  

the problem i need as much real state as possible to view the designs and screens am working in a readable viewable way, if the makes sense. to come around this, i currently scroll around and zoom in and out, or hide and show the panels, most probably its a mix of both. either way it’s a annoying… or i need to buy another real big monitor, but i already have a 15" macbook pro, which is great and enough when i hide the panels. this might be a big problem for laptop users without a secondary big screen, or who are portable and don’t have a dedicated work space. this is specially evident when they need to widen the left panel in order to view and read the layers tree. (which is another issue maybe raised in another topic) suggestion make side panels modular (photoshop/illustrator kind of thing). assets, layers on the left panels can be separable and can be undocked and moved elsewhere separately. design, prototype, inspection on the right panel are also separable and can be undocked and m

使用Agent频繁遇到无法访问PingFangSC字体的限制，希望可以解决 

Currently, you are able to use the ctrl+B command on a text style to apply the bold font weight to a desired string of text without breaking the text style. However, if you want to apply other font weights like light, medium, semibold, or black, you must either create a entirely new text style (which can add up quite quickly) or detach the text style and manually change the weight. A way to apply various font weights without breaking the style (in the same vein as applying different styling like bold, underline, and italic) would be extremely helpful in increasing a design system’s adoption and flexibility.

If I move a configuration of shapes and words, and then realize it’s not what I want, I can’t undo and go back to how I had it set up. Add as much context as possible (screenshots, Figma files, mockups, etc.)

I’ve noticed a usability issue in Figma around discovering updates/published files . Currently it’s difficult to tell whether anything has been updated or need to be published. There’s no immediate visual indication in the left panel, and users must actively open the Assets panel to check if updates are available.This makes updates easy to miss and adds unnecessary friction.Suggested improvement:Introduce a small notification indicator (e.g. a dot or badge) on the relevant menu item. This would give users an at-a-glance signal that something has changed and needs attention, without requiring extra clicks or manual checking. Thank you!

Realized when going back to a Tool that I subscribed to that there’s no way for me to pin it or save it anywhere for quick access. The only mechanism seems to be Recents. Seems like a total miss here. Way too many tools to assume Recents would be suffice.

Been testing out the Figma Agent using component library and have found it struggles to use nested component properties. While guidance for agents talks about buildng reusable blocks, it seems like this doesn’t work well with page-level compositions we use. There are page pattern components the agent fails to use nest components within. Here’s how it explains its failures - These are 2 of 3 patterns of failures agent was having building pages trying to use a page component and other compositional components. Pattern 2 — Complex nested prop objects on layout components (7 "Required dependency not found" failures)Higher-order layout components like Layout/Record page, Page header, and Tabs expanded failed with "Required dependency not found." These components have deeply nested prop structures:Page header: 8 props including boolean toggles (has Avatar, has Detail, has Actions), variant selectors (Breakpoint, layout), and nested sub-instances (Avatar, Labels, Header actions, Page header d

You just added 1 to 2 clicks to a feature that worked perfectly fine and only required one click.As a power user that needs to quickly select a hex value or change it you just added the equivalent of hundreds more clicks a day to my work load. I know I probably sound pathetic but I’m having a hard time justifying the changes to what I thought was a functionality that was as simple as efficient. Why add complexity to simplicity??Am I the only one complaining about this? 

Hi Figma Team,Thanks for the amazing work on the new Motion mode! It is a great update to the platform.I wanted to share a small feature idea that would improve the workflow. Right now, when creating returning or looping animations (like a button scale up and down), it takes some manual work to flip the keyframes and invert the Bezier curves.It would be awesome if we could select keyframes, copy them, and then paste them in reverse order using a shortcut (like Ctrl + Shift + V) or via a right-click menu option.Thanks for considering this, and keep up the great work!

Scale is one of my most used properties when designing interactions and states. It would be great if we had true ‘scale’ as a property. No, I’m not talking about the scale tool. That’s fake scale that affects the width/height of elements. I want the ability to enter something like ‘1.5’ and change the scale of an element, respectively.

I have a recurring use case: I want to create a gradient that fades to zero opacity while using styles or color variables. Unfortunately, this isn’t possible in Figma. I can only adjust the opacity if I break the variable/style binding. Why is that?

Used Figma Motion Beta. The key frame doesn’t work for gradients (The position and opacity og gradient points).

We're on a Figma Organization plan, on an annual contract. Recently our team started getting logged out, and now only two people can be logged in at the same time. This didn't happen before, and we haven't changed anything on our end.We asked our Account Manager what happened, and they told us: "we haven't historically enforced the Acceptable Use Policy with the same rigor we're applying now." In other words, the rules didn't change - Figma just decided to start enforcing them harder, partway through our contract, without telling us in advance.This is concerning. We allocated budget for this agreement based on the assumption that the terms and level of service would stay stable for the length of the contract. If Figma can quietly tighten enforcement whenever it wants, with no notice, then the terms we agreed to don't really mean much - Figma can change how the contract works in practice without ever changing the contract itself. That's a real imbalance of power between Figma and its cu

Hi Figma Team,I work extensively with interactions when building prototypes—sometimes having up to 50 different interactions on a single element. Once I have finished setting all of them up, if I realize I need to add another condition or check, I either have to edit each one individually or, if I'm lucky and they all share the exact same conditions, I can select them all at once to update them.To make maintaining interactions more flexible and convenient in general, a JSON import and export feature would be a massive help. It would allow users to build conditions exactly as needed, export them, and then easily apply them to a completely new element, or quickly insert a new query/condition across all existing ones.Best regards and thank you in advance,Reke Buchenau

Our Foundations file is published as a library, consumed by other design files and by developers via the Variables REST API. We need to test changes — including adding/removing variables, not just editing values — without those changes reaching devs or other files until we're ready.Current gaps:Branches can't be referenced as a library from another file, so we can't test a branched foundations file in a separate screens file. Extended Collections only allow overriding existing values, not adding/removing variables. Our only workaround is manually duplicating the whole file into a "sandbox" library and re-syncing it by hand whenever production changes — error-prone, with no diffing.Ask: A way to stage variable changes (ideally via branching) and reference that staged version as a library in a separate file for testing, while production and the REST API stay untouched until we merge and publish. A diff view between staged and production would also help avoid drift.

Figma Slides are missing basic embeds.YouTube videos are the only supported format, where pasting a link converts it to a playable video.If Figma Slides wants to win students, teachers, and everyday use caes then it needs to support the biggest platforms we as Gen Z use:TikTok Instagram XThis is extremely easy support to add! If you want I’ll vibe code it for you tonight! Gamma will win without this.