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.

Add idea Subscribe
Status Planned for future release
Created by Guest
Created on Nov 17, 2025

RELATED IDEAS

Initializing embedded chat with specific thread_id

When configuring the embedded chat, it would be great to have the option to initiate it with a specific (existing) thread_id. Customers who need a single continuous chat for every user for example would benefit from that.


So, the general idea is to enable the possibility to start a conversation and come back later to resume where you left off without the need to start from the beginning. It would enable usecases like:

  • a shared chat between multiple users and one AI

  • no more need to repeat information

  • improved personalization based on your chat style and history

  • better documentation, compliance and auditing possibilities

  • a continuous process which takes a long time and forces the user to come back later

  • + probably a bunch of other usecase I am not thinking of right now.

In an ideal world I imagine that you simply specify a parameter "thread_id" within the wxoConfiguration or the chatOptions parameter of the wxoConfiguration. In case the thread_id is specified the system checks if it actually exists.


If so, the thread is loaded and displayed accordingly. Otherwise, a fallback should be implemented to create a new thread instead.

Idea priority Urgent
  • Post comment

By clicking the "Post Comment" or "Add Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not include IBM confidential, company confidential, or personal information in any field.
Having problems accessing this portal? Describe the problems in an email to ideasibm@us.ibm.com.