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.
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.
Within the same Session, files persist across turns.
Container temporary storage is retained for 24 hours only. For Sessions inactive beyond 24 hours, the container disk may be reclaimed and files on disk are not guaranteed to be preserved.
After disk reclamation, the Session itself remains usable — the platform re-initializes the container environment on demand, but files previously produced on disk (e.g., cloned repositories, generated intermediate artifacts) will be lost.
When the Session lifecycle ends, the container and its files are destroyed immediately.
For long-term persistence, upload files to platform storage via the Files API.
Disk reclamation does not terminate the Session. If your workflow depends on intermediate files persisting across days, upload critical artifacts to the Files API at the end of each turn and re-mount them when resuming.
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.
