Atlas E74243keacEmergent
Help CenterBuilding with EmergentFeatures and Tools

Features and Tools

Last updated July 1, 2025

GitHub Integration

  • Push/pull from GitHub
  • Branch selection
  • Save progress & collaborate

Connect Your GitHub Account

To connect your GitHub account to Emergent:

1. Click on your profile at the top of the interface

2. Look for and click the "Connect GitHub" button

3. You will be redirected to GitHub's authorization page

4. Grant Emergent permission to access your repositories

 GitHub Button

To fetch and manage your repositories:

  1. Click the GitHub button in the Emergent interface
  2. Select a repository from the dropdown list to work with
  3. Choose specific branches if needed

Save to GitHub

To commit and push your changes to GitHub:

  1. Click the "Save to GitHub" button in the chat interface
  2. Enter a commit message describing your changes
  3. Select the branch you want to push to (or create a new branch)
  4. Click "PUSH TO GITHUB" to save your changes 

I can't push my code to GitHub

If you're experiencing difficulties pushing your Emergent project to GitHub:

  1. Use the built-in integration: Locate and use the "Save to GitHub" function in the chat interface. This native integration is optimized for Emergent projects.
  2. Check authentication: Verify your GitHub credentials are correctly linked to your Emergent account. You may need to reconnect authorization if it has expired.
  3. Repository permissions: Confirm you have write access to the target repository. Check that the repository exists and you're targeting the correct URL.

If problems persist, try creating a new repository specifically for your Emergent project, which often resolves permission-related issues.

Conflict detected error while pushing to GitHub

When encountering GitHub conflict errors with your Emergent project:

  1. Create a new branch:
  2. This is the simplest solution to bypass conflicts with existing code A new branch allows you to save your work without affecting the main codebase Later, you can properly merge changes using GitHub's conflict resolution tools
  3. Understanding the issue:
  4. This error typically occurs when changes in your Emergent project conflict with recent changes in the repository Creating a new branch isolates your changes until you're ready to resolve conflicts

For complex projects, we recommend always working in feature branches rather than pushing directly to main/master branches.

 

Live Preview

For viewing your app as you build it and check the responsiveness, design, and interactivity

To preview your application in real-time:

  1. Click the Preview button in the Emergent interface
  2. A preview window will open showing your application's current state
  3. Interact with your application to test functionality
  4. The preview automatically updates when you make changes to your code

Best Uses:

  • Test user interfaces before deployment
  • Verify that components render correctly
  • Check interactive elements like buttons and forms
  • Ensure responsive design works across different screen sizes
  • Debug visual issues in real-time

 Getting an error in the preview

When encountering errors in your Emergent project preview:

  1. Use the agent's debugging capabilities: Copy the complete error message text -> Paste it in the chat with a request like: "Please solve this error" .The agent will analyze the error and provide solutions.
  2. Why this works: The agent has deep knowledge of common development errors. By sharing the specific error, you enable precise troubleshooting This approach is faster than trying to describe the problem in general terms
  3. For persistent issues: If the agent cannot resolve the error, try providing additional context. Include information about when the error occurs and any relevant code sections.

Most preview errors can be resolved directly with the agent's assistance, as it has comprehensive understanding of web development issues. 

Code Editor (VS Code View)

To view full file structure, debug and modify agent-generated code manually

To access and use the code editor:

  1. Click the VS Code icon in the Emergent interface
  2. VS Code view will be opened
  3. Use the file explorer on the left to navigate your project structure
  4. Click on any file to view or edit its contents
  5. Make changes directly in the editor

Key Functions:

  • Edit code files directly
  • Navigate your project structure
  • Search within files
  • View error highlighting
  • Make manual adjustments to agent-generated code

Deployment

To deploy your application to the web:

  1. First, use the Preview button to test your application and ensure it works correctly.
  2. Once you're satisfied with the preview, click the Deploy button in the Emergent interface.
  3. Click "Deploy Now" to publish your application.
  4. Wait for the deployment process to complete (typically 15 minutes).
  5. Once finished, you'll receive a URL where your application is live.
  6. After deployment, you can configure environment variables and custom domain settings if needed.
  7. Share this URL to allow others to access your application.

Important Notes:

  • Always preview your application before deploying
  • Deployment creates a publicly accessible URL for your application
  • The deployment process typically takes 15 minutes
  • You can redeploy at any time to update your live application
  • Environment variables and domain settings can be configured after deployment
  • Deployment costs 50 credits per month per deployed app
  • Creates a production-ready environment with managed infrastructure that stays live 24/7
  • You can securely manage secrets and environment variables
  • Custom domains can be added, you just need to configure the A record with your DNS server and add Emergent's IP listed in the Custom Domain Flow.
  • You can relace your existing deployments with a new deployments without any additional charges, this will help you iterate on complex applications spanning across jobs.
  • View all deployed apps from the Home tab
  • Apps can be rolled back to a stable version at no additional cost
  • You can shut down any deployed app anytime to stop recurring charges

For any questions or assistance, feel free to email us at  support@emergent.sh  

Was this article helpful?