Studio
Studio is Biosimulant in the browser, at studio.biosimulant.com. Chat is the way in: you say what you want, and it runs on managed compute. Same runtime as the Python library and the Developer API.
Nothing to install, and you can start without an account.
The routes
| Route | What it is |
|---|---|
/ | Workspace home — recent chats, Labs and Runs in one place |
/chat | The conversational workspace. A conversation keeps its permalink at /c/:threadId |
/labs | Labs you own or have forked, and public labs you have opened |
/runs | Run history, with the lab context behind each simulation |
/files | Reusable input files you upload, and the outputs your runs produce |
/experiments | Runs grouped into arms so you can compare them |
/deployments | GitHub branches Studio watches, publishing a Lab version on every push |
Chat used to live at /, so older links still point there. They still work: a
request for / carrying a chat-entry parameter is redirected to /chat with
its query intact.
What Studio cannot do
Studio runs labs that live in your account or on the Hub. It can’t see uncommitted files on your own machine. Run those with the runtime or the CLI.
Start here
| If you want to… | Go to |
|---|---|
| Fork a public lab, change a parameter and compare runs | Studio quickstart |
| Understand what you keep without signing in | Guest and account mode |
| Know where your labs, runs and files live | Labs, runs and files |
| Compare several arms against one question | Run an experiment |
| Publish a Lab version on every push to a branch | Deployments |
Next steps
- Which surface do I want?: Studio beside the CLI, the Developer API and MCP
- Hub: where public labs come from
- Agents and MCP: the same account, driven by ChatGPT, Codex or Claude