Unable to use point and edit in Make

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! 

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.

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?

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! 

​@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. 

Hey ​@Summer Derrick, thank you for clarifying, and apologies for the delayed response! 

I’ve reached out to the team internally and shared your case to confirm whether this is expected behavior or not. I’ll update you here as soon as I hear back from them.

Appreciate your patience while I look into this! 

Hey ​@Summer Derrick, the team hasn’t been able to reproduce this on their end so far, so just want to make sure we’re looking at the same thing. Can you confirm if the save/discard buttons were disabled unless there was text in the prompt box?

If possible, could you also share a screenshot or a short recording (Loom or Google Drive link works great)? That would really help us take a closer look.

​@Gayani_S The save/discard buttons show up after I make a change with the Point/Edit tool. Here is a video link. 

Hey ​@Summer Derrick, thanks again for your patience, and I’m sorry for the delay in getting back to you. 

Since this is tied to account-specific details, I’m not able to fully investigate it here on the forum. To make sure this gets properly looked into, I’ve gone ahead and created a support ticket on your behalf ( #1895726) and shared your screen recording along with the context from this thread. That way, the team has everything they need to dig into what’s happening.

Someone from the support team should reach out to you soon with an update. Thanks again for your patience while we look into this!

Hi, I’m facing the same issue! I planned in a way that i would use my AI credits to vibe code and then edit manually. But now I’m stuck since the credits are over. Is there a workaround?

Hey theunrealsushi, thanks for reaching out! 

Staging edits through Point and Edit, or the newer edit tool and properties panel if your file has that update, happens before anything is committed. Applying those changes to update your file is what uses AI credits, since that step turns them into code, the same as sending a prompt would.

A couple of options if you'd like to keep moving in the meantime:

• Copy your current Figma Make preview into a Figma Design file and continue there. Regular editing in Figma Design doesn't draw from your AI credits. Just keep in mind this creates a static set of design layers rather than a functional version, and edits you make in Figma Design won't sync back to your original Figma Make file.
• If you'd rather roll back instead of moving forward, restoring an earlier version from your file's version history is also free.

Your credits will refresh at the start of your next billing period. If you'd like to keep applying edits sooner, your team admin can add more through an AI credits subscription or pay-as-you-go, both available on the Professional plan.

Here's more on Copy a Figma Make preview as design layers, and How AI credits work covers usage and resets in more detail.

Could you tell me what you're seeing when you try to make a manual edit right now, are you able to select an element and see the toolbar or properties panel at all, or does everything grey out immediately? That'll help me confirm whether it's the credits-on-Apply behaviour above or something else.

I think this is a very reasonable feature request. I can understand disabling AI-powered actions when the credit limit is reached, but disabling the entire prompt box also removes functionality that doesn’t consume credits.

Keeping Point and Edit available would make the credit limitation much less disruptive. Users could still make manual changes, inspect specific parts of the code, and continue working while waiting for their credits to reset or renew.

Hopefully the team can separate the AI-powered functionality from the manual editing tools so users aren’t completely blocked from their projects once they run out of credits.