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 1, 2026

First-class way to represent externally executed enterprise actions

Enterprise agents often should not execute directly. They should decide, then delegate execution to governed systems like BAW, Decisions, ITSM, ERP, or partner platforms.

This could be enabled by supporting an delegated/no-op tool concept which the WxO agent would use in a “go do this and tell me when your done” async mode. When the tool picked by the WxO agent is a no-op tool the WxO API would simply return a tool name and input params in the chat thread and let the calling platform decide what to do with it. Then the caller would send the chat thread back with the needed response asynchronously. For any other tool type (agent workflow, MCP tool, or OpenAPI/REST tool) WxO would invoke its tools as usual/as it does today.

This idea takes no capability away from WxO while opening its API for a platform like BAW to be driven from the inside by a WxO agent.

Idea priority High