Help center - Millwork

Start from what you see, not from what you think went wrong. Each help page lists a symptom, what it means, and the next thing to do. Work through the checks in order. If the problem is still there at the end, Contact support tells you what to send and what never to send.

Start with what you see

What you see	Go here
Sign-in failed, your application is still pending, or your access was removed	Sign-in and access
A provider connection failed, a secure setup link expired, or a model is missing from your catalog	Provider connection help
A run is waiting, failed, or has no result	Run and result help
An API key was rejected, lost, or may be exposed	API keys and account limits
A `402`, a `429`, a frozen wallet, or a payment that did not change your balance	API keys and account limits
A question about what a run costs or when the platform fee is charged	Model access and billing
An error code from the API	Errors and retries

If you use a coding assistant

Give the assistant the help page that matches your symptom. It may read non-secret context and run the documented read-only checks. It must ask you before a provider call, a request that costs money, a credential or account change, a message, or a deletion. See Use a coding assistant for the full rules.

Never send a password, API key, token, browser cookie, provider key, secure setup link, prompt, model output, or customer data to support.

Contact support

Send enough safe context for Millwork to investigate.