Sessions
A session is one private cloud workspace — editor, terminal, and files in your browser. You can have several; each one is independent and temporary.
Create a session
- Sign in, then go to home.
- Click + New coding session (first visit starts one for you automatically).
- Wait through the loading screen — typically seconds:
Setting up your dg.run workspace...Starting coding environment...Connecting...
- Your workspace opens embedded in the page.
You can watch a short sponsored message on the loading screen — watching it fully can earn a small credit reward (see Wallet & billing).
Open and switch
- Your dashboard at home lists Active sessions (status
live/starting) with an Open button each. - Opening a session at
/<sessionId>never creates a duplicate — it reconnects to the same workspace. - Refreshing the page does not stop the session. Close the tab and come back later while it's live — you'll reconnect.
Stop a session
- Click Stop Session in the workspace header, or Stop next to it on the dashboard. Confirm once — the workspace shuts down immediately.
- Stopped sessions move to Past (last 5 shown). They cannot be reopened — start a fresh one instead.
- Stopping also revokes that session's port share links (see Ports & sharing). The links stop working at once.
What ends a session
- You stop it yourself.
- Your credit balance runs out (see Wallet & billing).
- Your account is blocked.
- Rare infrastructure interruptions — the page shows Coding session ended.
If you land on Session not found, the workspace already expired or was stopped. Click Retry once, then Back to sessions and start a new one. Details in Support.
Workspaces are temporary
Nothing persists after a session ends — no files, no installed packages, no editor history. Before stopping:
git pushanything you want to keep, or- download files from the editor.
There is no "pause and resume later" — a stopped machine is gone for good by design.