Environments settings

Environments define where automation commands and agent tools run — containers or sandboxes with specific dependencies and access.

Configure environments

Open Settings → Environments to list and edit environments.

Each environment may specify:

  • Base image or runtime
  • Installed tools and packages
  • Network or secret access policies
  • Preview ports (3000–3999) published through the workspace gateway

Preview ports

Ports under the Ports tab are the only ports agents may expose as preview URLs.

  • Range: 3000–3999 (platform ports stay private)
  • Default is often 3000 only — add more if your app needs them
  • Bind services on 0.0.0.0 so the gateway can reach them
  • After changing ports, ask the agent for a fresh preview URL
  • Keep the conversation open while using a preview — idle environments stop after about 10 minutes

Agents cannot expand the allowlist; only workspace members can grant ports.

When environments are used

Automations with command steps execute in an environment. Agents may also use environments when running shell commands as part of a workflow.

Separate from production

Konvio environments are for automation and agent execution, not a replacement for your production infrastructure. Keep production credentials out of environments unless explicitly required and approved.

Best practices

  • Mirror production tool versions when commands depend on specific CLIs
  • Use workspace Variables for secrets instead of hard-coding in environment config
  • Name environments clearly (ci, investigation, deploy)
  • Grant only the preview ports you need