What you can rely on
| Capability | Status |
|---|---|
lore CLI, macOS / Linux / Windows | Works today |
| CI / headless via API key | Works today |
| Per-repo sharing with read / write / admin roles | Works today |
| Partition read access enforced (non-members see nothing) | Works today |
| Admin-gated destructive ops (obliterate, migrate locks) | Works today |
| Disk cap enforced by the filesystem itself | Works today |
| One lore version fleet-wide, upgraded for you | Works today |
Push blocked for read-only members | Not yet - upstream lore TODO |
| VS Code / Unreal / Unity plugins | Not yet - upstream lore roadmap |
| Clone a repo by name | Not supported - clone by URL |
Honest caveat: because push isn't yet role-gated upstream, treat read vs
write as intent, not a hard push barrier today. Read access and the admin-only
operations are enforced.
Your disk cap fails the way you'd want: writes stop with "no space left on device" at the limit, deletes always work, and freed space comes back immediately - never a read-only lockout.
Every workspace runs the same lore version - not a per-workspace choice. That's what lets us revoke a compromised token (lore has no other revocation mechanism) and move a workspace between hosts safely. When we upgrade the fleet, your workspace restarts briefly on its own - no data movement, nothing for you to do.