hermes-agent-spawning

To run long-running tasks as autonomous subprocesses, you can spawn independent Hermes Agent processes with dedicated sessions and full tool access. Each process operates in isolation, logging its own history to the database without sharing context with the parent process.

Agent orchestration for multi-turn collaborations involves spawning independent Hermes Agent subprocesses to manage complex, long-running tasks. It enables session resumption and background autonomous work while maintaining isolated execution environments for each agent.

Yes, you can interactively steer an agent during background execution using PTY interactive mode. This mode supports back-and-forth prompts and steering during execution, allowing you to guide the autonomous subprocess as it works.

Yes, you need the Hermes CLI installed and configured to spawn autonomous agents. The Skill relies on launching separate hermes CLI processes to handle long-running tasks with isolated sessions and lifecycle management.

Yes, one-shot mode works for non-interactive agent execution using the -q flag. It allows you to launch a Hermes Agent subprocess for single-turn tasks, contrasting with PTY interactive mode for back-and-forth collaboration.

Each spawned agent needs an isolated session to ensure independent execution and prevent context sharing with the parent process. Each subprocess logs its own history to the database, enabling concurrent long-running tasks without interference.