Support

Getting help, support & community

Where to get help

We're here to help you succeed with Emergent. Whether you have a question, need troubleshooting support, or want to connect with other builders, you have two main channels.

Discord community

Join our Discord server to:

  • Ask questions and get quick answers from the community
  • Share what you're building and get feedback
  • Learn tips and workflows from experienced users
  • Stay up to date with platform announcements

The Discord is the fastest way to connect with both the Emergent team and other builders.

Support email

For issues that require account-level assistance or private discussion, email us at support@emergent.sh.

We typically respond within one business day. Support email is best for:

  • Billing and subscription questions
  • Account access issues
  • Detailed bug reports
  • Feature requests that include sensitive information

Filing a good bug report

When something goes wrong, a detailed bug report helps us fix the issue quickly. The most important piece of information is your Job ID.

Include your Job ID

Every build or operation in Emergent has a unique Job ID visible in the workspace. To find it:

1

Locate the Job ID

Look in the bottom-left corner of the workspace sidebar or in the job history panel. It's a string like

job_abc123xyz
.

2

Copy the full ID

Click to copy or select and copy the entire Job ID string.

3

Include it in your report

Paste the Job ID in your Discord message or support email. This lets us look up the exact context of your build.

Tip

If you have multiple jobs related to the issue, include all relevant Job IDs.

Add screenshots of errors

A screenshot of the error message or unexpected behavior provides critical context. Capture:

  • The full error message text
  • Any red error banners or console output
  • The state of the workspace when the issue occurred

Describe what you expected vs. what happened

A quick sentence or two helps us understand the gap:

"I asked the agent to add a login page, expected it to create

/login
, but it created
/signin
instead and broke the routing."

This context, combined with your Job ID and screenshot, gives us everything we need to investigate.


Learning resources

If you're new to Emergent, check out Your first build for a guided walkthrough, or visit How apps work here to understand the platform's mental model.

Was this page helpful?

Related pages