hermes-agent-spawning

To spawn isolated subprocesses for long-running autonomous tasks, launch independent Hermes Agent instances that run in separate processes with their own sessions, tools, and persistent logs. This ensures full process isolation and session persistence away from the parent workflow.

Multi-agent orchestration via subprocess spawning differs from lightweight delegation by providing full process isolation, dedicated terminal environments, and persistent context or DB logs for long-running missions, rather than sharing the parent session's execution environment.

Yes, hermes-agent-spawning supports interactive PTY sessions for multi-turn collaboration. It enables long-running tasks to operate in isolated subprocesses with dedicated terminal environments, alongside a non-interactive one-shot mode for autonomous execution.

Yes, you can run parallel subtasks across independent agent sessions using subprocess isolation. Spawning separate Hermes Agent instances allows each parallel subtask to maintain its own persistent context, tools, and logs independently.

You need to spawn isolated agents for multi-agent coordination when executing long-running missions that require clear separation from the parent workflow, persistent session logs, and independent process deployment to prevent context interference.

Yes, non-interactive one-shot mode works for spawning autonomous agents in separate subprocesses. It satisfies the requirement for running long-running tasks autonomously without interactive PTY input, while maintaining persistent logs and process isolation.