Reusable Hermes profile distributions for agents running on Edka clusters.
- conductor — orchestrates Edka Codex environments from chat: implements features in coding environments, reviews pull requests in fresh read-only environments, and iterates until the work is approved. Requires a Hermes agent with Conductor enabled in its Edka settings and an installed Codex agent as the target.
Each profile is a Hermes profile distribution rooted at profiles/<name>/; the profile takes its name from distribution.yaml.
Via Edka: when deploying a Hermes agent, set Bootstrap to Profile distribution and pick a Profile. Published profiles (Edka Conductor) prefill the source; Custom repository takes this repository's URL and a Distribution Subpath (e.g. profiles/conductor). The profile is installed once, on first boot, alongside the agent's default profile. Update it later from the agent's Profiles tab with Update profile distribution.
By hand, on a running agent:
git clone https://github.com/edkadigital/agent-profiles /tmp/agent-profiles
hermes profile install /tmp/agent-profiles/profiles/conductorDistribution updates replace SOUL.md, skills/, and scripts/ from the source; config.yaml and everything user-owned (memories, sessions, .env) are preserved on update.
- A Codex agent installed on the cluster with environments configured (pinned version, environment domain, auth).
- The Hermes agent's Conductor tab enabled, with the target Codex agent selected and either Allow All Repositories or an explicit allowlist.
EDKA_MCP_URL,EDKA_MCP_GRANT_URL, andEDKA_MCP_TOKENpresent in the pod environment (the Edka chart injects them once Conductor is enabled; a pending pod restart is the usual reason they are missing).- Messaging access controlled at the agent level: set Gateway Allowed Users in the agent's Configuration tab. Fail closed; do not run a conductor open to a whole workspace. On chart 0.5.11+, chat platforms bind to the bootstrapped profile automatically.