Skip to main content

exec

How exec works in this workspace. Commands run in bash in a real Linux container, with Node.js, git and network access, and the workspace is synced in and out around each call. Read this before running commands, installing packages, or debugging files that don't show up where you expect.

소스 정보

저장소
cloudflare/computer
최근 소스 활동
2026년 10월 12일 14:03
감지된 SKILL.md 언어
영어
스타
9,835
포크
583

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
exec
description
How exec works in this workspace. Commands run in bash in a real Linux container, with Node.js, git and network access, and the workspace is synced in and out around each call. Read this before running commands, installing packages, or debugging files that don't show up where you expect.
# Running commands Every `exec` call runs your command with bash in a **Linux container**. The durable object starts the container, and a small daemon in it, `computerd`, runs the command. ## What's installed - Debian, with `bash`, `git`, `curl` and the usual core tools. - Node.js 22 and `npm`. - Anything else can be installed with `apt-get` or `npm`. It lasts until the container stops. ## Network The container has direct network access, so `npm install`, `git clone` and `curl` work. ## Files - `/workspace` in the container is the workspace. `cwd` defaults to it. - The durable object's storage holds the authoritative copy. Before each call, changes made outside the container are pushed into `/workspace`. After the call, changes made in the container are pulled back. Something written outside `/workspace` stays in the container and isn't saved. - `/workspace/.agents/skills` (where this file lives) is a read-only copy of files shipped with the Worker. Changes you make there in the container are dropped when the call ends. ## Things to know - The first call is slow, because the container has to boot. Later calls reuse it while it stays up. - A container that stops loses everything outside `/workspace`, including installed packages. Reinstall rather than assume they're still there. - Every file under `/workspace` is synced back to storage after each call. This example keeps no paths on the container's local disk, so a large `node_modules` or build folder under `/workspace` slows every call down. Put throwaway output in `/tmp`.
GitHub에서 보기