Sandbox Runtime
Every user gets an isolated, persistent sandbox environment that survives restarts.Persistence
Unlike ephemeral sandboxes, Myrm sandboxes retain:- Installed packages and tools
- File system state
- Environment configuration
- Running processes (with auto-restart)
Isolation
Each sandbox runs in an isolated container with:- Dedicated filesystem volume
- Network namespace isolation
- Resource limits (CPU, memory, disk)
- Security policies enforced at runtime
- UI Interaction Blacklisting: For sub-agents running in the background, the sandbox blocks UI interfaces (
interactive_feedback,send_message), ensuring they can never interrupt the user with popups, providing true physical isolation between background tasks and foreground user interaction.
Code Execution
Agents can execute code directly in the sandbox:- Python, Node.js, shell scripts
- Package installation via pip, npm, apt
- File read/write operations
- Network access (configurable)