Step 1
Choose the install machine
Decide which always-on computer will host Hermes. Keep it on reliable power, a trusted private network, and at the location where it will normally operate.
🦞Claw Empire private client portal
Signed-client onboarding
Your step-by-step Hermes setup hub.
Start here if you are already signed with Claw Empire. Choose the install target, follow the visual pre-call steps, and arrive with the host, admin owner, password manager, and MFA path ready.
Client prep guideHermes fresh install
Follow these steps before your guided install call. This is prep for supported onboarding, not a self-serve setup wizard.
Signed-client useThis hub is for clients already scheduled for onboarding or active implementation.
Fresh installs are Hermes-onlyNew deployments use the current Hermes runtime, not a new OpenClaw install.
No pasted secretsUse OAuth, password-manager sharing, or screen-share entry during the install call.
Step 1
Choose the guide for the machine we will configure.
Each path is a sequential preparation guide with branded setup visuals. Use the one that matches the computer that will host Hermes.
macOS workstation
macOS step-by-step guide
Best fit for an always-on Mac mini in the client office or home office.
Open macOS guide →Windows 11 + WSL2
Windows step-by-step guide
Best fit when the client machine is Windows but the runtime should stay in a Linux environment.
Open Windows guide →Linux host
Linux step-by-step guide
Best fit for clients who already operate a stable Linux machine or server with clear admin ownership.
Open Linux guide →Step 3
Check policy and legacy boundaries.
Bring any constraints to the call so setup does not stall around device management, network controls, or legacy OpenClaw assumptions.
Before the call
- Decide which always-on computer will host Hermes. Keep it on reliable power, a trusted private network, and at the location where it will normally operate.
- Make sure the business owner or operator can approve access decisions and use an administrator account during the call.
- Keep MFA devices, password manager access, approved accounts, and off-limits systems ready. Do not send passwords, private keys, recovery keys, or tokens in chat or email.
- Use a private, trusted network. Avoid hotel, airport, café, and conference Wi-Fi for install day.
- Tell us before the call about device-management, firewall, VPN, antivirus, IP allowlisting, or vendor-review constraints.
Legacy boundary
Hermes for fresh installs.
Legacy OpenClaw support is diagnostic-only unless explicitly scoped. The legacy path is ~/.openclaw/. No alternate legacy directory applies.
If you are asking about an existing OpenClaw system, label it as a diagnostic request so we do not treat it as a fresh install path.
Step 4
Keep this agenda open on install day.
Expect a calm working session: verify the host, connect approved systems, test supervised workflows, and document the handoff.
Step 1
Confirm scope, owner, machine, and access boundary.
Step 2
Verify OS, network, shell, package manager, and remote access posture.
Step 3
Install and configure Hermes on your infrastructure.
Step 4
Connect approved accounts and integrations through secure OAuth or password-manager flows.
Step 5
Run supervised test workflows with clear approval gates.
Step 6
Document operating commands, recovery notes, and the handoff checklist.
After install
Launch supervised, then widen autonomy.
The best assistants become trusted by proving judgment under review. Start narrow, observe behavior, and expand permissions deliberately.
- Run Hermes in supervised mode first; treat the first week as calibration.
- Keep one owner responsible for policy: autonomous actions, confirmation-required actions, and off-limits systems.
- Store handoff notes, recovery steps, and account ownership in your internal docs or password manager.
- Rotate temporary credentials and remove temporary remote access that is not part of ongoing support.
Quick links
Keep the right guide open during setup.
🦞Claw Empire setup desk
Need a decision?
Ask before install day.
If a company policy, device constraint, or access question changes the plan, send it to your Claw Empire contact before the call. The goal is a prepared handoff, not last-minute privilege escalation.