Introduction

Wisps gives you isolated Linux machines that you can create and use through an SDK, HTTP API, CLI, or MCP client. Run commands, work with files, and reconnect to interactive sessions.

Each machine is called a wisp. Choose an ephemeral sandbox for a single task, or a persistent workspace for ongoing work.

Start building

Start here	What you will do
Quickstart	Create a sandbox and run your first command using HTTP
Go · Python · TypeScript	Use Wisps from your application
MCP integration	Give a coding agent sandbox tools
API reference	Explore requests, responses, and schemas

What you need

Your Wisps provider supplies an API URL and access to a team. Use that URL throughout these docs; https://api.example.com is a placeholder.

Create a team API token for application code. Keep tokens in environment variables or your secret manager. See authentication.

Choose the right lifecycle

New API and SDK wisps default to ephemeral: they stop when idle, have a limited lifetime, and delete themselves after stopping. Use a person token to create an on-demand or always workspace when you need to keep it.

Files survive a stop and start. Running processes and memory do not. Deleting a wisp deletes its disk and checkpoints. See lifecycle and persistence.