Skip to main content
Manage your container lifecycle.

​
Get session status

GET /session
Returns the current state of your container: 
{
  "status": "running",
  "container_id": "user-abc123",
  "hostname": "abc123.fleet.easyclaw.app",
  "created_at": "2024-01-15T10:30:00Z",
  "plan": "pro"
}
Possible status values:
StatusDescription
runningContainer is active and processing messages
frozenContainer is suspended (zero CPU usage)
spawningContainer is being created
noneNo container exists for this user

​
Spawn a container

POST /session/spawn
Creates a new container from the template. If a container already exists, returns an error. Request body: 
{
  "provider": "anthropic",
  "model": "claude-sonnet-4-20250514"
}
Response: 
{
  "status": "spawning",
  "container_id": "user-abc123",
  "hostname": "abc123.fleet.easyclaw.app"
}
The container takes a few seconds to be ready. Poll GET /session until status is running.

​
Freeze a container

POST /session/freeze
Suspends all processes in the container. State is preserved — messaging bridges, files, and memory survive.

​
Restore a container

POST /session/restore
Resumes a frozen container. All processes pick up where they left off.

​
Kill a container

POST /session/kill
Permanently destroys the container. All data is wiped. A new spawn call is needed to start fresh.
Killing a container is irreversible. All files, conversation history, memory, and channel credentials in the container are permanently deleted.