Add confirmation before spending credits
Johnathan Lightfoot
Because MCP is conversational, there is risk that an assistant could trigger credit usage before the user fully understands what is being generated.
I would suggest a built-in confirmation mode:
“This will generate a 12-card presentation and may use approximately X credits. Continue?”
That would protect both Gamma and the user.
Nik Payne (Gamma design)
Johnathan Lightfoot this is a really thoughtful callout, especially with conversational/MCP flows where it’s easy to accidentally kick off something credit-heavy. I’ll pass the confirmation-mode idea to the team.
Quick question: would you want this confirmation every time credits might be spent, or only when it’s above a threshold (like “more than X credits” or “more than Y cards”)?
Johnathan Lightfoot
Nik Payne (Gamma design) Both, but with a threshold-based default.
Confirming every single credit spend would get annoying fast in normal conversation. But once a request crosses a real threshold, confirmation makes sense.
So: small/normal requests → just run. Bigger or credit-heavy requests → confirm first.
Triggers could be things like estimated credits above X, deck over Y cards, AI image generation on, premium image model, costly export options, or multiple outputs in one request.
Then maybe a workspace setting for people who want to pick their mode: always confirm, confirm above threshold, or never confirm. Threshold-based feels like the right default though.