Something broke. Read this.

Your Claude plan has a rolling usage limit, and you've used it up. Nothing is lost, and the window reopens on its own; what this costs today says which plans get how much. Paste save my place so a fresh session can pick up where you stopped.

Setup downloads the app's own copy of Node and its parts, and the download was cut off or the computer was offline. Connect to the internet and open Dorris again: it carries on from where it stopped. If the page names a different problem, paste the line it gives you for your agent.

Only one copy of the app runs at a time: Dorris, npm run open and npm run dev all refuse to start a second, because two copies sharing one local database lose data silently. Usually nothing is wrong: open the running copy from Dorris or with npm run open. npm run status shows what is running and changes nothing; npm run stop and npm run restart do what they say. If something else is using the app's port, paste something broke with the exact words.

Your store refused the app's request for orders, so the banner says Store not connected and opening the app takes you to Setup, where step 2 says Needs fixing. The app never falls back to sample data here: a fake tracking number in a real reply is worse than an error. Press step 2's Copy button, paste the message to your agent, and don't let it change code before it has explained the error. Fixed it in Shopify? Press Check again; a yes puts LIVE back in the banner. Typed something wrong? Type all three values again in the form under it.

Usually a permission was added but no new version of the app released, the app was made in a different Shopify organization from the store, or your plan hides customer details. Step 2 of the app's Setup page tells you which. Paste connect my store and work through it from the top; it's read-only, so there is nothing to break at the store end.

This happens only if you added AI-drafted replies or similar yourself: the model it names has been retired. One line in src/versions.ts names the model, and the current names are on what this costs today. Hand your agent the exact error and that page, and have it make the change and prove it with one draft.

This feels worst and is the most recoverable. Don't start fixing. Paste undo what the agent did: it names a point to go back to and what you'd lose, before anything is undone.

A secret went where someone else can read it, and deleting the message doesn't take it back. Replace the key first, then tidy up. Paste I leaked a secret. The steps in order are on I leaked an API key.

Your .env file holds your keys, and a commit keeps a copy in your project's history even after you delete it. If it went up to a hosting site, assume it's been read. Paste I leaked a secret, and replace every key in that file before cleaning up the history.

Your change didn't make it online, and the deploy log says why. First check whether the live version is still serving people. Paste the deploy failed: it settles that, then explains the cause.

Production is the live app real people are using. Stop the bleeding first: rolling back to the last version that worked is the cheapest move. Paste production is broken.

There's no reset link: the password is an environment variable, the OWNER_PASSWORD line of the .env file in the kit's folder. Open it (the dot hides it on a Mac, so ask your agent how; by its own rules it never reads that file back to you), delete everything after OWNER_PASSWORD=, save, and run npm run restart. The app asks you to create a new password. Online, change it in your host's environment settings and restart; paste walk me through a dashboard if you've never been there.

Remove or uninstall the app in your store admin's apps section. Shopify takes away its access, and your store is untouched, because the app only ever read. For a hand finding it, paste walk me through a dashboard.

A thing you added stopped doing its job without an error. A feedback button I had my agent build stopped posting to my team's chat, and I found out when my teammate asked why their tickets weren't being worked on; my agent fixed it in a couple of minutes. Tell yours what the thing used to do and what it does now, with nothing happened.

Paste something broke with the error copied exactly. If the first fix misses, paste that didn't work, which makes the agent name the assumption it got wrong. If nothing happened at all, nothing happened is written for that.

If it's setting up the kit that's stuck, write to me and I'll help you get it running.