Merge pull request #202 from redpanda-data/claude/docs-updates-2026-08-07

docs: Agentic Data Plane docs updates (2026-08-07)

Author: micheleRP

modules/connect/pages/create-agent.adoc

@@ -8,7 +8,7 @@
 :learning-objective-3: Connect to and test a running agent
 
 // Source: cloudv2 `proto/public/cloud/redpanda/api/adp/v1alpha1/agent.proto` (AgentCreate, ManagedAgentSpec) cross-referenced against `apps/adp-ui/src/components/agents/managed-create/` (managed-agent-canvas.tsx, model-picker.tsx, subagent-sheet.tsx, instructions-field.tsx, tool-list.tsx), `apps/adp-ui/src/components/agents/agent-detail-sections.tsx`, and `apps/adp-ui/src/routes/_authenticated/agents/$name.index.page.tsx` on cloudv2 main, verified 2026-08-01.
-// The managed create flow is a single canvas titled "New managed agent" with sections Identity, Model, Instructions, Tools, and a collapsible Advanced area (Subagents, Tags). The Model picker is a single model-only list; the provider that serves the chosen model is selected automatically. There is no stepper and no editable Agent ID field; the resource slug is derived from the name at submit. The managed agent detail Overview is organized into Agent, Model & runtime, System prompt, MCP servers, and Subagents sections. Managed agent detail tabs are Overview, Triggers, Inspector, Cost & Usage, Transcripts, and Permissions. Credentials and Setup tabs exist only on self-managed agents.
+// The managed create flow is a single canvas titled "New managed agent" with sections Identity, Model, Instructions, Tools, and a collapsible Advanced area (Subagents, Tags). The Model picker is a single model-only list; the provider that serves the chosen model is selected automatically. There is no stepper and no editable Agent ID field; the resource slug is derived from the name at submit. The managed agent detail Overview is organized into Agent, Model & runtime, System prompt, MCP servers, and Subagents sections. Managed agent detail tabs are Overview, Triggers, Playground, Cost & Usage, Transcripts, and Permissions. Credentials and Setup tabs exist only on self-managed agents. The interactive test tab, previously labeled Inspector, is now labeled Playground and its URL is `?tab=playground`. Re-verified 2026-08-07.
 
 Create a new glossterm:AI agent[] declaratively through Redpanda Agentic Data Plane. No Python or JavaScript code required. This guide walks through the managed create canvas section by section, then covers how to connect to and test the running agent.
 
@@ -155,7 +155,7 @@ When the agent is running, open its detail page. A managed agent has these tabs:
 
 * *Overview*: The agent's full configuration, organized into sections that you edit and save one at a time. The *Agent* section holds the display name, description, and tags (the agent ID is fixed). The *Model & runtime* section holds the LLM provider, model, and max iterations, along with the runtime status and endpoint. The *System prompt*, *MCP servers*, and *Subagents* sections hold the instructions, attached servers, and subagents.
 * *Triggers*: Schedules and event sources that invoke the agent. See xref:connect:triggers/overview.adoc[].
-* *Inspector*: An interactive test surface. See <<test-your-agent,Test your agent>>.
+* *Playground*: An interactive test surface. See <<test-your-agent,Test your agent>>.
 * *Cost & Usage*: Spend, tokens, and latency for the agent.
 * *Transcripts*: A record of every conversation against the agent.
 * *Permissions*: The access policies that apply to the agent as a principal. See xref:control:access-policies.adoc[].
@@ -211,12 +211,12 @@ For more about agent cards and how they're consumed, see xref:connect:a2a-concep
 
 Two tabs on the agent detail page support testing and observability:
 
-* *Inspector*: Send test prompts interactively and inspect each step of the agent's reasoning, tool calls, and responses. Use Inspector during development and tuning. The composer shows the agent's provider and model as read-only, so a test run always uses the agent's saved configuration.
+* *Playground*: Send test prompts interactively and inspect each step of the agent's reasoning, tool calls, and responses. Use Playground during development and tuning. The composer shows the agent's provider and model as read-only, so a test run always uses the agent's saved configuration.
 * *Transcripts*: Records every conversation against the agent (prompt, tool calls, tool outputs, final response). Use transcripts to audit production behavior.
 
-To test the agent in Inspector:
+To test the agent in Playground:
 
-. Open the agent's *Inspector* tab.
+. Open the agent's *Playground* tab.
 . Enter a test prompt.
 . Verify the agent:
 +

modules/connect/pages/draw-charts.adoc

@@ -1,18 +1,18 @@
 = Draw Charts from an Agent
-:description: Make an agent render inline bar and line charts in the Inspector by emitting a chart code block that follows the Agentic Data Plane chart contract.
+:description: Make an agent render inline bar and line charts in the Playground by emitting a chart code block that follows the Agentic Data Plane chart contract.
 :page-topic-type: how-to
 :personas: agent_builder
 :learning-objective-1: Instruct an agent to draw a bar or line chart by emitting a chart code block
 :learning-objective-2: Migrate an earlier chart prompt to the Agentic Data Plane chart contract
 :learning-objective-3: Diagnose a chart that renders as an error or stays a placeholder
 
-// Source: cloudv2 `apps/adp-ui/src/components/agents/inspector/components/chart-block.tsx`, `chart-block-renderer.tsx`, and `ai-elements/response.tsx` on origin/main. Verified 2026-07-28.
+// Source: cloudv2 `apps/adp-ui/src/components/agents/inspector/components/chart-block.tsx`, `chart-block-renderer.tsx`, and `ai-elements/response.tsx` on origin/main. Verified 2026-07-28; the agent interaction tab is now labeled Playground (route `?tab=playground`), re-verified 2026-08-07.
 
 An agent draws a chart by emitting a fenced code block tagged `chart` whose body is strict JSON that follows the Agentic Data Plane chart contract.
-The Inspector renders the data with the Agentic Data Plane chart components.
+The Playground renders the data with the Agentic Data Plane chart components.
 The fence body contains data, not Recharts component code.
-The agent's *Inspector* tab renders that block with Chart, Data, and Code views.
-This is a rendering convention: the agent decides when a chart helps and writes the data, and the Inspector draws it.
+The agent's *Playground* tab renders that block with Chart, Data, and Code views.
+This is a rendering convention: the agent decides when a chart helps and writes the data, and the Playground draws it.
 No tool call or application setup is required.
 
 [IMPORTANT]
@@ -39,14 +39,14 @@ After reading this page, you will be able to:
 
 == How chart rendering works
 
-When the agent's response contains a fenced code block tagged `chart`, the Inspector parses the block body as a chart configuration and draws the chart in place of the code.
+When the agent's response contains a fenced code block tagged `chart`, the Playground parses the block body as a chart configuration and draws the chart in place of the code.
 Every other code block renders as plain code, so a `chart` block is the agent's only departure from ordinary output.
 
 The renderer supplies the visual presentation.
 A valid configuration renders as a responsive SVG chart with the Redpanda theme, a tooltip, and a legend.
 The agent supplies the chart type, optional title, labels, series names, and numeric values.
 
-Agentic Data Plane draws a `chart` block wherever it shows the agent's response: the agent's *Inspector* tab and the *Transcripts* tab.
+Agentic Data Plane draws a `chart` block wherever it shows the agent's response: the agent's *Playground* tab and the *Transcripts* tab.
 When an external application calls the agent, whether that application draws the chart depends on how it renders the agent's output.
 
 == Write the chart block
@@ -57,15 +57,15 @@ Unsupported chart types or invalid values show an error.
 * Tag the fence `chart`.
 The opening fence is three backticks followed by the word `chart`, with no other language tag.
 * Write the body as strict JSON.
-The Inspector parses the body with a JSON parser, not a JavaScript evaluator, so use double-quoted keys and strings, unquoted numbers, no trailing commas, no comments, and no JavaScript expressions, functions, or callbacks.
+The Playground parses the body with a JSON parser, not a JavaScript evaluator, so use double-quoted keys and strings, unquoted numbers, no trailing commas, no comments, and no JavaScript expressions, functions, or callbacks.
 * Set the top-level `type` to `bar` or `line`.
 * Add a top-level `data` object with `labels` and `datasets` arrays.
 Each dataset contains a `data` array and can include a `label`.
-Without a `label`, the Inspector names the series `Series 1`, `Series 2`, and so on.
+Without a `label`, the Playground names the series `Series 1`, `Series 2`, and so on.
 Values in a dataset must be finite numbers or `null`.
 * To display a title, add a top-level `title` string.
 * Do not add renderer-specific `options`, plugins, scales, animations, or color properties.
-The Inspector controls those presentation details.
+The Playground controls those presentation details.
 
 A bar chart:
 
@@ -121,7 +121,7 @@ Rules for the chart block:
   "data" array and can include a "label".
 - Do not emit renderer-specific options, plugins, scales, animations, or colors.
 - Put a brief plain-text explanation (1 or 2 sentences) before the chart block.
-  Do not also paste a data table; the Inspector has a built-in Data view.
+  Do not also paste a data table; the Playground has a built-in Data view.
 
 Example response to "show last quarter's orders by month":
 
@@ -143,21 +143,21 @@ Orders peaked in February:
 
 For prompt-writing patterns that make this output reliable, see xref:connect:system-prompts.adoc#output-formatting[Output formatting].
 
-== Test the chart in the Inspector
+== Test the chart in the Playground
 
-. Open the agent and switch to the *Inspector* tab.
+. Open the agent and switch to the *Playground* tab.
 . Enter a prompt that calls for a chart, such as `Show the broker count for the demo cluster over the last 3 months as a bar chart`.
 . Wait for the agent to finish its response.
 The chart appears in place of the `chart` block.
 
-image::connect:agent-chart-rendered.png[alt="The Inspector rendering a bar chart titled Broker count / demo cluster / 3 months, with a Chart, Data, and Code view selector above bars for January, February, and March."]
+image::connect:agent-chart-rendered.png[alt="The Playground rendering a bar chart titled Broker count / demo cluster / 3 months, with a Chart, Data, and Code view selector above bars for January, February, and March."]
 
 Use the view selector to switch between:
 
 * *Chart*: The responsive bar or line chart.
 Hover over the chart to inspect values.
 * *Data*: The chart's values as a table, reconstructed from the configuration.
-* *Code*: The JSON configuration the Inspector parsed.
+* *Code*: The JSON configuration the Playground parsed.
 
 Zoom, pan, and PNG export are not available.
 
@@ -186,7 +186,7 @@ Convert other chart types to `bar` or `line`.
 
 |`options`, `plugins`, `scales`, animations, or colors
 |Remove them.
-The Inspector supplies the presentation.
+The Playground supplies the presentation.
 
 |Zoom, pan, or PNG export instructions
 |Remove them.
@@ -256,7 +256,7 @@ Common causes include invalid JSON, a missing `type` field, a missing `data` obj
 For migration guidance, see <<migrate-chart-js-prompt>>.
 
 |A Building chart… placeholder remains visible
-|The placeholder shows while the `chart` block streams in, because the Inspector cannot parse the configuration until the closing fence arrives.
+|The placeholder shows while the `chart` block streams in, because the Playground cannot parse the configuration until the closing fence arrives.
 The chart replaces the placeholder when the agent finishes the response.
 If the response finishes and the body cannot be parsed, the Failed to render chart error replaces the placeholder.
 If the placeholder remains after the agent stops responding, instruct the agent to emit one complete `chart` block with a closing fence.

modules/control/pages/cost-usage.adoc

@@ -83,7 +83,7 @@ Use *Download full report* when you need the whole dataset rather than the chart
 
 The *Activity* tab answers a different question from the report: instead of what something cost, it shows what's running right now. It ranks the agents with traffic over a window of the last hour (the default), the last 24 hours, or the last 7 days, and shows each agent's change against the previous window. Select an agent to see its recent requests and open a conversation.
 
-The Inspector's live view also hands off to this tab: when an agent task is still running after several minutes, the Inspector points you here to follow it to completion.
+The Playground's live view also hands off to this tab: when an agent task is still running after several minutes, the Playground points you here to follow it to completion.
 
 == Next steps
 

modules/gateway/pages/configure-provider.adoc

@@ -204,7 +204,7 @@ For Bedrock, the picker exposes inference profiles, not raw foundation-model IDs
 Redpanda stores models as structured `ProviderModel` entries (one entry per model, with the model name as the only required field). Each model can carry custom pricing overrides that replace the catalog rates for that model in cost reporting; see <<pricing-overrides>>. The legacy flat `models` field still works on writes for backward compatibility.
 ====
 
-Beyond pricing, the catalog carries each model's capabilities and context-window limits. The model discovery API (the `ListModels` and `GetModel` methods on `ModelService`) reports `max_input_tokens` (the largest context the model accepts) and `max_output_tokens` (the most it can generate in a single response) for each model. Both are read-only catalog metadata: a limit the catalog doesn't declare stays unset rather than reported as zero. Clients read `max_input_tokens` to show how full an agent's context window is, such as the context-window indicator on the agent's *Inspector* tab.
+Beyond pricing, the catalog carries each model's capabilities and context-window limits. The model discovery API (the `ListModels` and `GetModel` methods on `ModelService`) reports `max_input_tokens` (the largest context the model accepts) and `max_output_tokens` (the most it can generate in a single response) for each model. Both are read-only catalog metadata: a limit the catalog doesn't declare stays unset rather than reported as zero. Clients read `max_input_tokens` to show how full an agent's context window is, such as the context-window indicator on the agent's *Playground* tab.
 
 [[pricing-overrides]]
 === Override per-model pricing