Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.qoder.com/llms.txt

Use this file to discover all available pages before exploring further.

Agent Sessions run inside isolated sandbox containers. This page lists the operating system, preinstalled tools, and resource limits for the runtime.

Operating System

ItemValue
DistributionUbuntu 22.04 LTS (Jammy)
Architecturex86_64 (amd64)
KernelLinux 5.10.134 (LIFSEA container engine, based on Linux 5.10 LTS)

Preinstalled Tools

System Tools

ToolVersionDescription
git2.34+Version control
curl7.81+HTTP client
wget1.21+File download
jq1.6+JSON processing
vim8.2+Text editor
unzip / tarsystemArchive tools
sshOpenSSH 8.9+SSH client
make4.3+Build tool

Language Runtimes

LanguageVersionPackage manager
Python3.12.xpip 24+
Node.js20.x LTSnpm 10+
Go1.22.xgo mod

Package Managers

ToolDescription
aptSystem package management
pipPython packages
npmNode.js packages

Working Directory

/app
The Agent’s default cwd is /app. Note that $HOME points to /data (a different directory), so ~/ expands to /data, not the cwd. For uploaded file mount paths, see Files and Mounts.

Installing Extra Software

Use the Environment’s packages field to install additional dependencies:
{
  "config": {
    "packages": [
      "postgresql-client",
      "redis-tools",
      "ffmpeg"
    ]
  }
}
The container runs apt-get install for the listed packages on startup.
You can also instruct the Agent in its system prompt to install language packages with pip install or npm install.

Networking

Network access is governed by the Environment’s config.networking field (object form required):
TypeDescription
unrestrictedThe container can reach the public internet (default)
limitedOnly known-safe public services and package managers are reachable
allowed_hostsOnly the listed hosts are reachable
Example:
{
  "config": {
    "networking": {
      "type": "allowed_hosts",
      "allowed_hosts": [
        "api.github.com",
        "registry.npmjs.org"
      ]
    }
  }
}
See Cloud Environments — Networking Policies for the full field reference.

Resource Limits

ResourceDefault limitDescription
CPU4 vCPUAllocated processor cores
Memory8 GBAvailable RAM
Disk25 GBWorkspace storage (overlay filesystem, ~18 GB usable)
Execution time30 minutesMaximum duration of a single turn
When memory or disk limits are exceeded, the process is OOM-killed or writes fail. Consider reminding the Agent in the system prompt to be mindful of resource usage.

File Persistence

  • Within the same Session, files persist across turns.
  • When the Session ends (archived or deleted), the container and its files are destroyed.
  • For long-term persistence, upload files to platform storage via the Files API.

Execution User

All commands run as root inside the container. whoami returns root, but the USER environment variable is not set (empty string). Agents can install system packages and write to any system directory without sudo. If restrictions are needed, specify them in the Agent’s system prompt.

Environment Variables

Variables preset in the container:
VariableValueDescription
HOME/dataUser home directory (~/ expands here, different from cwd /app)
USER(not set, empty string)Note: the USER environment variable is not injected; use whoami to get the actual identity, which returns root
SHELL/bin/bashDefault shell
LANGen_US.UTF-8Locale
Vault credentials are injected as environment variables when you link a Vault to the Session.