Workspaces
Each Loor project lives in a workspace — a real, file-persistent environment running on Loor's infrastructure. Open a tab, you're attached.
What a workspace is
A workspace is the environment a project lives in: real Node, real git, real file system,
real terminal. Studio is just the tab you attach to it from. Close the tab and the workspace stays —
when you re-open, you re-attach. Files survive.
Anatomy
- File system at
/home/user/workspace— persistent across restarts. - Terminals — multiple zsh sessions, one click to open.
- Dev server — auto-started from your
loor.json. - Preview — your dev port served on a per-project HTTPS subdomain.
- Source Control — git status / diff / commit / push, browser-side.
- Vibe Chat — AI agent wired into all of the above.
Hibernation
Workspaces sleep when nobody's looking. After ~20 minutes idle, Loor hibernates the container — files are preserved on disk, but you stop accruing compute. The next request bumps it back up. Typical wake time: 2–6 seconds.
This means you only pay for time you're actually building. Hobby's free quota is generous because of this — most weekend projects live well below it.
Preview & dev-server
When your dev server binds to a port (e.g. 5173), Loor detects it and exposes it on a per-workspace
subdomain: https://5173-yourapp.loor.dev. Studio's Preview tab is just an iframe pointed
at that subdomain — you can also open it in another tab.
Files & persistence
Files are stored on a persistent volume attached to the workspace. They survive hibernation, restarts, and Loor's behind-the-scenes maintenance. They do not migrate to another workspace — each project has its own.
If you connect a GitHub repo, the workspace is initialized from it. git push from
inside the workspace pushes back to your remote — Loor never holds your code.