How to skip a check, or turn one off
Piezas checks your app at a few points while your AI builds it and before it goes live. You are always in charge. Every stop can be passed, and only you can pass it: your AI can't say these words for you. Type the words below in the chat with your AI (Claude Code or Codex). Most of them also work…
Piezas checks your app at a few points while your AI builds it and before it goes live. You are always in charge. Every stop can be passed, and only you can pass it: your AI can't say these words for you.
Type the words below in the chat with your AI (Claude Code or Codex). Most of them also work in your own terminal.
Put a version live anyway
When a deploy stops and lists what is wrong, reply:
deploy anyway
This version goes live as it is, with everything that was listed. Piezas remembers your answer, so the next deploy asks only about something new or changed.
If the list includes a safety rule (for example, your app's private key showing in the browser) or a missing setting, type exactly deploy anyway with no other words.
Skip one check
When a check keeps failing, you can leave it out for now:
- skip and the part's name, for example skip Add a dog
- skip all, to leave out every part listed
A skipped check stays out until it passes again. To give your AI more time to fix it instead, reply keep trying.
OK a check your AI changed
Sometimes your AI rewrites one of the checks. Piezas asks you first:
- yes and the part's name, for example yes Add a dog, to accept the change
- keep fixing, to keep the original check
The quality scan
The quality scan is a second look at your app's code.
| You type | What happens |
|---|---|
| quality scan off | The scan stops for good. Turn it back on with quality scan on. |
| quality scan before publishing only | The scan runs only when you put the app live. |
| go live without the scan | This one version goes live without the scan. |
| accept 2 (or accept all) | Go on without fixing that problem (or any of them). |
The design preview
Before your AI builds the real app, it shows you a preview. When you're happy with it, reply approve.
Changes outside your app's folder
If your AI needs to change something outside your app's folder, Piezas asks first. Reply allow outside changes to let it, for this session.
In your own terminal
You can also answer in a terminal window, outside your AI:
| You run | What it does |
|---|---|
npx piezas deploy |
When it stops, type deploy anyway to go live as it is, or press Enter to have it fixed first. |
npx piezas quality-scan off |
Turns the quality scan off. Use on to turn it back on. |
npx piezas unattended on |
For automatic deploys (for example from GitHub): they go live without the quality scan. The checks still run. |
What stays on
A few safety rules always apply while your AI builds:
- Your app's private key never goes into the browser.
- Your app's data stays in Piezas, not in a separate database.
Your AI can't write code that breaks these rules. If a version that breaks one ever reaches a deploy, you can still put it live with deploy anyway. Fixing it is strongly recommended.
Good to know
- Only your own words count. If your AI asks you to type one of these phrases, type it yourself in the chat.
- Each answer covers what you were shown. If the code changes after you answer, Piezas may ask again about the new version.