TypeScript SDK

The TypeScript SDK is published as @rlp/sdk. It mirrors the official Daytona SDK's TypeScript surface (class names, method names, error types), so most Daytona code ports by changing the import. All methods are async and fully typed.

Install

npm install @rlp/sdk

Configure

Construct a Daytona client with an optional config object. Every field falls back to environment variables — an explicit config value wins, then RLP_*, then DAYTONA_* where a fallback exists.

import { Daytona } from '@rlp/sdk'
 
// Explicit configuration
const daytona = new Daytona({
  apiUrl: 'https://api.example.com',
  apiKey: 'rlp_...',
  toolboxUrl: 'https://proxy.example.com/toolbox',
})
 
// Or rely entirely on environment variables
const daytona = new Daytona()

The constructor throws DaytonaValidationError if no API URL can be resolved, and DaytonaAuthenticationError if no API key can be resolved. If no toolbox URL is available from any source, sandbox operations that need it throw DaytonaValidationError at that point. API keys are covered under Authentication.

Quick example

Create a sandbox, run a command in it, then delete it:

import { Daytona } from '@rlp/sdk'
 
const daytona = new Daytona()
 
const sandbox = await daytona.create({ image: 'node:22-slim' })
try {
  const result = await sandbox.process.executeCommand('node -e "console.log(6 * 7)"')
  console.log(result.exitCode) // 0
  console.log(result.result)   // 42
} finally {
  await sandbox.delete()
}

See the quickstart for a longer walkthrough.

Reference pages

• Daytona (client) — sandbox CRUD, lifecycle helpers, service accessors
• Sandbox — lifecycle, fork, previews, VM-state snapshots
• Process — command execution, code runs, sessions
• FileSystem — file operations inside the sandbox
• Git — git operations inside the sandbox
• SnapshotService — image aliases and Dockerfile builds
• VolumeService — persistent volumes
• ObjectStoreService — S3-compatible bucket mounts
• SecretService — project secrets
• Errors — the error hierarchy