Issue Station
Sign In
Tools hereToolbox

hermes - ✅(Solved) Fix Memory UI dashboard local_embedded fails to auto-start Hindsight when hindsight-embed is not on PATH [1 pull requests, 2 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#23202•Fetched 2026-05-11 03:30:33
View on GitHub
Comments
2
Participants
1
Timeline
8
Reactions
0
Author
tilarsotilarso
Participants
tilarsotilarso
Timeline (top)
labeled ×4commented ×2cross-referenced ×2

In local_embedded mode, the Memory UI dashboard backend can fail to auto-start Hindsight with:

hindsight-embed command not found in dashboard environment

This happens when the dashboard process runs with a minimal PATH that does not include uv/venv tool locations.

Error Message

  1. include path diagnostics in error response

Root Cause

dashboard/plugin_api.py::_ensure_hindsight_local_daemon() invokes a bare command:

cmd = ["hindsight-embed", "-p", profile, "daemon", "start"]

So startup depends on PATH lookup only.

PR fix notes

PR #23519: fix(hindsight): repair embedded daemon PATH lookup

Description (problem / solution / changelog)

What does this PR do?

Repairs local_embedded Hindsight startup when the dashboard/plugin runtime inherits a minimal PATH. Hermes now prepends likely install locations for hindsight-embed before the daemon manager shells out, so an installed embedded daemon can still auto-start even when the current process PATH omits the active venv or uv tool bin directory.

Related Issue

Fixes #23202

Type of Change

  • 🐛 Bug fix (non-breaking change that fixes an issue)
  • ✨ New feature (non-breaking change that adds functionality)
  • 🔒 Security fix
  • 📝 Documentation update
  • ✅ Tests (adding or improving test coverage)
  • ♻️ Refactor (no behavior change)
  • 🎯 New skill (bundled or hub)

Changes Made

  • Added _ensure_hindsight_embed_on_path() in plugins/memory/hindsight/__init__.py to repair PATH with common Hermes install locations before local_embedded daemon startup.
  • Called the helper at embedded-daemon boot time and added a log breadcrumb when hindsight-embed still cannot be resolved.
  • Added regression tests in tests/plugins/memory/test_hindsight_provider.py covering both PATH repair and the no-op path when lookup already works.

How to Test

  1. Run uv run --frozen pytest -q -o addopts='' tests/plugins/memory/test_hindsight_provider.py.
  2. Run uv run --frozen ruff check plugins/memory/hindsight/__init__.py tests/plugins/memory/test_hindsight_provider.py.
  3. In a minimal-PATH environment, initialize local_embedded Hindsight and confirm Hermes can still resolve hindsight-embed from the active venv/bin or uv tool bin.

Checklist

Code

  • I've read the Contributing Guide
  • My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
  • I searched for existing PRs to make sure this isn't a duplicate
  • My PR contains only changes related to this fix/feature (no unrelated commits)
  • I've run pytest tests/ -q and all tests pass
  • I've added tests for my changes (required for bug fixes, strongly encouraged for features)
  • I've tested on my platform: macOS 15.4.1

Documentation & Housekeeping

  • I've updated relevant documentation (README, docs/, docstrings) — or N/A
  • I've updated cli-config.yaml.example if I added/changed config keys — or N/A
  • I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
  • I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
  • I've updated tool descriptions/schemas if I changed tool behavior — or N/A

Screenshots / Logs

  • 98 passed in 13.33s
  • All checks passed! from targeted ruff check

Changed files

  • plugins/memory/hindsight/__init__.py (modified, +59/-0)
  • tests/plugins/memory/test_hindsight_provider.py (modified, +41/-1)

Code Example

cmd = ["hindsight-embed", "-p", profile, "daemon", "start"]
RAW_BUFFERClick to expand / collapse

Summary

In local_embedded mode, the Memory UI dashboard backend can fail to auto-start Hindsight with:

hindsight-embed command not found in dashboard environment

This happens when the dashboard process runs with a minimal PATH that does not include uv/venv tool locations.

Environment

  • Hermes on Docker/Unraid
  • Memory UI plugin: hermes-memory-ui v0.4.6
  • Hindsight installed and runnable, but binary not on dashboard PATH
  • Example PATH seen by dashboard shell context:
    • /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games

Repro

  1. Configure Hindsight in local_embedded mode.
  2. Ensure dashboard runtime PATH does not include the location of hindsight-embed.
  3. Open Memory UI panel that triggers Hindsight recall/contents.
  4. Observe failure: hindsight-embed command not found in dashboard environment.

Root cause

dashboard/plugin_api.py::_ensure_hindsight_local_daemon() invokes a bare command:

cmd = ["hindsight-embed", "-p", profile, "daemon", "start"]

So startup depends on PATH lookup only.

Expected behavior

If hindsight-embed is installed in common Hermes locations, dashboard should resolve and launch it without requiring PATH changes.

Proposed fix

Resolve binary robustly:

  1. shutil.which("hindsight-embed")
  2. fallback absolute paths commonly used in Hermes deployments (venv + uv tool installs)
  3. include path diagnostics in error response

Notes

I implemented this locally and validated:

  • py_compile passes
  • helper call succeeds under constrained PATH (no command-not-found)
  • added daemon diagnostics payload to simplify troubleshooting

Happy to open a PR if desired.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

If hindsight-embed is installed in common Hermes locations, dashboard should resolve and launch it without requiring PATH changes.

#api#parallel task#integration issue#index setup#retrieval issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - ✅(Solved) Fix Memory UI dashboard local_embedded fails to auto-start Hindsight when hindsight-embed is not on PATH [1 pull requests, 2 comments, 1 participants]