Skip to content

fix(bridge): detect hermes chat with global flags in bridge status check#1917

Open
lb1192176991-lab wants to merge 1 commit into
MemTensor:mainfrom
lb1192176991-lab:fix/bridge-hermes-global-flags
Open

fix(bridge): detect hermes chat with global flags in bridge status check#1917
lb1192176991-lab wants to merge 1 commit into
MemTensor:mainfrom
lb1192176991-lab:fix/bridge-hermes-global-flags

Conversation

@lb1192176991-lab

Copy link
Copy Markdown

Fixes #1915

The isHermesChatRunning() function in bridge.cts uses pgrep -f "hermes chat" which fails when global flags are placed before the subcommand (e.g., hermes --skills memory-routing chat).

Changed the pattern to a regex "hermes\\s.*chat\\b" that matches:

  • hermes chat (adjacent)
  • hermes --flags chat (global flags before subcommand)
  • hermes chat --flags (flags after subcommand, already worked)

Fixes MemTensor#1915

The `isHermesChatRunning()` function in bridge.cts uses pgrep with a fixed string pattern that fails when global flags are placed before the subcommand. Changed to a regex pattern that matches both `hermes chat` and `hermes --flags chat`.
@lb1192176991-lab lb1192176991-lab force-pushed the fix/bridge-hermes-global-flags branch from 681d108 to 4587d66 Compare June 12, 2026 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix(memos-local-plugin): bridge status detection misses hermes chat with global flags

1 participant