Projects
A Studio project is an ordinary WAID project on disk. Studio creates it by running the CLI for you and streaming the output back, so nothing about the result is Studio-specific.
Create a project#
Open the New project panel, type a name, and press Create. The name becomes a folder, a package name and a build product, so it is checked strictly:
lowercase letters, digits and hyphens, starting with a letter or digitup to 64 charactersCreation runs in three stages, and the panel streams each one live:
Scaffold#
Studio runs waid new <name>, which creates the project and its
waid.config.json.
Install#
Studio runs npm install in the new project. This is the slow stage, and its
output is streamed rather than buffered, so you can see it working.
Skill#
Studio writes the agent contract into the project, which is what lets the chat panel work against it.
When it finishes, the panel reports where the project landed.
Where projects live#
Projects are created inside Studio's declared workspace, ~/WaidStudioProjects.
This is a granted directory, not a preference. Studio's manifest grants that one path to the file, process and shell capabilities, and Studio cannot write outside it. If you want a project somewhere else, create it with the CLI directly.
When creation fails#
Every failure is named rather than reported as a generic error:
| What you see | What it means |
|---|---|
| Invalid name | The name broke the rule above. |
| Already exists | A project of that name is already in the workspace. |
waid was not found on PATH | The CLI is not installed, or not visible to Studio. See below. |
npm was not found on PATH | Node is not installed, or not visible to Studio. |
| Failed during scaffold / install / skill | The stage ran and exited non-zero. The last lines of its output are shown. |
| Host unavailable | Studio is running without the host bridge, so it cannot start processes. |
A missing waid or npm is usually a PATH problem, not a missing
install. Studio resolves both against the runtime's inherited PATH, so a
copy of Studio launched from Finder can fail to see binaries that work fine in
your terminal. Launching from a terminal, or installing to a location on the
system PATH, resolves it.
Open a project#
The Projects panel lists what is in the workspace. Opening one loads it into
the studio: the preview server starts, and the settings forms read that
project's waid.config.json.