Opening Studio

Summary#

Opens Studio in your browser. You name a project, say what you want, and Studio starts your own installed Claude Code in the project's folder, shows what it is doing, checks the result and opens the app. Projects are ordinary folders on your computer; everything Studio knows about one is kept inside it.

Signature#

osy studio [stop] [--print-url] [--instance <name>]

Description#

Run it from any folder. It reads nothing from where it is run.

• Studio's source travels inside the toolchain. osy studio copies it to ~/.osy/studio/source, starts (or finds) the local platform named studio, compiles Studio into it, and opens your browser. The first start on a computer takes about a minute; later ones a few seconds. Nothing is downloaded: Studio and the two kits it uses are in the folder.
• The tab it opens is the only one signed in. Studio can start programs and read folders on your computer, so it answers no one else. The browser is opened through a link that works once: the same address typed into another tab, another browser, or requested by a page of another site, opens a page that says how to open Studio and nothing more. Run osy studio again whenever you want another signed-in tab.
• osy studio stop ends Studio and any build it is running. Your projects are untouched, and the next osy studio finds them again from their folders.
• --print-url prints the one-time address instead of opening a browser.
• --instance <name> opens a second Studio beside the first: its own local platform (studio-<name>) and its own copy of the source (~/.osy/studio-<name>/source), so it neither stops nor changes the one already open. It keeps its projects in a folder of its own too (~/.osy/studio-<name>/projects) — two Studios never share one. It is for trying another build of osy while the first Studio stays as it is. osy studio stop --instance <name> ends it.
• Where projects are kept is Osy Projects in your documents folder. Settings has "Where your projects are kept": name another folder inside your home folder and new projects are made there. Nothing is moved — the projects already made stay where they are, and Studio lists the ones in the folder it is pointed at. Each Studio remembers its own folder.

In a project you have:

• Chat — what you asked, what the builder is doing now in a sentence, its plan and design as it writes them, pictures of the app as they are taken, and the build as a timeline you can open entry by entry. While it works, the current step and Stop stay at the foot of the window. When it has a question about the product, the question is a card with its options, what each costs and its recommendation; "Use your recommendations" lets it decide without stopping.
• Open app — as it is, or with sample data: the worlds the app's own tests start from (Dev seeds: a fixture you can load into the running app), loaded into it — which replaces what is in the app — and then the accounts that world made, each with Sign in as. An app with no sample data offers one press that asks the builder for it.
• The model and the effort — which model builds and how long it thinks first: a default under Settings, and a chip on the prompt box for one project. "Default" leaves it to your Claude Code.
• Publish — put the project on Osyrin, or send it its changes: the sheet says who is signed in, which app it is there, the version people get, what changed since and what will happen, then runs the CLI's own osyrin app create and osy deploy. Signing in to Osyrin is under Settings, in Osyrin's own sign-in. See Publishing a project to Osyrin.
• Photos — every picture, build by build.
• Mood board — pictures you like, faces for headings and text, a few colours or a palette Studio works out from one colour (each checked so its text can be read). The builder is told to follow them, in a sentence you see first.

A download also holds a launcher — Osyrin Studio (Osyrin Studio.command on macOS and Linux, Osyrin Studio.cmd on Windows) — that does the same on a double-click, with nothing on your PATH.

A newer Studio. Studio is the toolchain's version, so a newer Studio is a newer osy. A little after Studio opens, and every few hours while it stays open, it asks the toolchain (osy upgrade --check --json --daily, see Upgrading the toolchain) — after the first screen is drawn, so a start is never slowed, and an answer that cannot be had is simply no notice. When there is one, a card at the foot of the rail says "Osyrin Studio 0.15.0 is available (you have 0.14.2)", with What's new, and what to do depends on how the toolchain was installed:

Updating keeps your projects, which are folders. The old Studio's local platform is replaced, as every local platform is on an upgrade; a projects folder chosen under Settings is the one thing it remembered there, so name it again.

Studio's local platform is an ordinary one (Running a local platform): it is listed by osy instances, and it stops by itself after an hour with nothing running and nothing asked of it.

Examples#

osy studio             # start Studio and open it, signed in, in your browser
osy studio stop        # end it
osy studio --instance trial   # a second Studio, beside the first

See also#

Launching your app — osy launch --as <login> is the same one-time sign-in for an app of your own.

Host — the computer a local app runs on — how an Osy# app such as Studio starts programs and reads folders on the computer it runs on.