Skip to main content
MeshAgent publishes base images so you can package and ship agents/services quickly without building every dependency from scratch.

​
Where to Pull

​
Image Catalog

​
How to Choose

  • Use meshagent/cli when the container should start directly into the meshagent CLI and join a room as a process, meeting transcriber, or VoiceBot.
  • Use meshagent/cli-playwright only when that same CLI-style container also needs bundled Playwright browsers.
  • Use meshagent/python or meshagent/node when you want a slimmer language runtime base and will install your own app dependencies.
  • Use meshagent/python-sdk-slim, meshagent/python-sdk, or meshagent/node-sdk when you want MeshAgent packages or workspace scaffolding already present.
  • Use meshagent/shell when you want a shell-first utility image with common Linux tooling instead of the lean CLI runtime.

​
Prewarmed Room Images

In MeshAgent cloud rooms, the room host precaches these image refs at startup so the first use is already warm:
  • meshagent/cli:default
  • meshagent/python:default
  • meshagent/node:default
  • meshagent/python-sdk:default
  • meshagent/python-sdk-slim:default
  • meshagent/node-sdk:default
If one of those images fits your runtime, use it first. In practice:
  • Use meshagent/cli:default for most CLI, process, meeting-transcriber, or VoiceBot containers that do not need bundled browser automation.
  • Use meshagent/python:default when you want a slim Python runtime and will install or layer your own app dependencies.
  • Use meshagent/python-sdk-slim:default or meshagent/python-sdk:default when you want MeshAgent Python packages preinstalled.
  • Use meshagent/node:default or meshagent/node-sdk:default for JS/TS runtimes depending on whether you want a plain runtime or the SDK workspace scaffold.
Images such as meshagent/cli-playwright, meshagent/shell, meshagent/dotnet-sdk, and meshagent/flutter are still published, but they are not part of the default cloud-room precache list today. For those images, and for custom images, the -esgz variants still matter more for cold-start performance.

​
Tags & Cold Starts

  • Tags: use :default inside MeshAgent manifests and room workflows when you want MeshAgent to resolve the image to the runtime-recommended tag for the current server version. You can also pin explicit version tags (for example 0.8.x) when you want an exact image version.
  • Stargz: every base image also has a *-esgz variant. In MeshAgent cloud rooms these matter most for custom images and for stock images outside the prewarmed set above. On environments without the stargz snapshotter they still run normally, just without the lazy-pull speedup. If you are building your own container we recommend creating a stargz-optimized image, because that is still the main way to improve cold-start pull time for custom images.
  • Platform: images are published for linux/amd64.
  • Using Containers: Learn how to run containers through the MeshAgent Containers API. This is very helpful for running code on demand inside a Room.
  • Optimizing Containers: Learn how to optimize your container when deploying a custom service.