Skip to main content
Question

Unable to use point and edit in Make

  • March 31, 2026
  • 6 replies
  • 95 views
Paul Wagner

I’m not sure if this is a bug or just the current logic for Make, but I wanted to flag an issue with how the interface handles credit limits.

Currently, once a user runs out of AI credits, the entire prompt box is disabled—including the Point and Edit option. While I understand the need to gate AI-generated features, Point and Edit allows for manual changes that don’t actually cost credits. By locking the whole box, users lose access to manual text editing and the ability to jump directly to specific code views.

The Request: If this isn't a bug, could we treat this as a feature request? It would be great if the Point and Edit mode remained active even after credits are exhausted. This would allow users to continue making manual updates and navigating the code without being completely locked out of the workflow.

6 replies

Gayani_S
Figmate
  • Gayani_S
  • Community Support
  • April 1, 2026

Hey ​@Paul Wagner, thanks for reaching out! I understand that blocking the entire prompt box, especially the Point and Edit option disturbs your workflow.

I checked with the team, and this is currently expected behaviour. That said, your suggestion makes a lot of sense, and you’re not alone in this feedback. I’ve added your post to our internal tracking so it’s captured as a feature request.

It would be really useful to understand your specific use case a bit more. For example, which actions you’re trying to take within Point and Edit after hitting the credit limit.

 

Thank you for flagging this! 

Paul Wagner
  • Paul Wagner
  • Author
  • New Member
  • April 2, 2026

What I would expect to be able to do with point and edit even when I no longer had credits left would basically be the options allowed under the point and select’s Edit properties toolbar

  1. Manually edit text or it’s style
  2. Modify it’s margin or padding
  3. Delete a selection
  4. Select something and choose go to source where I am then taken to where that object lies in the code view

Hopefully that is helpful. I plan to make more of my edits this way even when I have available tokens now that it is a limited resource. But if I run out I would expect to still be able to make manual edits of this nature.

Gayani_S
Figmate
  • Gayani_S
  • Community Support
  • April 8, 2026
Hey ​@Paul Wagner, apologies for the delayed response and thanks for sharing more context! 

I’ve added this additional context to our internal tracking. Thanks again for taking the time to share your use case! 

Summer Derrick

It appears that Figma is charging AI credits for direct edits. Since there is no way to commit the change unless you use the prompt box. I tried to change one word in a button and it wouldnt save the change. I used the prompt box and it charged me 44 credits. ​@Gayani_S  is this expected behavior?

Gayani_S
Figmate
  • Gayani_S
  • Community Support
  • April 22, 2026

Hey ​@Summer Derrick, I want to make sure I understand what happened correctly:

When you edited the button text using the prompt box, did the AI action run successfully but the text change didn’t actually save? Or do you mean you weren’t able to make the direct text edit without going through the prompt box in the first place? 

A little more detail will help me better understand the behavior you’re seeing and share more accurate info. Thank you for you help! 

Summer Derrick

​@Gayani_S I made the edit to the button text directly in the code. While in the code view a note popped up in the prompt box asking if I want to save or discard the changes I just made. When I hit save it charged me 44 credits. If I didnt choose save or discard my changes would be lost. 

Terms & ConditionsCookie settingsAccessibility statement