~/sursakit

// docs

Where you land after login

You authenticated (with email, Google, or GitHub). Now what? This page walks you through the first 10 minutes inside Sursakit — what every screen does and how to get to a running workspace.

1. The dashboard

Right after login you land on the dashboard. The top bar shows three things:

  • Organization switcher — your default org is selected. If you belong to more than one, switch from here.
  • Workspace switcher — empty on first login. You'll create your first workspace from the dashboard.
  • Profile menu — your account, billing, sign out.

The main area shows recent workspaces, recent sessions, and a chat input wired to Codex. New users see an empty state with a single CTA: New workspace.

2. Create your first workspace

Click New workspace. You'll be asked for:

  1. A name (anything — you can rename later).
  2. One or more services. Pick from:
    • Import a Git repo (GitHub, GitLab, or Bitbucket).
    • Pull a Docker Hub image.
    • Upload a folder.
    • Start empty.
    • Add a database from a template.

On confirm, Sursakit provisions the workspace and drops you into the workbench on the default main session.

3. The workbench

This is where you'll spend most of your time. The layout, top to bottom, left to right:

  • Top bar — workspace + session switcher, run controls, share button.
  • Left rail — file explorer grouped by service, plus activity icons (search, source control, tasks).
  • Center — Monaco editor with tabs.
  • Bottom panel — logs, problems, terminals (one per service), preview.
  • Right rail — Codex chat, version control, and pull-request panels.

Click Run all in the top bar to boot every service. Logs stream into the bottom panel. Application services expose a Preview URL.

4. Your first edit

Expand a service in the file explorer, open a file, change something, save. Monaco is connected to a real language server inside the workspace, so completions, diagnostics, and go-to-definition all see your dependencies.

If your service hot-reloads, you'll see the change reflected in the preview immediately. Otherwise, the runtime restarts.

5. Your first commit

Open the Version Control panel on the right. Review the diff, stage your changes, and commit. If you don't want to write a commit message, click Generate commit message — it'll draft one from the diff.

From the same panel you can push and open a pull request against your connected GitHub / GitLab / Bitbucket remote.

6. Hand a task to Codex

Open the chat panel in the right rail and describe a task — "add a Stripe webhook handler", "fix the timezone bug in the date picker". Codex spins up its own session, runs your services, edits files, and commits. When it's done, it lands the work as a pull request you can review the same way you'd review a teammate's.

What's next