Cloud workspace

Open a GitHub repo in the browser. The agent edits in the open.

Anyone with access to the repository can sign in, launch a workspace, and see file changes as green additions and red deletions — the same shape as Claude Code, in the chat.

How someone else onboards a project

Sign in with GitHub. Shram uses OAuth with repo scope so it can list repositories you can already clone. Org repos appear after the org grants the Shram OAuth app access (GitHub → Settings → Applications).
Create a workspace. Pick the repo from the list, or paste a github.com/owner/repo URL. Use the branch that should boot.
Launch. If the repo has no .shram.yaml, Shram’s agent reads the tree and writes one into the workspace so preview can boot. You can edit it after.
Build. Preview and the agent open in the browser. Edits stream as +added / −removed lines at the top of the chat, not buried in a collapsed tool row.

Project file

You do not paste this by hand. On onboard, the agent writes .shram.yaml into the clone when the repo does not already have one. Edit it in the workspace if the guessed dev_command is wrong.

name: my-app
dev_command: pnpm dev
ports:
  - 3000
env:
  NODE_ENV: development
secrets:
  vault_path: secret/data/projects/my-app/dev