Hi Warp team,

I’m seeing inconsistent behavior between Gemini CLI and Hermes Chat / Hermes Agent inside Warp, and I think Hermes is not being detected or enhanced correctly as a third-party CLI agent.

Warp’s docs say supported CLI agents should be auto-detected and get the agent toolbelt, Rich Input, notifications, remote session control, etc. Rich Input should be available with Ctrl-G or from the bottom Rich Input button when a supported agent is running in the active pane. Remote Control is also exposed from the /remote-control chip in the agent utility bar for supported sessions.

What I expected

When I run Hermes Chat inside Warp, I expected behavior similar to Gemini CLI and other supported CLI agents:

• the bottom agent utility bar appears
• Rich Input is available
• /remote-control appears
• File Explorer / related Warp agent footer features appear
• the session feels like a properly integrated agent session inside Warp

What actually happens

When I run Gemini CLI in Warp, I get the expected Warp-enhanced experience. The bottom utility bar is visible and includes things like:

• /remote-control
• File explorer
• Rich Input

But when I run Hermes Chat, those Warp features do not appear. Instead:

• the bottom Warp agent utility bar is missing
• Rich Input is not available the same way
• /remote-control is missing
• the Hermes session feels like a generic terminal app rather than a supported/enhanced CLI agent
• the overall UX is worse because the pane ends up feeling much less usable than Gemini in the same Warp setup

Environment

• OS: Windows
• Shells reproduced from: PowerShell, Ubuntu / WSL

Reproduction steps

1. Open Warp.
2. Open either PowerShell or Ubuntu/WSL.
3. Run Gemini CLI and observe that Warp shows the expected agent footer / toolbelt.
4. In another pane/tab, run Hermes Chat.
5. Observe that Hermes does not get the same Warp agent UI/features.

Why I think this is a Warp issue

Warp documents “first-class support” / “universal agent support” for supported third-party CLI coding agents, including auto-detection, Rich Input, notifications, code review, and remote session control. The utility bar and Rich Input are supposed to activate when a supported agent is running in the active pane.

From a user point of view, Hermes appears to be missing that integration path entirely, while Gemini works correctly in the same Warp install on the same machine. That makes it look like one of these is happening:

• Hermes is not currently recognized as a supported third-party CLI agent
• Hermes detection fails because of how the command/process is launched
• Warp suppresses the toolbelt for Hermes because it behaves more like a TUI
• or Hermes support is incomplete compared with Gemini / Codex / Claude Code / OpenCode

Requested fix

Please investigate Hermes Chat support in Warp and either:

1. Add proper support/detection so Hermes gets the same Warp-enhanced CLI agent experience where technically possible, including:
   • agent utility bar
   • Rich Input
   • /remote-control
   • relevant footer tools/features
2. OR If Hermes is not currently supported, please document that clearly in the third-party CLI agent docs and explain what would be required for support.

What would count as fixed

This issue would feel fixed if Hermes Chat in Warp:

• is recognized as an agent session or supported CLI agent session
• shows the bottom agent toolbelt
• supports Rich Input via the button and/or Ctrl-G where applicable
• shows /remote-control where applicable
• behaves consistently across PowerShell and Ubuntu/WSL

Attachments

(Screenshots attached above showing Gemini CLI with expected footer/toolbelt vs Hermes Chat without it)