This guide shows you how to execute commands in the sandbox, handle output, and manage errors effectively.
The SDK provides multiple approaches for running commands:
exec()- Run a command and wait for complete result. Best for one-time commands like builds, installations, and scripts.execStream()- Stream output in real-time. Best for long-running commands where you need immediate feedback.startProcess()- Start a background process. Best for web servers, databases, and services that need to keep running.
Use exec() for simple commands that complete quickly:
import { getSandbox } from "@cloudflare/sandbox";
const sandbox = getSandbox(env.Sandbox, "my-sandbox");
// Execute a single command
const result = await sandbox.exec("python --version");
console.log(result.stdout); // "Python 3.11.0"
console.log(result.exitCode); // 0
console.log(result.success); // trueimport { getSandbox } from '@cloudflare/sandbox';
const sandbox = getSandbox(env.Sandbox, 'my-sandbox');
// Execute a single command
const result = await sandbox.exec('python --version');
console.log(result.stdout); // "Python 3.11.0"
console.log(result.exitCode); // 0
console.log(result.success); // trueWhen passing user input or dynamic values, avoid string interpolation to prevent injection attacks:
// Unsafe - vulnerable to injection
const filename = userInput;
await sandbox.exec(`cat ${filename}`);
// Safe - use proper escaping or validation
const safeFilename = filename.replace(/[^a-zA-Z0-9_.-]/g, "");
await sandbox.exec(`cat ${safeFilename}`);
// Better - write to file and execute
await sandbox.writeFile("/tmp/input.txt", userInput);
await sandbox.exec("python process.py /tmp/input.txt");// Unsafe - vulnerable to injection
const filename = userInput;
await sandbox.exec(`cat ${filename}`);
// Safe - use proper escaping or validation
const safeFilename = filename.replace(/[^a-zA-Z0-9_.-]/g, '');
await sandbox.exec(`cat ${safeFilename}`);
// Better - write to file and execute
await sandbox.writeFile('/tmp/input.txt', userInput);
await sandbox.exec('python process.py /tmp/input.txt');Commands can fail in two ways:
- Non-zero exit code - Command ran but failed (result.success === false)
- Execution error - Command couldn't start (throws exception)
try {
const result = await sandbox.exec("python analyze.py");
if (!result.success) {
// Command failed (non-zero exit code)
console.error("Analysis failed:", result.stderr);
console.log("Exit code:", result.exitCode);
// Handle specific exit codes
if (result.exitCode === 1) {
throw new Error("Invalid input data");
} else if (result.exitCode === 2) {
throw new Error("Missing dependencies");
}
}
// Success - process output
return JSON.parse(result.stdout);
} catch (error) {
// Execution error (couldn't start command)
console.error("Execution failed:", error.message);
throw error;
}try {
const result = await sandbox.exec('python analyze.py');
if (!result.success) {
// Command failed (non-zero exit code)
console.error('Analysis failed:', result.stderr);
console.log('Exit code:', result.exitCode);
// Handle specific exit codes
if (result.exitCode === 1) {
throw new Error('Invalid input data');
} else if (result.exitCode === 2) {
throw new Error('Missing dependencies');
}
}
// Success - process output
return JSON.parse(result.stdout);
} catch (error) {
// Execution error (couldn't start command)
console.error('Execution failed:', error.message);
throw error;
}The sandbox supports shell features like pipes, redirects, and chaining:
// Pipes and filters
const result = await sandbox.exec('ls -la | grep ".py" | wc -l');
console.log("Python files:", result.stdout.trim());
// Output redirection
await sandbox.exec("python generate.py > output.txt 2> errors.txt");
// Multiple commands
await sandbox.exec("cd /workspace && npm install && npm test");// Pipes and filters
const result = await sandbox.exec('ls -la | grep ".py" | wc -l');
console.log('Python files:', result.stdout.trim());
// Output redirection
await sandbox.exec('python generate.py > output.txt 2> errors.txt');
// Multiple commands
await sandbox.exec('cd /workspace && npm install && npm test');// Run inline Python
const result = await sandbox.exec('python -c "print(sum([1, 2, 3, 4, 5]))"');
console.log("Sum:", result.stdout.trim()); // "15"
// Run a script file
await sandbox.writeFile(
"/workspace/analyze.py",
`
import sys
print(f"Argument: {sys.argv[1]}")
`,
);
await sandbox.exec("python /workspace/analyze.py data.csv");// Run inline Python
const result = await sandbox.exec('python -c "print(sum([1, 2, 3, 4, 5]))"');
console.log('Sum:', result.stdout.trim()); // "15"
// Run a script file
await sandbox.writeFile('/workspace/analyze.py', `
import sys
print(f"Argument: {sys.argv[1]}")
`);
await sandbox.exec('python /workspace/analyze.py data.csv');Set a maximum execution time for commands to prevent long-running operations from blocking indefinitely.
Pass timeout in the options to set a timeout for a single command:
const result = await sandbox.exec("npm run build", {
timeout: 30000, // 30 seconds
});const result = await sandbox.exec('npm run build', {
timeout: 30000 // 30 seconds
});Set a default timeout for all commands in a session with commandTimeoutMs:
const session = await sandbox.createSession({
commandTimeoutMs: 10000, // 10s default for all commands
});
await session.exec("npm install"); // Times out after 10s
await session.exec("npm run build"); // Times out after 10s
// Per-command timeout overrides the session default
await session.exec("npm test", { timeout: 60000 }); // 60s for this commandconst session = await sandbox.createSession({
commandTimeoutMs: 10000 // 10s default for all commands
});
await session.exec('npm install'); // Times out after 10s
await session.exec('npm run build'); // Times out after 10s
// Per-command timeout overrides the session default
await session.exec('npm test', { timeout: 60000 }); // 60s for this commandSet the COMMAND_TIMEOUT_MS environment variable to define a global default timeout for every exec() call across all sessions.
When multiple timeouts are configured, the most specific value wins:
- Per-command
timeoutonexec()(highest priority) - Session-level
commandTimeoutMsoncreateSession() - Global
COMMAND_TIMEOUT_MSenvironment variable (lowest priority)
If none are set, commands run without a timeout.
- Check exit codes - Always verify
result.successandresult.exitCode - Validate inputs - Escape or validate user input to prevent injection
- Use streaming - For long operations, use
execStream()for real-time feedback - Use background processes - For services that need to keep running (web servers, databases), use the Background processes guide instead
- Handle errors - Check stderr for error details
Verify the command exists in the container:
const check = await sandbox.exec("which python3");
if (!check.success) {
console.error("python3 not found");
}const check = await sandbox.exec('which python3');
if (!check.success) {
console.error('python3 not found');
}Use absolute paths or change directory:
// Use absolute path
await sandbox.exec("python /workspace/my-app/script.py");
// Or change directory
await sandbox.exec("cd /workspace/my-app && python script.py");// Use absolute path
await sandbox.exec('python /workspace/my-app/script.py');
// Or change directory
await sandbox.exec('cd /workspace/my-app && python script.py');- Commands API reference - Complete method documentation
- Background processes guide - Managing long-running processes
- Streaming output guide - Advanced streaming patterns
- Code Interpreter guide - Higher-level code execution