Contact support

For help with boxes.dev, email hi@boxes.dev. You can also report a bug or send a product suggestion from the desktop app: open Help and feedback beside your account at the bottom of the sidebar, then choose Send feedback.

Email and the public support page are available if you can't sign in.

Use Send feedback to describe a problem and choose which diagnostics to include. Select the image to enlarge it.

Include enough context to reproduce the problem

Tell us what you tried, what you expected, and what happened instead. Include:

• Names or links for the project, devbox, thread, or automation involved.
• The approximate time, with your time zone.
• Whether you were using desktop, mobile, web, or the CLI.
• The exact error message and any support reference or request ID shown.
• The recovery steps you've already tried.

Use Copy details if the error offers it. For a display problem, include a screenshot of the affected area. Remove passwords, tokens, and other secrets from anything you send.

Report from your terminal

Run dvb report-bug on your own computer to send a report to the same feedback queue as the desktop app. The command sends the report as soon as you run it, so write your own description of what happened. For example, if the ports menu stayed empty after you reconnected:

dvb report-bug "The ports menu stayed empty after reconnecting."

For a longer description of the same problem, pipe the text to dvb report-bug --stdin:

printf '%s\n' \
  'I woke my devbox and started the development server on port 3000.' \
  'The ports menu stayed empty after I reloaded the desktop app.' \
  | dvb report-bug --stdin

The report will include your description, CLI version, operating system, and your boxes.dev account information when you're signed in. It won't automatically attach repository files, environment variables, or your working-directory path. If the dvb command isn't set up on your computer, set up the CLI first.

Reports from coding agents

Codex and Claude agents on your boxes.dev machines can send reports to the same queue. When an agent finds that a boxes.dev command it needed is missing or doesn't work, it can send a short description of what it was trying to do and what happened. The report will include your boxes.dev account, the machine and project, and the thread's ID, and the agent will mention the report in its final response. Agents are instructed to leave out confidential information, such as secrets, source code, personal data, and details of your work, unless you explicitly ask them to include it. They can include IDs that help us debug the problem, such as thread or devbox IDs. If you'd rather an agent didn't send feedback, say so in your request. See Send feedback to boxes.dev for the commands agents use.

Security and abuse reports

Send suspected vulnerabilities to security@boxes.dev. Include the affected part of the product, steps to reproduce, the impact, and a proof of concept if safe to share. Stop testing if you encounter another person's sensitive data.

Report harmful public preview content to report@boxes.dev.

If you need to delete an account you can't sign in to, email hi@boxes.dev from the account's email address with the subject “Delete my boxes.dev account.”