Guest and account mode
You can use Studio before you have an account. Guest mode is there so you can try it first and decide afterwards.
The two modes
| Guest | Account | |
|---|---|---|
| How it starts | Immediately, in the browser | Your Biosimulant login |
| Where the work lives | A private session in this browser | Your account |
| History | Kept for 30 days, in this browser only | Kept with your account |
| Private Labs | No — public Hub content only | Yes |
| Saving to Studio | No, but you can download what you generate | Yes |
| Compute | Supported, within the guest limits below | Your account’s compute |
A guest session belongs to the browser that started it. It won’t follow you to another device, and clearing site data ends it.
Guest limits
These are the defaults. They can change during the beta.
| Limit | Default |
|---|---|
| Session retention | 30 days |
| Turns per day | 50 |
| Compute turns per day | 10 |
| Maximum upload | 100 MB |
Guests can chat, upload files, use public Hub content, run supported compute, and download the work they generate.
Signing in
Sign in when you want the work to follow you. An account keeps your chat history across devices, lets you start from private Labs, and gives you somewhere to save what you build.
Signing in to Studio is not the same as authenticating the CLI or connecting an agent. Each surface has its own credential — see Which surface do I want?.
Sharing
You can share a workspace as a read-only snapshot at /s/:shareId. Anyone with the link sees the snapshot but can’t change it or run from it. Controlling who can see a lab is a different thing — see Visibility and sharing.
Next steps
- Studio quickstart: fork a lab and run it
- Labs, runs and files: where your work is kept
- Visibility and sharing: private and public labs