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 Needs more information
Created by Guest
Created on Sep 22, 2025

RELATED IDEAS

Need source control (e.g. GIT integration) for agents and assistants

Larger implementations of orchestrate for agents and assistants are normally done through teams.

These teams need to be able to use git and a ci/cd pipeline to check out agents or assistants, make modifications, and check them back in so that they can be deployed by a ci/cd pipeline.

Idea priority Urgent
  • Post comment
  • Admin
    Eric Boutilier
    Oct 17, 2025

    Hi Victor,

    During a recent Slack conversation about CI/CD, the ADK development lead, Eric Marcoux, shared the following:

    For procode teams who wish to build out ci/cd pipelines, we fully support CI/CD for agents, tools, and knowledge authored pro code via the adk. But this I mean if they start yaml files for configuration, python tools and flows, model definitions, connection definitions, mcp toolkit definitions, etc, and version them with git, we have all of the commands via the cli you need to create a build pipeline to import and deploy every asset of watsonx Orchestrate, including some which do not even exist in the end user UI.
    If you wish to promote between two servers from configuration checked into source code, this is entirely possible to do today.
    However, this will not allow you to capture and version changes if part of your team is pro code and part of your team works with the ui. For this you need the ability to export assets from an Orchestrate server as well. This quarter we're extending export functionality to include all other assets like knowledge configuration, openapi tools, flows, etc.

    Regarding the last paragraph, we've already completed export support for connections, knowledge configurations, and agentic workflows (aka flows)


    Reply
  • Admin
    Laurent Tillette de Clermont-Tonnerre
    Sep 24, 2025

    Thank you for the additional details, we are targeting to introduce the versioning of agent artifacts in December as well as several environment to test them all right within the wxO platform: https://watson-orchestrate.ideas.ibm.com/ideas/LSABER-I-1192

    Will that do or do they specifically need an integration with GIT or else?

    Clarification on scope is key as well, thank you!!

    1 reply

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.