When a generation returns nothing

Fix a problem

MaShop writes files only in the Build and Agent modes, and only when the turn runs to its end.

What you see is one of four things. The assistant answers and nothing in the project moved. The reply is empty. A card appears instead of work. Or a notification takes the place of the reply.

The mode was read only

Four response modes exist: Ask, Plan, Build, Agent. Ask and Plan are read only. Ask hands the model six tools, all of them reading. Plan adds one, writing a plan. The refusal comes from the server, not from an instruction.

The badge reads Build before you choose anything, but that badge is not sent. Until you open the Response mode menu and click, the server guesses from your message. A question is read as a question and answered.

Your choice then holds for the whole page load. It stays active when you switch to the Automations thread, where the selector is hidden.

Do this: open Response mode, pick Build or Agent, send again. Reload the page to clear a mode you no longer want.

Build and Agent offer the same 29 tools. Agent only asks the model to keep going instead of handing back at each step. The four modes sets out the rest.

The turn ended on a card

A card stops the turn. The model does not read its own card and does not carry on.

• Questions card. Answer, or press the skip button. Your answers leave as your next message.
• Plan card. Press the build button. That message carries the whole plan again and is billed like any other, because the plan is not held in memory.

The engine returned nothing

When the model returns no text and no card, MaShop cancels the credit reservation. Nothing is charged.

The sentence that explains this is written on the server, in French. It is the same in every language, and it is not a sign that anything else went wrong.

Do this: name the file or the page to change, or pick another model in the input bar.

GitHub or Supabase is not connected

The chat answers with an explanation instead of generating, and nothing is charged. The check runs on every turn, not only on the first message. Disconnecting GitHub mid conversation stops the next message. Netlify stays optional at that point.

There is nowhere to install the code

If the generation dies before it starts on a project that was never published, MaShop says so and names the Publish button. A project with no database and no live site has nowhere to receive code. Publish first, then send the request again. Nothing is charged.

Credits, rate limit and role

What you read	What it means and what to do
Out of credits. Top up to keep generating.	The balance was refused before any model was called, so nothing is charged. Your message stays in the thread. Top up, then send it again.
Too many requests: N/10 per minute.	The rate limit is 10 messages per minute and 100 per hour. It is checked first, before anything else. Wait, then resend.
Store not found	The chat needs the editor role. A viewer reads this, and so does an account with no access to that project. Ask the owner for editor.
A refusal naming forbidden subjects	The content rule refuses before any model call. Nothing is charged.
A French sentence about an archived project	The project is archived, deleted or suspended. Restore it to keep generating.

Images

The input bar accepts five images. The server keeps four. The fifth is dropped with no message while the counter still reads five. Send four at most.

Any message carrying an image goes to the model that reads images, and that model stays selected for your next messages until you pick another one.

Ceilings that cut a long turn

• Twenty tool turns per message, and a budget of 200 000 tokens.
• Three hundred seconds for one generation.

The conversation itself has ceilings of its own, on how much it remembers and for how long. They are set out in How MaShop works.

Start a new conversation rather than deleting the old one

Deleting a conversation is final. There is no trash and no recovery.