autoresearchclaw-must-run-in-isolated-container-not-hermes
AutoResearchClaw generates and executes arbitrary experiment code in its 23-stage pipeline. This code MUST run in a sandboxed container separate from oracle-hermes — never pip-installed into Hermes’s Python environment. The integration pattern is a dedicated ‘researchclaw’ container on oracle-network using Docker-in-Docker or host Docker socket for its own experiment sandbox. Coupling it with Hermes risks dependency conflicts and exposes the orchestrator to generated code execution.
Related
- autoresearchclaw-requires-dedicated-container-for-sandbox
- autoresearchclaw-requires-dedicated-container-for-experiment
- researchclaw-dedicated-container-oracle-network-deployment
- oracle
- docker
- researchclaw-container-requires-docker-socket-for-experiment
- autoresearchclaw-requires-dedicated-container-sandbox
- researchclaw-dedicated-container-required-for-sandbox
- oracle-container-naming-follows-oracle-prefix-on-oracle-netw
- researchclaw-dedicated-container-mandatory-for-experiment-sa
- researchclaw-container-isolation-required-for-experiment-cod
- researchclaw-must-run-in-dedicated-container-for-experiment
- researchclaw-requires-dedicated-container-with-docker-socket
- researchclaw-dedicated-container-required-for-experiment-san
- researchclaw-must-run-in-dedicated-container-for-sandboxing