Skip to main content
Email support@getmillwork.dev when the checks on a help page did not fix the problem. Support needs enough context to find the request on Millwork’s side: which surface, which endpoint, when, and the error’s instance ID. Support never needs a secret, a prompt, or model output, and cannot recover a key or credential that you no longer have.

​
What to send

  • what you tried and what you expected;
  • the surface: dashboard, API, or provider;
  • the endpoint and HTTP method;
  • the UTC time;
  • your organization ID, and the run ID or connection ID;
  • the HTTP status, and the error’s type, title, and instance;
  • whether it happens every time; and
  • which checks you already completed.
For a dashboard problem, a redacted screenshot helps. For a billing question, include only the amount, the UTC time, and the run or receipt ID. Never include card or bank details. The platform fee for a live run is charged when Millwork accepts it; see Model access and billing before you ask about a charge.

​
What never to send

Never send a password, API key, token, browser cookie, provider key, secure setup link, invitation link, prompt, model output, or customer data.
Millwork cannot recover a secret that is no longer available. Create a new API key in the dashboard, or complete a new secure setup for a provider key.

​
Ask your coding assistant to prepare the report

Copy the prompt below into the coding assistant that can see your project or your current terminal. It collects the safe details listed above and writes the draft. You review the draft, then send it yourself.
Review the draft before you send it. The assistant prepares the report. It does not email support or change your account.
Do not paste an entire console, log file, request body, or response body into an assistant. First remove credentials, authorization headers, cookies, secure setup links, prompts, model output, and customer data.