This FAQ is written for the open-source Docker and SDK workflow.
Map the container to a different host port:
Then use http://localhost:3000 as the sandbox base URL.
Make sure the container has enough memory and that it is started with the recommended seccomp option:
If you run in a restricted container runtime, also check whether Chromium sandboxing or shared-memory limits need additional runtime flags.
Check that the base URL points to the host port you mapped:
Handle errors in layers:
success: false indicates a tool-level failure.status, exit_code, or stderr output.See Error Handling for the recommended pattern.
Check whether the page is fully loaded, whether the target element is visible, and whether the automation method matches your task. Use CDP or page APIs for DOM-level automation, and GUI actions for visual desktop-level interaction.
Chromium downloads normally land in the user downloads directory, such as /home/gem/Downloads. Use the file API to inspect or retrieve downloaded files.
No. AIO Sandbox exposes an aggregated MCP endpoint at /mcp. You can connect an MCP-compatible client directly to that endpoint.
The MCP endpoint focuses on commonly used tools by default. Prefer the documented browser APIs or high-level MCP tools unless you need low-level CDP behavior.
Build a custom image from the public AIO Sandbox image and install your packages in the Dockerfile. For runtime-only setup, use lifecycle hooks described in AIO Hooks.
Set WORKSPACE when starting the container. See Workspace.