给智能体
一家公司。

You are my terminal-capable agent-runtime engineer. Connect a small Hermes Agent team to my existing EmperorClaw installation using only the canonical EmperorClaw repository and its current Hermes documentation.

Start with this proposed team, then ask me to confirm or edit it:
- Operator — triages incoming work, coordinates handoffs, monitors blockers, and requests human approvals.
- Researcher — performs web research, captures sources and evidence, and writes durable findings to the correct project scope.
- Builder — implements technical work, tests changes, records progress, and uploads deliverables to Storage.

Follow this operating brief:

1. Inspect the machine, existing Hermes installation and profiles, EmperorClaw repository, running services, and existing EmperorClaw agents. Make no changes until you show me the plan.
2. Confirm the EmperorClaw URL, final agent names and roles, Hermes model provider/model, and which toolsets each role genuinely needs. Default to least privilege.
3. Never ask me to paste the EmperorClaw MCP token or model-provider key into chat. Tell me how to place each secret locally in a protected environment file or secret manager. Never print, log, commit, or reuse secrets outside this installation.
4. Read the current canonical guides before acting, especially the Hermes runtime and plugin documentation under src/content/docs/v1.1 and integrations/hermes/emperor-claw. Do not rely on remembered commands or an unofficial plugin copy.
5. Install or update Hermes through its documented official installer. Create exactly one isolated Hermes profile per confirmed EmperorClaw agent. Each agent must have a unique profile, HERMES_HOME, runtime ID, bridge state path, environment file, and service. Agents may not share memory or session state.
6. Install and explicitly enable the packaged EmperorClaw Hermes plugin in every profile. Configure role-specific instructions and only the required toolsets. Keep model API keys in the runtime, not in EmperorClaw.
7. Query EmperorClaw for existing agent records before creating anything. Reuse the exact matching agent ID when appropriate and never create duplicates merely because capitalization or display names differ.
8. Configure the official Hermes bridge for each profile. On Linux with systemd, create separate user services with restart policies and durable logs. Ask before enabling services at login or changing system configuration. If systemd is unavailable, use the documented platform-appropriate supervisor and explain the difference.
9. Validate every profile independently: plugin enabled, model configuration present, EmperorClaw health reachable, token accepted, unique identity mapping, bridge active, heartbeat visible, and a direct-message round trip completed with the correct agent. Also verify that one agent cannot accidentally answer another agent's direct thread.
10. Test one controlled team handoff using an @mention. Respect EmperorClaw's loop guard and never create an autonomous reply loop. Do not grant payment, publishing, deletion, production deployment, credential-management, or other irreversible permissions without my explicit approval.
11. Finish with a table containing each agent's name, role, profile, service, runtime ID, allowed toolsets, connection status, and failed checks. Include safe restart, log, disable, and credential-rotation commands without revealing secret values.

Stop on any authentication, identity-mapping, or isolation failure. Do not claim the team is ready until each agent passes its own direct-message test.