Workspace Start

Create the first workspace

Prepare repository access, choose the right template and backup, create the workspace, and launch Browser IDE.

Customer adminsCustomer members
Console-rendered Create Workspace page with safe repository access, template choice, and create readiness.
Console-rendered example with safe data: Create shows Git credential health and readiness context before workspace creation.

Pre-flight checklist

Before you click Create, confirm:

  • Account setup is not blocked.
  • Billing or trial access is approved.
  • Prepaid workspace time and managed-AI credit are funded when your account uses prepaid access.
  • The workspace target is available.
  • The template you selected is approved for your account.
  • The repository URL and branch are correct.
  • The database backup or seed choice is correct.
  • Private Git credentials show valid clone access when needed.

Choose repository access

For public repositories, paste the clone URL and branch.

For private repositories, use the Console credential flow for your provider. Console may validate the credential and show health information, but it does not show saved token, app-password, or private-key values after storage.

ProviderTypical safe inputDo not paste
GitLabProject URL, branch, saved PAT health state.Raw PAT in tickets or docs.
GitHubRepository URL, branch, saved PAT health state.Raw PAT in screenshots.
BitbucketRepository URL, branch, saved app-password health state.App-password values.
Azure DevOpsOrganization/project/repo URL and branch.PAT value outside the credential flow.

Create the workspace

  1. Open Create.
  2. Choose the approved template.
  3. Confirm workspace target and repository settings.
  4. Select a backup or seed when the template needs one.
  5. Review credential and readiness messages.
  6. Click Create Workspace.
  7. Watch build status until the workspace is ready.

If Console shows a validation error, fix that exact field before retrying. If Coder accepts the workspace and startup later fails, keep the workspace available for inspection unless an operator tells you cleanup is safe.

Launch Browser IDE

  1. Open My Workspaces.
  2. Wait for the workspace status to be ready or running.
  3. Click Browser IDE.
  4. If the browser asks you to sign in again, complete SSO and return to the launch link.

The Browser IDE link should use the public workspace URL. If it opens an internal service address or redirects to a place your browser cannot reach, stop and report the issue.

Create blocked troubleshooting

BlockerWhat it usually meansNext action
Billing or prepaid balanceThe account is not approved or funded for creates.Ask a customer admin or operator to review Catalog and billing state.
Target unavailableRuntime target is not ready for this account.Ask ISM support to review target readiness.
Template unavailableThe visible template alias cannot resolve to an active template.Choose another approved template or ask support.
Git validation failedRepo URL, branch, or credential is wrong.Update the repository or credential health state.
Workspace user provisioning failedIdentity or Coder user mapping needs review.Escalate with visible error and user email.

Done When

  • Billing or trial access is approved.
  • Workspace target is available.
  • Template choice is available for your account.
  • Repository and branch are correct.
  • Backup or database seed choice is correct.
  • Browser IDE opens after the workspace is ready.