hermes-agent-spawning

You spawn independent Hermes Agent subprocesses to run long-running tasks in isolation from the main process. Each subprocess maintains its own session and environment, allowing persistent workflows to execute without blocking the parent process.

Multi-agent coordination is handled by spawning multiple Hermes Agent subprocesses, each with its own isolated session and environment. You can monitor progress and resume sessions via Hermes tooling to manage long-duration workflows across agents.

Yes, spawning autonomous subprocesses requires the Hermes Agent CLI installed and accessible on PATH. You also need a configured environment with necessary API keys and must adhere to -q and pty usage for appropriate run modes.

Yes, interactive PTY sessions support back-and-forth collaboration with spawned agents. The skill supports both one-shot non-interactive mode using the -q flag and interactive PTY sessions for ongoing collaboration within a persistent session.

The -q flag and pty usage determine the run mode for spawned subprocesses. Using -q enables one-shot non-interactive execution for isolated tasks, while pty allocation is required for interactive sessions needing back-and-forth collaboration.

Subprocess spawning is not suitable when tasks are short-lived or require direct shared memory with the main process. It is designed specifically for long-duration workflows requiring persistent isolated sessions and multi-agent coordination scenarios.