Git

A clone has three resource profiles — network, CPU, and writes. No single isolate budget fits all three, so each phase gets its own.

Clone a repository over HTTPS and work in it like any other directory. git clone fetches real packfiles from the remote. It is one of the heaviest operations a session runs. Fetch needs network time, index-pack needs CPU, and checkout makes many writes. Each phase gets a fresh CPU budget, and checkout is split into resumable chunks.

The terminal below clones a real GitHub repository: packfile negotiation, indexing, then checkout, ending in ordinary files on the session disk.

nimbus — git

Live sandbox — connecting…

git clone https://github.com/AshishKumar4/Markflow
cd Markflow && npm install && npm run dev

facebook/react, with 7,300 files, clones in ~28 s. Checkout resumes in bounded chunks, which has materialized 84,000-file worktrees. What you get is ordinary session disk. The editor sees it, npm install runs in it, and it persists.

Transport is HTTPS only; SSH is not supported. index-pack CPU can still exceed one invocation’s budget on clones with 75,000+ objects, such as microsoft/TypeScript. Making that phase resumable is in progress.