mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-11-18 20:04:07 +03:00
d99af4187b
The Singularity/Apptainer backend (tools/environments/singularity.py) now ships as the official 'singularity' plugin in NousResearch/hermes-official-plugins, registered through the terminal-environment provider seam under the same backend name and config keys (terminal.backend: singularity, terminal.singularity_image / TERMINAL_SINGULARITY_IMAGE, terminal.container_*). - 'singularity' leaves BUILTIN_BACKEND_NAMES so the plugin can register it; every hardcoded classification set drops it (the provider declares is_remote/is_container/supports_streams instead). - LEFT_CORE gains a singularity row: homes whose terminal.backend (or .env TERMINAL_ENV) is singularity get the catalog plugin once, on hermes update or agent/gateway start. An unknown-backend error for 'singularity' names the install command (new row field terminal_backend). - A plugin backend receives its per-task '<backend>_image' override; batch runs register one for the active backend. - BaseEnvironment's sudo-probe knob is renamed _passwordless_sudo_probe_supported: plugin backends set it, and the old spelling trips the install scanner. - Core's scratch-dir disk warning and process-exit sweep were Singularity-only and move to the plugin; the singularity setup row, dashboard probe/row and config defaults/bridges go too. Docs point at the plugin.
9 lines
419 B
Python
9 lines
419 B
Python
"""Hermes execution environment backends: one BaseEnvironment ABC for running shell commands
|
|
in a specific context (local, Docker, SSH, Modal direct/Nous-managed, Daytona, Vercel Sandbox;
|
|
plugin backends register through ``agent.terminal_env_registry``). ``terminal_tool._create_environment``
|
|
selects the backend from TERMINAL_ENV."""
|
|
|
|
from tools.environments.base import BaseEnvironment
|
|
|
|
__all__ = ["BaseEnvironment"]
|