Studio Help

Using the terminal and logs

Studio includes a terminal panel and a build log so you can see exactly what is happening inside your app.

The build log

During and after a build, the log panel records every step: file changes, dependency installs, errors from the dev server. You do not need to read it for normal use, but it is useful when something goes wrong.

To open the log: Click the Logs or Terminal tab in the bottom panel of the Studio workspace. The log fills as the build runs and stays there after the build finishes.

What to look for when debugging:

• Red lines indicate errors. Copy the full error text when reporting an issue to support.
• Lines starting with error: or warn: are worth reading first.
• Build complete at the end of a successful turn confirms the build finished without errors.

The terminal

The terminal gives you direct access to the file system inside your app's sandbox. You can use it to:

• Run one-off commands, such as a database migration script.
• Check a file's contents.
• Install a package temporarily to test it before adding it via a prompt.

To open the terminal: Click the terminal icon in the bottom panel or use the Terminal tab if it is visible. Type commands and press Enter as you would in any command-line tool.

Limits on terminal use

The terminal runs inside your project's sandbox. Commands run in that environment only and do not affect anything outside your project. Long-running processes may stop when the sandbox sleeps.

Getting help from a log error

If you copy an error from the log and paste it into the chat panel with a description of what you were trying to do, Studio can often diagnose and fix the problem in one turn.