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.

Set up a shared Slack support channel

Some teams can create a Slack Connect channel shared with the boxes.dev team. If this option is available for your team:

1. Open the Slack channel page.
2. Check the channel name and the email address you use for Slack, then choose Set up channel.
3. Accept the invitation in Slack or through the email Slack sends. Your workspace may require an administrator's approval.
4. Once you've joined, invite coworkers from inside the Slack channel.

If the invitation doesn't arrive, send it again from the same page. The new invitation will use the same channel.

Use this channel for questions and support. To start coding-agent work from Slack, set up the separate Slack integration.

Some signup offers include an automatic Slack invitation. If yours does, look for the invitation at the email you used to sign up. New teammates joining your boxes.dev team will also be invited to that automatically created channel. You can check the invitation or use a different Slack email on the Slack channel page. If the first invitation is still awaiting acceptance, accept it before requesting another teammate's invitation.

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.”