Skip to content
BENIBIX Learn

Claude Agent SDK Hosting

AI🧩 Claude Agent SDKAgent SDK Deployment

Also known as Agent SDK Hosting, Hosting the Agent SDK, Agent SDK deployment

Running Agent SDK agents on your own servers. Each session is its own process.

Think of it like

It is like giving each helper a room. Each room has a desk for its papers.

Example

A team puts its agent in a Docker container. Each user gets a session. The chat files are copied out to a store, so a restart loses nothing.

Why it matters

Files on a container's disk vanish when it restarts. Planning for that early saves lost sessions later.

Definition

Agent SDK hosting is how you run Agent SDK agents on your own servers. Each session starts a Claude Code process that owns a shell, a folder and its chat files on disk. So it is not like a simple web API. Each agent is a process that lives a long time and keeps files. Most teams run it in a container, starting with about 1 GiB of memory, 5 GiB of disk and one CPU per agent.
Your app runs one Claude Code process for each session. A restart wipes its files.

Common mistake

Treating it like a stateless API. Each session is a process with files, and a restart wipes them.

Key takeaways

  1. 1
    One process per session. Claude Code runs inside.
  2. 2
    State on disk. Lost on restart.
  3. 3
    A container each. About 1 GiB to start.