Create the slice you actually want
Branch from a folder, repo surface, or focused task boundary instead of cloning everything by default.
Create a focused slice, pull only the missing blocks, and work in a git-compatible tree immediately. When the task is smaller than a local checkout, edit the same versioned files directly with gs fs.
Focused local work without the full-download penalty
gs slice create ui-refresh apps/web
mkdir ui-refresh && cd ui-refresh
gs slice checkout <slice-id-or-slug>
git statusUse the same versioned filesystem directly when the fix is faster than opening a worktree.
gs fs write /$USER/app/NOTICE.txt --text "hotfix shipped remotely"
gs fs snapshot -m "patch notice"The product pitch is simple: carve out the exact slice you want, check it out fast, and merge back through changesets. Cloud edit is still there, but it is the lightweight side path instead of the whole story.
Branch from a folder, repo surface, or focused task boundary instead of cloning everything by default.
Checkout stays cheap because the client reuses cached objects and only downloads missing blocks.
Do the local work in your editor, then publish back through the same explicit review and merge path.
From custom slice creation to merge
gs slice create ui-refresh apps/web
mkdir ui-refresh && cd ui-refresh
gs slice checkout <slice-id-or-slug>
$EDITOR src/routes/settings.tsx
gs changeset create --message "refresh settings page" --files src/routes/settings.tsx
gs changeset merge <changeset-id>Not every change needs a worktree. For direct file edits, snapshots, and quick reads, gs fskeeps you in the same slice model without the checkout step.
Use the cloud filesystem directly
gs fs mkdir /$USER/notes
gs fs write /$USER/notes/todo.md --text "ship the patch"
gs fs cat /$USER/notes/todo.md
gs fs snapshot -m "notes update"Start with the right surface.