Appearance
⌘K
DocsCommon problems and how to recover from them.
What's happening: The plan includes the wrong features or scope.
How to fix it:
How to prevent it: Use the first prompt template from Prompting and include an explicit out-of-scope list.
What's happening: MonstarX started building but the process appears stuck.
How to fix it:
What's happening: The Preview tab shows nothing, or an empty screen.
Most likely cause: A required service isn't connected.
How to fix it:
Other possible causes:
What's happening: You sent a message and the build completed, but the Preview tab shows an empty screen.
Most likely cause: A required connector wasn't set up before building.
How to fix it:
If all required services are already connected, use Discuss mode and ask: "The Preview is blank after my last message. Is there an error in the code?"
What's happening: A message like "No credits remaining" appears and the build won't start.
How to fix it:
Credits are consumed when MonstarX builds or rebuilds your app. Discussing and reviewing the plan does not use credits.
What's happening: Something you described isn't in the built app.
How to fix it:
How to prevent it: Read the full plan before approving. If something's missing, correct it before you approve.
What's happening: A connector shows as Required and the app won't work without it.
How to fix it:
How to fix it:
pk_test_ and sk_test_pk_live_ and sk_live_What's happening: Password reset or confirmation emails aren't arriving.
How to fix it:
How to fix it:
How to fix it:
What's happening: A recent change caused something to stop working.
How to fix it:
How to prevent it: Use Discuss mode before any message that touches multiple parts of your app.
How to fix it:
Build incrementally. Start simple. Add features one message at a time, don't try to describe everything at once.
Read the plan before approving. It's your only checkpoint before building starts.
Use Discuss mode freely. If you're unsure whether a message will trigger a large change, ask in Discuss mode first.
Use test credentials while developing. Switch to live keys only before your final publish.
Describe patterns, not individual fixes. If the same issue appears in multiple places, describe it once: "All buttons across the app should use #2563eb. Fix all instances."