refactor: consolidate Hermes into generic HTTP option in pair-agent

Hermes doesn't have a host-specific config — it uses the same generic
curl instructions as any other agent. Removing the dedicated option
simplifies the menu and eliminates a misleading distinction.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Garry Tan 2026-04-06 00:25:05 -07:00
parent 21f2a449eb
commit 2e3aeaf3ac
No known key found for this signature in database
GPG Key ID: C1F69E85C74EFE1D
2 changed files with 16 additions and 28 deletions

View File

@ -592,19 +592,17 @@ Use AskUserQuestion:
Options: Options:
- A) OpenClaw (local or remote) - A) OpenClaw (local or remote)
- B) Hermes (local or remote) - B) Codex / OpenAI Agents (local)
- C) Codex / OpenAI Agents (local) - C) Cursor (local)
- D) Cursor (local) - D) Another Claude Code session (local or remote)
- E) Another Claude Code session (local or remote) - E) Something else (generic HTTP instructions — use this for Hermes)
- F) Something else (generic HTTP instructions)
Based on the answer, set `TARGET_HOST`: Based on the answer, set `TARGET_HOST`:
- A → `openclaw` - A → `openclaw`
- B → `hermes` (if not in hosts registry, use generic) - B → `codex`
- C → `codex` - C → `cursor`
- D → `cursor` - D → `claude`
- E → `claude` - E → generic (no host-specific config)
- F → generic (no host-specific config)
## Step 3: Local or remote? ## Step 3: Local or remote?
@ -758,10 +756,6 @@ OpenClaw agents use the `exec` tool instead of `Bash`. The instruction block use
`exec curl` syntax which OpenClaw understands natively. When using `--local openclaw`, `exec curl` syntax which OpenClaw understands natively. When using `--local openclaw`,
credentials are written to `~/.openclaw/skills/gstack/browse-remote.json`. credentials are written to `~/.openclaw/skills/gstack/browse-remote.json`.
### Hermes
Hermes agents work the same way as OpenClaw. Use the generic instruction block
(option F) which provides standard curl commands that any agent can execute.
### Codex ### Codex

View File

@ -70,19 +70,17 @@ Use AskUserQuestion:
Options: Options:
- A) OpenClaw (local or remote) - A) OpenClaw (local or remote)
- B) Hermes (local or remote) - B) Codex / OpenAI Agents (local)
- C) Codex / OpenAI Agents (local) - C) Cursor (local)
- D) Cursor (local) - D) Another Claude Code session (local or remote)
- E) Another Claude Code session (local or remote) - E) Something else (generic HTTP instructions — use this for Hermes)
- F) Something else (generic HTTP instructions)
Based on the answer, set `TARGET_HOST`: Based on the answer, set `TARGET_HOST`:
- A → `openclaw` - A → `openclaw`
- B → `hermes` (if not in hosts registry, use generic) - B → `codex`
- C → `codex` - C → `cursor`
- D → `cursor` - D → `claude`
- E → `claude` - E → generic (no host-specific config)
- F → generic (no host-specific config)
## Step 3: Local or remote? ## Step 3: Local or remote?
@ -236,10 +234,6 @@ OpenClaw agents use the `exec` tool instead of `Bash`. The instruction block use
`exec curl` syntax which OpenClaw understands natively. When using `--local openclaw`, `exec curl` syntax which OpenClaw understands natively. When using `--local openclaw`,
credentials are written to `~/.openclaw/skills/gstack/browse-remote.json`. credentials are written to `~/.openclaw/skills/gstack/browse-remote.json`.
### Hermes
Hermes agents work the same way as OpenClaw. Use the generic instruction block
(option F) which provides standard curl commands that any agent can execute.
### Codex ### Codex