tinyhumansai/openhuman · error

call_memory_agent: agent definition '{AGENT_ID}' not found i

Error message

call_memory_agent: agent definition '{AGENT_ID}' not found in registry

What it means

The global agent registry is up, but no built-in definition with id AGENT_ID (the memory agent) exists in its list. The registry and the tool disagree about which agents are installed — a registration or gating mismatch rather than a bad argument.

Source

Thrown at src/openhuman/memory/agent/tools.rs:141

        let parent = current_parent();
        if parent.is_none() {
            return Ok(ToolResult::error(
                "call_memory_agent: no parent agent context — this tool must be \
                 called from within an agent turn."
                    .to_string(),
            ));
        }

        let registry = AgentDefinitionRegistry::global()
            .ok_or_else(|| anyhow::anyhow!("call_memory_agent: agent registry not initialised"))?;

        let definition = registry
            .list()
            .iter()
            .find(|d| d.id == AGENT_ID)
            .cloned()
            .ok_or_else(|| {
                anyhow::anyhow!(
                    "call_memory_agent: agent definition '{AGENT_ID}' not found in registry"
                )
            })?;

        let parent = parent.expect("checked above");
        if !parent.allowed_subagent_ids.contains(AGENT_ID) {
            log::warn!(
                "[call_memory_agent] blocked memory subagent outside parent allowlist parent_agent={} requested_agent={} allowed={:?}",
                parent.agent_definition_id,
                AGENT_ID,
                parent.allowed_subagent_ids
            );
            return Ok(ToolResult::error(format!(
                "call_memory_agent: agent '{AGENT_ID}' is not in parent agent '{}' subagents.allowlist",
                parent.agent_definition_id
            )));
        }

View on GitHub (pinned to 7491200858)

Solutions

  1. Verify the memory agent's built-in definition is registered by the active DomainSet/feature configuration
  2. Check for a renamed agent id in the registry versus the constant compiled into this tool
  3. Rebuild with the agent harness features that register the memory agent
Defensive patterns

Strategy: validation

When it happens

Trigger: Thrown at src/openhuman/memory/agent/tools.rs:141 when the library encounters an invalid state.

Common situations: See trigger scenarios.


AI-assisted analysis of tinyhumansai/openhuman@7491200858 (2026-08-17). Data as JSON: /api/errors/28f2515b70c76edc. Report an issue: GitHub.