Skip to main content
Version: 3.1

Studio

Operaide Studio runs one isolated editor process per user. Two settings shape what these processes can do: environment variables for all Studio processes of your organisation, and the deployment-level webview mode for editor extensions.

Set Environment Variables for Studio Processes​

You configure organisation-wide environment variables as a Connection of type Operaide Studio Environment under Connections in the sidebar.

  1. Open Connections and create a connection of type Operaide Studio Environment.
  2. Use default as the connection name.
  3. Add key-value pairs under Environment Variables.

Every Studio process started afterwards receives these variables. Running sessions keep their old environment until they stop and start again.

Typical uses: API tokens for command-line tools, integration tokens, debug settings.

Enable Editor Extension Webviews​

Panels of installed editor extensions (for example the Claude Code extension) stay blank by default. The editor serves panel content from random per-panel subdomains, so extension JavaScript runs on an isolated browser origin. These subdomains do not resolve on a standard single-host deployment.

To make extension panels work, the deployment operator sets one environment variable on the app container:

environment:
  OPERAIDE_STUDIO_WEBVIEW_EXTERNAL_ENDPOINT: "{{hostname}}"

This is a container-level setting in the deployment's compose file. An organisation admin can alternatively set the same variable org-wide through the Studio Environment connection described above.

warning

Same-origin panels remove the browser-side isolation of extension code. A malicious or compromised editor extension can then read the user's platform session, including login tokens, and act as that user through the API. Isolation between users on the server is not affected. Enable this only when your users install extensions from sources you trust.

Full isolation with working extension panels requires a wildcard DNS setup. Operaide does not support that yet.

Common Mistakes​

  • Expecting new environment variables in a running session: variables apply when a Studio process starts. Reopen Studio after changing the connection.
  • Enabling webviews without reading the warning above: the setting trades browser-side isolation for working extension panels. Make that decision consciously.