Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

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.

IBM Employees should enter Ideas at https://ideas.ibm.com



Status Submitted
Created by Guest
Created on Oct 12, 2026

Add Native Prompt Caching Support for Anthropic Claude on AWS Bedrock in Watson Orchestrate Agent Runtime

Watson Orchestrate's agent runtime does not inject the cache_control: {"type": "ephemeral"} metadata on static prompt segments when calling Anthropic Claude on AWS Bedrock, so Bedrock prompt caching is never activated.

Why it's useful: Every agent turn recomputes the full static context (system instructions + skill catalog), wasting Bedrock compute tokens and adding latency — even though the downstream gateway already supports caching.

Who benefits: Enterprise customers running high-volume agent workloads on Bedrock/Anthropic models who want lower token costs and faster response times.

How it should work: The agent runtime should automatically attach cache_control breakpoints to static prompt segments (base instructions, tool/skill catalogs) at the point of LLM dispatch when routing to Bedrock/Anthropic models — requiring no configuration from the end user.

Idea priority Medium