# First run

> For the complete documentation index, see [llms.txt](/llms.txt)

## Open a folder

On launch, studio asks for a **project folder** — the app you want to test. If
that folder isn't set up for unotest yet, studio scaffolds it for you: the
`unotest/` layout, a config, and a runnable example test. There's no `init`
command to run.

Open another project any time from **File → Open Workspace…** (`⌘O`) or
**New Window** (`⌘N`).

## Browser check (web)

Studio runs web tests in your **system Chrome or Edge**. If neither is found, it
offers to take you to the Chrome download — you can still open the workspace to
browse and edit; only *running* a web test needs a browser.

## The window is the viewer

Once a folder opens you're in the full [viewer](/viewer/overview/): the scenario
tree, live runs, the step debugger, the inspector, and a docked terminal. Those
panels are documented in [The Viewer](/viewer/tour/) — studio is the same UI in a
native window.

## Many projects at once

Each window is its own workspace with its own local server, so you can open
several projects side by side without them interfering.

## The built-in terminal

The window includes the viewer's [docked terminal](/viewer/terminal/), so you can
run unotest or talk to your AI agent right there — without a separate install.

## Next

- [Web & iOS targets](/studio/targets/)
- [Connect your AI agent](/studio/agents/)
