feat(agent): let orchestrator profiles control other Hermes agent profiles via ACP#14009
Closed
dodo-reach wants to merge 1 commit into
Closed
feat(agent): let orchestrator profiles control other Hermes agent profiles via ACP#14009dodo-reach wants to merge 1 commit into
dodo-reach wants to merge 1 commit into
Conversation
Collaborator
Collaborator
1 similar comment
Collaborator
Contributor
Author
|
Thanks for linking #9459 and #11169. This PR is meant as a complementary control-plane piece: those changes improve in-process delegation, while this PR adds a standalone ACP session client so one Hermes profile can act as an orchestrator and directly control other Hermes profiles as persistent peer agents across reusable sessions. |
bac6a50 to
e4e480f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
scripts/hermes-session-client.pyreference client for Hermes ACP sessionsinitializeWhy
Hermes already has profiles, ACP server mode, and nested delegation. What was still missing was a small, protocol-correct bridge that lets a Hermes profile directly control other Hermes profiles as peer agents.
This adds that bridge.
In practice, this unlocks a new Hermes usage pattern: one profile can serve as the orchestrator while other profiles act as specialized agents with their own config, SOUL, memory, sessions, and tools. The orchestrator can open fresh sessions, resume prior ones, continue conversations, fork threads, and iterate on delegated work across those other profiles.
That makes Hermes profiles usable not just as isolated personas, but as a coordinated multi-profile agent system.
Relation to #9459 and #11169
This PR is complementary to the
delegate_task(profile=...)work in #9459 and #11169, but it solves a different layer of the problem.#9459/#11169focus on in-process delegation: Hermes usesdelegate_task(profile=...)to spawn or route work to a profile-backed child worker.So the distinction is:
delegate_task(profile=...)improves delegation inside Hermes' existing subagent flowhermes-session-client.pyenables a profile-level orchestrator to directly manage other Hermes agent profiles across reusable ACP sessionsThis PR intentionally does not change
delegate_task, tool routing, or delegation semantics. It adds a standalone ACP session client that builds on Hermes' current ACP and profile architecture to unlock profile-to-profile orchestration cleanly.Testing
venv/bin/python -m pytest tests/scripts/test_hermes_session_client.py -qvenv/bin/python -m pytest tests/acp/test_server.py tests/acp/test_session.py -qNotes
This PR intentionally keeps the scope narrow:
delegate_taskflow