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 Jul 9, 2025

RELATED IDEAS

Native Version Control Capabilities for AI Agents

Introduce native version control capabilities for AI agents in watsonx Orchestrate.

This feature would allow users to create, tag, and manage multiple versions of the same agent—enabling safer deployments, rollback to previous versions, and traceability across development, staging, and production environments.
Functionality should include:

- Manual or automatic version tagging on publish/save
- Viewing changelog or diff between versions
- Reverting or promoting a specific version to "active"
- APIs or UI support for version history access


Idea priority High
  • Post comment
  • Guest
    Jun 17, 2026

    Further, it would be great if we could explicitly state what version of the agent to use within a channel. For example, in the embedded web chat, the chatOptions key under the window.wxOConfiguration variable could additionally have a key titled agentVersion or something similar to indicate the precise agent version that should be referenced. This is very similar to the current agentEnvironmentId key that can be used to indicate if the "Draft" or "Live" version of the agent should be referenced by the chat.

        chatOptions: {

            agentId: "xxx",

            agentEnvironmentId: "xxx",
            agentVersion: "xxx",

        }
    Reply
  • Guest
    Nov 17, 2025

    I would like this idea to also allow me to save system prompts and connection settings, because an update changed the system prompts and caused the agent to stop working.

    Reply
5 MERGED

Versioning of tools

Merged
Some of the actions in the assistant are skill-based, meaning they rely on skills (no matter it's a workflow or decision model etc) built in the "skill studio" of orchestrate . Every time someone publishes a new version in the skill studio in orch...
over 1 year ago in  Planned for future release

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.