Terminal

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

All commands run within the project’s isolated sandbox, using the same repository clone, runtime configuration, and environment variables available to the agent.

Development & Build Workflows

Use the Terminal to compile, build, and run your project exactly as you would in a local development environment.

• Run development and build commands Example: npm run build, yarn dev, make build
• Inspect files and directories Example: ls, pwd, tree, cat package.json
• Execute scripts Example: bash scripts/deploy.sh, python migrate.py
• Install dependencies Example: npm install axios, pip install fastapi
• Start or stop services Example: npm run start, docker compose up, kill <process-id>
• Test runtime behavior Example: npm test, pytest, curl http://localhost:3000

This is typically used after making code changes to verify behavior before committing or generating a pull request.

Repository Inspection

The Terminal allows you to inspect repository structure and file contents directly.

Common use cases

• List files and directories ls tree
• View file contents cat package.json less README.md
• Check branch or Git status git status git branch

This is useful when validating file changes, investigating structure, or confirming environment state.

Script & Task Execution

Many repositories include automation scripts or project-specific tooling. The Terminal allows you to execute these directly.

Common use cases

• Run migration scripts python migrate.py
• Execute setup scripts bash scripts/setup.sh
• Run seed or data scripts node scripts/seed.js

This is commonly used during feature implementation or environment preparation.

Environment Debugging

When troubleshooting runtime issues, the Terminal provides visibility into the workspace environment.

Common use cases

• Inspect environment variables printenv echo $DATABASE_URL
• Check running processes ps aux
• Verify installed packages npm list pip list

This is especially useful when diagnosing dependency conflicts or configuration mismatches.

Service Control

If your project runs background services, the Terminal allows you to start, stop, and manage them.

Common use cases

• Start local services docker compose up
• Stop services docker compose down
• Kill a process kill <process-id>

Service state persists within the workspace according to project configuration.

Relationship to Agent Execution

The agent can also run commands in execution-enabled modes. The Terminal provides manual control alongside automated execution.

Use the Terminal when you want to:

• Validate agent-generated commands manually
• Run exploratory commands
• Debug issues interactively
• Confirm runtime behavior before committing

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

Isolation & Safety

All Terminal commands:

• Execute inside the project’s isolated workspace
• Affect the cloned repository, not the original GitHub repo
• Respect environment variables defined at deployment
• Remain subject to version control and review workflows

The Terminal does not access your local system or external infrastructure unless explicitly configured to do so.