Terminal & Shell Access

The Terminal runs inside the same sandboxed workspace provisioned for the project. It operates against the cloned repository, not your local machine and not the original GitHub source.

The shell prompt reflects the full worktree path. For example:

daytona@e6562e08:~/.local/share/opencode/worktree/.../trial-d6d85b7d$

This confirms you are operating inside the isolated trial branch, not the base repository or your local environment.

Opening and Managing Terminals

The Terminal opens in the right panel. Multiple terminal sessions can be open at the same time, each appears as a named tab (for example, "Terminal 1", "Terminal 2"). Use the + button to open a new tab and the × on a tab to close it.

When a command is actively running, a loading spinner appears in the top right icon bar of the workspace, indicating the terminal is busy.

What You Can Do

All standard shell commands work as expected. Common uses include:

Build and development Run build tools, development servers, and scripts exactly as you would locally, npm run dev, yarn build, make, bash scripts/setup.sh.

Dependency management Install or update packages, npm install, pip install fastapi. Output including audit warnings and vulnerability reports appears directly in the terminal.

Repository inspection Explore the file tree and file contents, ls, cat package.json, git status, git log.

Environment debugging Inspect runtime state, printenv, echo $DATABASE_URL, npm list, ps aux.

Service control Start or stop background services, docker compose up, kill <process-id>.

Test execution Run test suites and validate behavior before committing, npm test, pytest, curl http://localhost:3000.

Relationship to Agent Execution

The agent can also run commands during task execution. The Terminal gives you manual control alongside that automated execution, useful for validating agent-generated changes interactively, running exploratory commands, or debugging issues before committing.

Both manual and agent-driven execution operate within the same sandboxed environment.

Isolation

All terminal commands execute inside the project's isolated workspace. They affect the cloned repository only and respect environment variables defined in Secrets. The terminal does not access your local system or external infrastructure unless explicitly configured.