This library provides convenient access to the Runloop SDK & REST API from server-side TypeScript or JavaScript.
The additional documentation guides can be found at docs.runloop.ai. The full API of this library can be found in api.md.
The RunloopSDK is the recommended, modern way to interact with the Runloop API. It provides high-level object-oriented interfaces for common operations while maintaining full access to the underlying REST API through the .api property.
npm install @runloop/api-client
Here's a complete example that demonstrates the core SDK functionality:
import { RunloopSDK } from '@runloop/api-client';
const sdk = new RunloopSDK({
bearerToken: process.env.RUNLOOP_API_KEY, // This is the default and can be omitted
});
// Create a new devbox and wait for it to be ready
const devbox = await sdk.devbox.create();
// Execute a synchronous command
const result = await devbox.cmd.exec({ command: 'echo "Hello, World!"' });
console.log('Output:', await result.stdout()); // "Hello, World!"
console.log('Exit code:', result.exitCode); // 0
// Start a long-running HTTP server asynchronously
const serverExec = await devbox.cmd.execAsync({
command: 'npx http-server -p 8080',
});
console.log(`Started server with execution ID: ${serverExec.executionId}`);
// Check server status
const state = await serverExec.getState();
console.log('Server status:', state.status); // "running"
// Later... kill the server when done
await serverExec.kill();
await devbox.shutdown();
The main SDK class that provides access to all Runloop functionality construct view the RunloopSDK documentation to see specific capabilities.
The SDK provides object-oriented interfaces for all major Runloop resources:
runloop.devbox - Devbox management (create, list, execute commands, file operations)runloop.blueprint - Blueprint management (create, list, build blueprints)runloop.snapshot - Snapshot management (list disk snapshots)runloop.storageObject - Storage object management (upload, download, list objects)runloop.api - Direct access to the REST API clientThe SDK is fully typed with comprehensive TypeScript definitions:
import { RunloopSDK, type DevboxView } from '@runloop/api-client';
const runloop = new RunloopSDK();
const devbox: DevboxView = await runloop.devbox.create();
If you're currently using the legacy API, migration is straightforward:
All of the runloop client methods runloop.secrets has moved to runloopSDK.api.secrets. Updating all references to this will move to the new sdk client.
// Before (Legacy api client)
import Runloop from '@runloop/api-client';
const runloop = new Runloop();
const secretResult = await runloop.secrets.create({ ... });
// After (SDK)
import { RunloopSDK } from '@runloop/api-client';
const runloop = new RunloopSDK();
const secretResult = await runloop.api.secrets.create({ ... });
Once you've migrated your existing code to the new SDK client you can optionally go through and move from the API paradime to the object oriented SDK.
// Before (Legacy api client)
import Runloop from '@runloop/api-client';
const runloop = new Runloop()
const devboxResult = await runloop.devboxes.createAndAwaitRunning()
await runloop.devboxes.executeAndAwaitCompletion(devboxResult.id, {"command": "touch example.txt"})
const snapshotResult = await runloop.devbox.snapshotDisk()
await runloop.devboxes.snapshotDisk(devboxResult.id)
await runloop.snapshots.awaitCompleted(snapshotResult.id)
runloop.devbox.create({ snapshot_id: snapshotResult.id})
...
await runloop.devbox.shutdown(devboxResult.id)
// After (SDK)
import { RunloopSDK } from '@runloop/api-client';
const runloop = new RunloopSDK();
const devbox = await runloop.devbox.create();
await devbox.cmd.exec({ command: "touch example.txt" });
const snapshot = await devbox.snapshotDisk();
await snapshot.createDevbox();
...
await devbox.shutdown();
Customize the SDK with your API token, endpoint, timeout, and retry settings:
const runloop = new RunloopSDK({
bearerToken: process.env.RUNLOOP_API_KEY,
timeout: 60000, // 60 second timeout
maxRetries: 3, // Retry failed requests
});
The SDK provides comprehensive error handling with typed exceptions:
try {
const devbox = await runloop.devbox.create();
const result = await devbox.cmd.exec({ command: 'invalid-command' });
} catch (error) {
if (error instanceof RunloopSDK.APIError) {
console.log('API Error:', error.status, error.message);
} else if (error instanceof RunloopSDK.APIConnectionError) {
console.log('Connection Error:', error.message);
} else {
console.log('Unexpected Error:', error);
}
}
You may also provide a custom fetch function when instantiating the client,
which can be used to inspect or alter the Request or Response before/after each request:
import { fetch } from 'undici'; // as one example
import { RunloopSDK } from '@runloop/api-client';
const runloop = new RunloopSDK({
fetch: async (url: RequestInfo, init?: RequestInit): Promise<Response> => {
console.log('About to make a request', url, init);
const response = await fetch(url, init);
console.log('Got response', response);
return response;
},
});
Note that if given a DEBUG=true environment variable, this library will log all requests and responses automatically.
This is intended for debugging purposes only and may change in the future without notice.
By default, this library uses a stable agent for all http/https requests to reuse TCP connections, eliminating many TCP & TLS handshakes and shaving around 100ms off most requests.
If you would like to disable or customize this behavior, for example to use the API behind a proxy, you can pass an httpAgent which is used for all requests (be they http or https), for example:
// Configure the default for all requests:
const runloop = new RunloopSDK({
httpAgent: new HttpsProxyAgent(process.env.PROXY_URL),
});
// Override per-request:
await runloop.devboxes.create({...}, {
httpAgent: new http.Agent({ keepAlive: false }),
});
This package generally follows SemVer conventions, though certain backwards-incompatible changes may be released as minor versions:
We take backwards-compatibility seriously and work hard to ensure you can rely on a smooth upgrade experience.
We are keen for your feedback; please open an issue with questions, bugs, or suggestions.
TypeScript >= 4.5 is supported.
The following runtimes are supported:
"node" environment ("jsdom" is not supported at this time).Note that React Native is not supported at this time.
If you are interested in other runtime environments, please open or upvote an issue on GitHub.