NousResearch/hermes-agent

Memory provider tools missing from agent execution path

Cluster 4781 · agent. Data as of

Nothing open on GitHub. Fix merged in #4803 on 3 Apr 2026. Check it covers your case.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #4803. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and fixes concern a bug where a holographic/memory plugin registers successfully but its tools are not routed into the sequential agent execution loop. The work focuses on correcting that routing path.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #4803 fix: route memory provider tools in sequential execution path

    merged to main

    files: run_agent.py

    Show the diff
    • run_agent.py
      @@ -6009,6 +6009,30 @@ def _execute_tool_calls_sequential(self, assistant_message, messages: list, effe
                               spinner.stop(cute_msg)
                           elif self.quiet_mode:
                               self._vprint(f"  {cute_msg}")
      +            elif self._memory_manager and self._memory_manager.has_tool(function_name):
      +                # Memory provider tools (hindsight_retain, honcho_search, etc.)
      +                # These are not in the tool registry — route through MemoryManager.
      +                spinner = None
      +                if self.quiet_mode and not self.tool_progress_callback:
      +                    face = random.choice(KawaiiSpinner.KAWAII_WAITING)
      +                    emoji = _get_tool_emoji(function_name)
      +                    preview = _build_tool_preview(function_name, function_args) or function_name
      +                    spinner = KawaiiSpinner(f"{face} {emoji} {preview}", spinner_type='dots', print_fn=self._print_fn)
      +                    spinner.start()
      +                _mem_result = None
      +                try:
      +                    function_result = self._memory_manager.handle_tool_call(function_name, function_args)
      +                    _mem_result = function_result
      +                except Exception as tool_error:
      +                    function_result = json.dumps({"error": f"Memory tool '{function_name}' failed: {tool_error}"})
      +                    logger.error("memory_manager.handle_tool_call raised for %s: %s", function_name, tool_error, exc_info=True)
      +                finally:
      +                    tool_duration = time.time() - tool_start_time
      +                    cute_msg = _get_cute_tool_message_impl(function_name, function_args, tool_duration, result=_mem_result)
      +                    if spinner:
      +                        spinner.stop(cute_msg)
      +                    elif self.quiet_mode:
      +                        self._vprint(f"  {cute_msg}")
                   elif self.quiet_mode:
                       spinner = None
                       if not self.tool_progress_callback:

1 PR closed without merging

From the close comments: merged via another change 1

  • #4785 fix(agent): route memory provider tools in sequential execution path · merged via another change → #4803
Closed issues · 1
  • Closed#4781Holographic memory plugin registers but tools not injected into agent loop
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
agent
Merged PRs
#4803
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
3 Apr 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.

For your agent

The same facts, typed.