Workspaces
JJHub workspaces run on cloud microVMs. The public workspace API is now first-class: you create a workspace, connect over SSH, suspend or resume it, fork it, and snapshot it without going through the older session-only surface.Public API
POST /api/repos/:owner/:repo/workspacescreates or resumes a workspaceGET /api/repos/:owner/:repo/workspaces/:id/sshreturns SSH connection infoPOST /api/repos/:owner/:repo/workspaces/:id/suspendsuspends the VMPOST /api/repos/:owner/:repo/workspaces/:id/resumeresumes the VMPOST /api/repos/:owner/:repo/workspaces/:id/forkforks the current workspacePOST /api/repos/:owner/:repo/workspaces/:id/snapshotcreates a reusable snapshotGET /api/repos/:owner/:repo/workspace-snapshotslists saved snapshots
Create a Workspace
SSH Access
CLI Shortcuts
The first-party CLI wraps the workspace API and can auto-detect or create the workspace you need:jjhub workspace issue fetches the issue, creates a workspace, opens a draft landing request that references the issue, and then connects to the workspace so you can start working immediately.
Suspend and Resume
Suspend keeps the workspace disk and memory state so resume is effectively instant:Forking
Forking creates a parallel copy of the current workspace so you can explore a risky change without disturbing the source VM:Snapshots
Snapshots let you save workspace state and later create a new workspace from it:Legacy Session API
The older session-based endpoints still exist for terminal-session compatibility:POST /api/repos/:owner/:repo/workspace/sessionsGET /api/repos/:owner/:repo/workspace/sessions/:id/sshPOST /api/repos/:owner/:repo/workspace/sessions/:id/destroy
/workspaces for new integrations and the jjhub workspace ... CLI surface.