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 Nov 4, 2025

Character encoding issue when importing agents from ADK

When exporting agent for modification using the ADK, no issues occur concerning the character encoding, for example, some character like é/à/è are correctly kept as is during the export.

However, when importing the agents back into orchestrate with the ADK, these characters (in the agent description, instructions, etc...) break encoding.

For example : "Procédure d'installation" becomes "Procédure d’installation" in orchestrate.


While non-blocking, this makes the modification of agents through the ADK less appealing, as even when not modifying these string (e.g. just changing the model), all such string breaks, and we have to clean it up in the Orchestrate web UI.

Idea priority Medium
  • Admin
    Laurent Tillette de Clermont-Tonnerre
    Nov 8, 2025

    Thank you for your input, this might be a defect, did you consult tech support on that?