Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.meshagent.com/llms.txt

Use this file to discover all available pages before exploring further.

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

​
Where to Pull

​
Image Catalog

ImageBest forWhat’s insideNotes
meshagent/cliProcess-backed CLI agents, meeting transcribers, and VoiceBot containers that do not need in-container browser automationA lean runtime image with the prebuilt meshagent binary as the entrypointUse this when you want the CLI runtime itself, not a general-purpose Linux shell image. Typically you run meshagent process join ..., meshagent meeting-transcriber join ..., or meshagent voicebot join ....
meshagent/cli-playwrightCLI agents that need bundled Playwright or Stagehand browser automation inside the containermeshagent/cli plus Playwright, downloaded browser binaries, Xvfb, fonts, and browser runtime librariesUse this only when the container itself launches Playwright-managed browsers. If you do not need browser automation, prefer meshagent/cli.
meshagent/pythonMinimal Python runtime base for custom images and runtime-label deploy flowsPython 3.13 slim runtime with a standard virtualenv path preconfigured on PATHUse this when you want a clean Python base and will install your own dependencies or let MeshAgent layer your code on top at deploy time. This is not the same image as meshagent/python-sdk.
meshagent/python-sdk-slimStandard Python agents and services that want core MeshAgent Python packages preinstalled without the heavier optional integrationsmeshagent/python plus uv and the core MeshAgent Python packages: API, Agents, Tools, OpenAI, and OTELRecommended starting point for most Python services when you want MeshAgent packages preinstalled but do not need the broader integration set.
meshagent/python-sdkPython services that want the fuller preinstalled MeshAgent Python stackmeshagent/python-sdk-slim plus Codex, Computers, LiveKit, MarkItDown, MCP, and Anthropic packagesUse this when you want the broader MeshAgent Python package set already in the image. If you only need a base runtime, use meshagent/python instead.
meshagent/shellShell-based tools, utility containers, and developer-style agents that need a Bash entrypoint and common Linux toolsPython 3.13 slim, a Python virtualenv with selected MeshAgent packages, and common Linux tools such as git, curl, ripgrep, tree, and tcpdumpThis is the better fit when you want an interactive shell-style container rather than the lean meshagent CLI binary image.
meshagent/nodeMinimal JS/TS runtime base for custom Node servicesA plain Node runtime imageUse this when you want a bare Node base and will install or copy your own application code yourself. This is not the same image as meshagent/node-sdk.
meshagent/node-sdkJS/TS services using the MeshAgent Node workspace scaffoldNode runtime plus the meshagent-entrypoint and meshagent-ts workspace scaffoldPreferred Node SDK image when you want the MeshAgent TS workspace already present. Also published with the compatibility tag meshagent/nodejs-sdk.
meshagent/dotnet-sdk.NET servicesThe latest .NET SDK image with the meshagent-dotnet source tree copied into the workspaceUse this as a build base when you want the MeshAgent .NET SDK source already available in the image.
meshagent/flutterFlutter and Dart UI buildsFlutter SDK image with the meshagent-dart, meshagent-flutter, and meshagent-flutter-shadcn workspace packages copied inUse this when you are building or publishing Flutter-based UIs or packages on top of the MeshAgent Flutter workspace.

​
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.