Use the integrated terminal
Run project commands and read their output without leaving Choro.
Last updated 16 September 2026
Run project commands and read their output without leaving Choro.
Before you start
Open the project’s Code workspace. Know what command you intend to run and whether it changes files, starts a service, or only inspects the project.
The demo’s Verify command has finished and printed its result. Read both the output and the session’s exited state instead of assuming that opening a terminal means the command succeeded.
Step by step
Open Terminal from Code. Check the working directory in the shell before running a command, especially if you have switched projects or isolated workspaces.
Enter the project’s documented command and inspect its output. For a first orientation, read the README rather than guessing a package manager or run script.
Keep a long-running development server in its own terminal session so its output remains easy to follow.
When output contains a local HTTP or HTTPS address, open the matching service in Preview. Confirm that the page belongs to this project.
Stop a command deliberately when it is no longer needed. Use the relevant session or service control and check that the process has actually ended.
What to expect
The terminal provides the command output you need to diagnose runs, tests, and local services alongside the project files.
Troubleshooting and useful details
An open terminal is not evidence that a command succeeded. Read its exit result and errors. If a command cannot be found, check the project’s environment and installation instructions. Do not paste unknown commands just to clear an error.