Running work
Interactive sessions
A shell or a notebook on real GPUs, billed as Strike, that shuts itself off when you walk away.
Sometimes you need to poke at a model before you write the job. An interactive session is a job that runs a shell or JupyterLab instead of your command, and that you connect to.
Start one
forge shell --gpus 1 --image ghcr.io/yourlab/dev:latest
# or a notebook, opened in your browser
forge notebook --gpus 2 --image ghcr.io/yourlab/dev:latestforge shell drops you into the container over SSH, through our gateway, with the key from your console profile. forge notebook prints a private HTTPS link to JupyterLab.
How it is billed
Sessions bill at the Strike rate, per second, or draw from your hour bank if you pass --plan bank. They are never Ember: losing a shell mid thought is worse than paying full price.
Idle shutoff
A session stops itself after 30 minutes in which all of its GPUs sat under 2 % load and no client was connected. Five minutes before, the shell prints a warning and the notebook shows a banner. Change the window with --idle 2h, up to 8 hours.
Limits
At most 2 sessions per team at once, up to 8 GPUs each, and 24 hours per session.