GitHub
Quick custom slice checkouts

Check out a custom slice in seconds.

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.

Custom slices
Create a focused work surface instead of dragging an entire checkout into every task.
Quick checkout
Pull the manifest first, then download only the blocks your machine is missing.
Cloud edit
Use `gs fs` for direct remote edits when a full local tree would be slower than the fix.
Quick checkout

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 status
Cloud edit

Skip the checkout for tiny changes

Use 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"
Custom slice loop

Make local work the main path when the task deserves a real checkout.

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.

01

Create the slice you actually want

Branch from a folder, repo surface, or focused task boundary instead of cloning everything by default.

02

Check it out fast

Checkout stays cheap because the client reuses cached objects and only downloads missing blocks.

03

Merge with changesets

Do the local work in your editor, then publish back through the same explicit review and merge path.

Full 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>
  • Git-compatible local worktree
  • Custom slice per feature or folder
  • Changeset merge when you are ready to publish
Cloud edit when local is overkill

Still versioned. Still slice-backed. Just lighter weight.

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.

  • Same home slice and commit history
  • Remote reads, writes, snapshots, and diffs
  • Good for hotfixes, notes, and tiny edits
Remote path

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.

Create a custom slice. Check it out fast. Use cloud edit for the rest.