From 06105c9c622171ae73b57d0947cd25b16acf9a09 Mon Sep 17 00:00:00 2001 From: Matt Vollmer Date: Wed, 4 Mar 2026 23:21:08 -0500 Subject: [PATCH] docs(agents): convert markdown images to HTML img tags (#22647) --- docs/ai-coder/agents/architecture.md | 2 +- docs/ai-coder/agents/index.md | 4 ++-- docs/ai-coder/agents/models.md | 8 ++++---- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/ai-coder/agents/architecture.md b/docs/ai-coder/agents/architecture.md index 4a68e4a32b..5b686f2b50 100644 --- a/docs/ai-coder/agents/architecture.md +++ b/docs/ai-coder/agents/architecture.md @@ -19,7 +19,7 @@ Three components are involved in every agent interaction: reads and writes files, and executes processes — exactly what occurs when a developer connects via their IDE. -![Architecture diagram ](../../images/guides/ai-agents/agent-loop-detailed.png) +Architecture diagram ## The same connection your IDE uses diff --git a/docs/ai-coder/agents/index.md b/docs/ai-coder/agents/index.md index 74dd0db466..92d62520e4 100644 --- a/docs/ai-coder/agents/index.md +++ b/docs/ai-coder/agents/index.md @@ -68,7 +68,7 @@ The workspace itself has no knowledge of AI. It is standard compute infrastructure — there are no LLM API keys, no agent harnesses, and no special software installed. All intelligence lives in the control plane. -![Architecture diagram showing the control plane in the center, with arrows out to LLM providers and arrows to workspaces](../../images/guides/ai-agents/agent-loop.png) +Architecture diagram showing the control plane in the center, with arrows out to LLM providers and arrows to workspaces The agent loop runs in the control plane. It makes outbound requests to LLM providers and connects to workspaces only when tool execution is needed. @@ -195,7 +195,7 @@ enterprise LLM proxies, self-hosted model endpoints, and internal gateways. Administrators can configure multiple providers simultaneously and set a default model. Developers select from enabled models when starting a chat. -![Screenshot of the provider/model configuration admin panel](../../images/guides/ai-agents/llm-providers.png) +Screenshot of the provider/model configuration admin panel The model configuration panel in the Coder dashboard. diff --git a/docs/ai-coder/agents/models.md b/docs/ai-coder/agents/models.md index cd34a0718a..3ed543ee8a 100644 --- a/docs/ai-coder/agents/models.md +++ b/docs/ai-coder/agents/models.md @@ -37,12 +37,12 @@ models, internal gateways, or third-party proxies like LiteLLM. useful for enterprise proxies, regional endpoints, or self-hosted models. 1. Click **Save**. -![Screenshot of the providers list in the admin dialog](../../images/guides/ai-agents/models-providers.png) +Screenshot of the providers list in the admin dialog The providers list shows all supported providers and their configuration status. -![Screenshot of the add provider form](../../images/guides/ai-agents/models-add-provider.png) +Screenshot of the add provider form Adding a provider requires an API key. The base URL is optional. @@ -75,11 +75,11 @@ generation parameters, and provider-specific options. 1. Configure any provider-specific options (see below). 1. Click **Save**. -![Screenshot of the models list in the admin dialog](../../images/guides/ai-agents/models-list.png) +Screenshot of the models list in the admin dialog The models list shows all configured models grouped by provider. -![Screenshot of the add model form](../../images/guides/ai-agents/models-add-model.png) +Screenshot of the add model form Adding a model requires a model identifier, display name, and context limit. Provider-specific options appear dynamically based on the selected