Skip to Main Content
Shape the future of IBM watsonx Orchestrate

Start by searching and reviewing ideas others have posted, and add a comment (private if needed), vote, or subscribe to updates on them if they matter to you.

If you can't find what you are looking for, create a new idea:

  1. stick to one feature enhancement per idea

  2. add as much detail as possible, including use-case, examples & screenshots (put anything confidential in Hidden details field or a private comment)

  3. Explain business impact and timeline of project being affected

[For IBMers] Add customer/project name, details & timeline in Hidden details field or a private comment (only visible to you and the IBM product team).

This all helps to scope and prioritize your idea among many other good ones. Thank you for your feedback!

Specific links you will want to bookmark for future use
Learn more about IBM watsonx Orchestrate - Use this site to find out additional information and details about the product.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Under review
Created by Guest
Created on May 18, 2026

Interoperable user memory across Orchestrate and other AI agent platforms

Watsonx Orchestrate user memory should interoperate with memory stores used by other AI agents and platforms.

Problem 1 : Missing relevant memories . Users may interact with an agent through Watsonx Orchestrate, and also through other interfaces which pass through a different agent platform to reach the same agent. The memory is maintained separately in each platform. 

Problem 2: Different geneal context for the user.  Over time both platforms will gather different memories of the user according to the conversations had while in their domain. This will mean that the platform's overall undertanding of the user by the user memory contect will be different. This will lead to the user preferring one entry point ove the other as it will seem to know them better.  

see attaced doc for a diagram illustrating the above problms

Problem summary: If each platform maintains isolated user memory, the same user may receive different personalisation, context, and continuity depending on their entry point. 

The request is for Orchestrate to support some form of user-memory interoperability. This would improve consistency of user experience, reduce fragmented context, and support coherent multi-agent ecosystems where memory follows the user, not just the interface.

However it is implemented is fine:

  • Support user memory as an MCP-based service so Orchestrate can read/write governed user memory from approved external memory services
  • or Extend A2A so agents can advertise whether they support user-memory exchange, and negotiate what memory can be shared, queried, or updated. 
  • or Adopt a services like OpenMemory / Mem0
  • or lean in on agent mmemory protocol (though this sounds a long road)
Idea priority High