Code Server (VS Code in Browser)

Code Server runs a full VS Code IDE in your browser — extensions, terminal, debugger, and Git — with direct access to the sandbox network and no local install required.

Aithroyz deploys Code Server on a dedicated VM with a persistent home directory. The terminal has direct access to the sandbox internal network (10.0.0.x).

Access

URL: https://vscode.<env-name>.ops.aithroyz.com

Password: Shown in Environments detail → Credentials panel.

Opening a workspace

Explorer

Ctrl+Shift+E

Open the file explorer to browse and open files in your persistent home directory.

Terminal

Ctrl+`

Open an integrated terminal with full bash access to the VM and internal sandbox network.

Clone from Gitea

Ctrl+Shift+P → Git: Clone

Paste the Gitea HTTPS or SSH clone URL to pull a repository directly into the workspace.

Clone from GitHub

Ctrl+Shift+P → Git: Clone

Clone any public or private GitHub repository the same way — provide a PAT if the repo is private.

Installing extensions

Open the Extensions panel with Ctrl+Shift+X and search for any VS Code extension. Recommended extensions for sandbox work:

Python (ms-python.python)

Full Python language support — IntelliSense, linting, debugging, and Jupyter notebook integration.

ESLint (dbaeumer.vscode-eslint)

JavaScript and TypeScript linting inline in the editor.

HashiCorp Terraform

Syntax highlighting, IntelliSense, and formatting for .tf files — useful for reviewing OpenTofu modules.

Docker (ms-azuretools.vscode-docker)

Browse and manage containers, images, and compose files from the sidebar.

YAML (redhat.vscode-yaml)

Schema-aware YAML editing for Kubernetes manifests, CI workflows, and n8n exports.

ℹ

Extensions are stored in the persistent data volume and survive environment restarts. You only need to install them once.

Accessing sandbox resources from the terminal

The terminal runs directly on the sandbox VM and can reach all internal services by their private IP addresses.

# SSH into another VM in the sandbox (no bastion needed)
ssh user@10.0.0.21

# Query the Elasticsearch API directly via internal IP
curl -u elastic:<password> http://10.0.0.20:9200/_cluster/health

# Use the AWS CLI against MinIO via the S3 subdomain
aws s3 ls --endpoint-url https://s3.<env-name>.ops.aithroyz.com

# POST to TheHive API
curl -X POST http://10.0.0.25:9000/api/v1/case \
  -H "Authorization: Bearer <api-key>" \
  -H "Content-Type: application/json" \
  -d '{"title": "Incident-001", "severity": 2}'

Tips

✓

Extensions and settings persist in the data volume across reboots and environment TTL extensions — you only need to configure your workspace once.

ℹ

Code Server automatically detects locally running servers and shows a port-forwarding notification. Click Open in Browser to access a dev server running on a local port via the browser.

✓

If Docker is installed on the Code Server VM, you can use the Dev Containers extension to run full containerized development environments with isolated toolchains.

Gitea (Self-hosted Git)Read article →MinIO (S3-compatible Storage)Read article →

Code Server (VS Code in Browser)

Code Server runs a full VS Code IDE in your browser — extensions, terminal, debugger, and Git — with direct access to the sandbox network and no local install required.

Aithroyz deploys Code Server on a dedicated VM with a persistent home directory. The terminal has direct access to the sandbox internal network (10.0.0.x).

Access

URL: https://vscode.<env-name>.ops.aithroyz.com

Password: Shown in Environments detail → Credentials panel.

Opening a workspace

Explorer

Ctrl+Shift+E

Open the file explorer to browse and open files in your persistent home directory.

Terminal

Ctrl+`

Open an integrated terminal with full bash access to the VM and internal sandbox network.

Clone from Gitea

Ctrl+Shift+P → Git: Clone

Paste the Gitea HTTPS or SSH clone URL to pull a repository directly into the workspace.

Clone from GitHub

Ctrl+Shift+P → Git: Clone

Clone any public or private GitHub repository the same way — provide a PAT if the repo is private.

Installing extensions

Open the Extensions panel with Ctrl+Shift+X and search for any VS Code extension. Recommended extensions for sandbox work:

Python (ms-python.python)

Full Python language support — IntelliSense, linting, debugging, and Jupyter notebook integration.

ESLint (dbaeumer.vscode-eslint)

JavaScript and TypeScript linting inline in the editor.

HashiCorp Terraform

Syntax highlighting, IntelliSense, and formatting for .tf files — useful for reviewing OpenTofu modules.

Docker (ms-azuretools.vscode-docker)

Browse and manage containers, images, and compose files from the sidebar.

YAML (redhat.vscode-yaml)

Schema-aware YAML editing for Kubernetes manifests, CI workflows, and n8n exports.

ℹ

Extensions are stored in the persistent data volume and survive environment restarts. You only need to install them once.

Accessing sandbox resources from the terminal

The terminal runs directly on the sandbox VM and can reach all internal services by their private IP addresses.

# SSH into another VM in the sandbox (no bastion needed)
ssh user@10.0.0.21

# Query the Elasticsearch API directly via internal IP
curl -u elastic:<password> http://10.0.0.20:9200/_cluster/health

# Use the AWS CLI against MinIO via the S3 subdomain
aws s3 ls --endpoint-url https://s3.<env-name>.ops.aithroyz.com

# POST to TheHive API
curl -X POST http://10.0.0.25:9000/api/v1/case \
  -H "Authorization: Bearer <api-key>" \
  -H "Content-Type: application/json" \
  -d '{"title": "Incident-001", "severity": 2}'

Tips

✓

Extensions and settings persist in the data volume across reboots and environment TTL extensions — you only need to configure your workspace once.

ℹ

Code Server automatically detects locally running servers and shows a port-forwarding notification. Click Open in Browser to access a dev server running on a local port via the browser.

✓

If Docker is installed on the Code Server VM, you can use the Dev Containers extension to run full containerized development environments with isolated toolchains.