Move image folders

Author: ntrogh

docs/copilot/agents/background-agents.md

@@ -98,11 +98,11 @@ To continue a local agent session in a background agent session:
 
     * Select **Continue Chat In** and then select **Background**
 
-        ![Screenshot showing the "Continue in Chat" button in VS Code chat interface.](./images/background-agents/continue-in-chat-background.png)
+        ![Screenshot showing the "Continue in Chat" button in VS Code chat interface.](../images/background-agents/continue-in-chat-background.png)
 
     * If you're using the [Plan agent](/docs/copilot/chat/chat-planning.md), select the **Start Implementation** dropdown and the select **Continue in Background** to run the implementation in a background agent session
 
-        ![Screenshot showing the "Start Implementation" button in VS Code chat interface.](./images/background-agents/plan-agent-start-implementation-background.png)
+        ![Screenshot showing the "Start Implementation" button in VS Code chat interface.](../images/background-agents/plan-agent-start-implementation-background.png)
 
     * Type `@cli /delegate` in the chat input and send the message
 
@@ -126,7 +126,7 @@ To enable custom agents with background agents:
 
 1. Select the custom agent from the Agents dropdown
 
-    ![Screenshot showing custom agent selection in VS Code chat interface.](./images/background-agents/custom-agent-selection.png)
+    ![Screenshot showing custom agent selection in VS Code chat interface.](../images/background-agents/custom-agent-selection.png)
 
 1. Enter a prompt and notice that the custom agent is used to handle the task
 
@@ -145,15 +145,15 @@ To create a Copilot CLI background agent session with a worktree:
 
 1. In the chat editor, select **Worktree** for the isolation mode.
 
-    ![Screenshot showing the "Worktree" isolation mode option in VS Code chat interface.](./images/background-agents/isolated-run-mode.png)
+    ![Screenshot showing the "Worktree" isolation mode option in VS Code chat interface.](../images/background-agents/isolated-run-mode.png)
 
     To run a background agent on the current workspace without isolation, select **Workspace**.
 
 1. Enter your prompt to create a new Git worktree and start the background agent session
 
 1. In Source Control view, in the **Repositories** view, you can view the Git worktree
 
-    ![Screenshot showing Git worktree in VS Code Source Control view.](./images/background-agents/git-worktree-source-control.png)
+    ![Screenshot showing Git worktree in VS Code Source Control view.](../images/background-agents/git-worktree-source-control.png)
 
     The Agents view also shows the worktree path for the background agent session.
 
@@ -170,13 +170,13 @@ Learn more about [using Git worktrees in VS Code source control](/docs/sourcecon
 
 To view the conversation history of a background agent session, select the session in the Agents view. The chat editor opens, displaying the full conversation history and any code changes made by the agent. To open the agent session in a new VS Code window, right-click the session and select **Open in New Window**.
 
-![Screenshot showing background agent session details in VS Code chat editor.](./images/background-agents/background-agent-session-details.png)
+![Screenshot showing background agent session details in VS Code chat editor.](../images/background-agents/background-agent-session-details.png)
 
 In the chat editor, you can provide additional instructions to the background agent or review the changes it made.
 
 If you prefer to view the Copilot CLI session instead of the chat conversation in VS Code, right-click the session in the Agents view and select **Resume Agent Session in Terminal**. You can interact with the Copilot CLI directly in VS Code.
 
-![Screenshot showing the Copilot CLI session inside VS Code.](./images/background-agents/copilot-cli-in-terminal.png)
+![Screenshot showing the Copilot CLI session inside VS Code.](../images/background-agents/copilot-cli-in-terminal.png)
 
 ## Next steps
 

docs/copilot/agents/cloud-agents.md

@@ -79,7 +79,7 @@ To continue a local agent session in a cloud agent session:
 
     * If you're using the [Plan agent](/docs/copilot/chat/chat-planning.md), select the **Start Implementation** dropdown and the select **Continue in Cloud** to run the implementation in a cloud agent session
 
-        ![Screenshot showing the "Start Implementation" button in VS Code chat interface.](./images/background-agents/plan-agent-start-implementation-background.png)
+        ![Screenshot showing the "Start Implementation" button in VS Code chat interface.](../images/background-agents/plan-agent-start-implementation-background.png)
 
 The cloud agent session starts automatically, carrying over the full chat history and context. You can monitor the cloud agent's progress in the Agents view.
 
@@ -95,7 +95,7 @@ In the chat editor, you can provide additional instructions to the cloud agent o
 
 When you have installed the GitHub Pull Requests extension, you can view the pull requests created by Copilot coding agent from the Pull Requests view, under the category **Copilot On My Behalf**.
 
-![Screenshot of the Pull Requests view in VS Code showing pull requests created by Copilot coding agent.](./images/cloud-agents/copilot-on-my-behalf-pull-requests.png)
+![Screenshot of the Pull Requests view in VS Code showing pull requests created by Copilot coding agent.](../images/cloud-agents/copilot-on-my-behalf-pull-requests.png)
 
 ## Related resources
 

docs/copilot/agents/overview.md

@@ -34,7 +34,7 @@ These autonomous agents have the following capabilities:
 
 VS Code supports four main categories of agents, each designed for different use cases and levels of interaction:
 
-![Diagram showing agent types by environment and interaction.](./images/overview/agent-types-diagram.png)
+![Diagram showing agent types by environment and interaction.](../images/agents-overview/agent-types-diagram.png)
 
 <!--
 ```mermaid
@@ -126,7 +126,7 @@ Third party agents are background agents developed by external providers (for ex
 
 The **Agents view** provides a centralized interface for tracking and managing your agent sessions, both local in VS Code and in other environments, such as Copilot coding agent, GitHub Copilot CLI, or OpenAI Codex.
 
-![Screenshot of the Agents view in VS Code showing multiple agent sessions.](./images/overview/agents-view.png)
+![Screenshot of the Agents view in VS Code showing multiple agent sessions.](../images/agents-overview/agents-view.png)
 
 To open the **Agents** view, run the **Agents: Focus on Agents View** command from the Command Palette (`kb(workbench.action.showCommands)`).
 
@@ -154,7 +154,7 @@ By default, the Agents view shows all sessions, except archived sessions. Use th
 * Type: Local, Background, Cloud, or Codex
 * Status: Completed, In Progress, Failed, or Archived
 
-![Screenshot of the Agents view filter dropdown.](./images/overview/agents-view-filter.png)
+![Screenshot of the Agents view filter dropdown.](../images/agents-overview/agents-view-filter.png)
 
 Select **Reset** to reset the filters to the default value.
 
@@ -201,7 +201,7 @@ For example, you might start with a local agent to brainstorm and plan a feature
 
 You can delegate a local agent session from chat in VS Code by using the **Continue In** button in the chat input box, or use the `@cli`, `@cloud`, or `@codex` commands to pass a task to another agent type.
 
-![Screenshot of the chat input box showing the Continue In button.](./images/overview/delegate-local-session.png)
+![Screenshot of the chat input box showing the Continue In button.](../images/agents-overview/delegate-local-session.png)
 
 In a background agent session, you can delegate to a cloud agent by using the `/delegate` command in the chat input box.
 
@@ -211,15 +211,15 @@ When you delegate a session, VS Code creates a new agent session of the selected
 
 Select an agent session in the Agents view to open a chat editor that displays the full conversation history, file changes, and status updates.
 
-![Screenshot of an agent session details view in VS Code.](./images/overview/agent-session-details.png)
+![Screenshot of an agent session details view in VS Code.](../images/agents-overview/agent-session-details.png)
 
 You can continue iterating with the agent via the chat interface in the session details view. For example, you can ask the agent to make further modifications, explain changes, run tests, and more.
 
 ## Review file changes
 
 When an agent makes code modifications, you can review the changes directly from within the session details view. The view shows the list of changed files, along with diff statistics.
 
-![Screenshot of the file changes diff editor in an agent session.](./images/overview/agent-file-changes.png)
+![Screenshot of the file changes diff editor in an agent session.](../images/agents-overview/agent-file-changes.png)
 
 Select a changed file to view a diff editor that highlights the specific lines added, removed, or modified by the agent.
 

docs/copilot/customization/language-models.md

@@ -205,7 +205,7 @@ You can use locally hosted models in chat by using [bring your own model key](#b
 
 * Use a built-in model provider that supports local models
 * Install an extension from the [Visual Studio Marketplace](https://marketplace.visualstudio.com/search?term=tag%3Alanguage-models&target=VSCode&category=All%20categories&sortBy=Relevance), for example, [AI Toolkit for VS Code with Foundry Local](https://aka.ms/AIToolkit)
-* Configure a [custom OpenAI-compatible model](#use-an-openai-compatible-model)
+* Configure a [custom OpenAI-compatible model](#_add-an-openaicompatible-model)
 
 Currently, you cannot connect to a local model for inline suggestions. VS Code provides an extension API [`InlineCompletionItemProvider`](/api/references/vscode-api.md#InlineCompletionItemProvider) that enables extensions to contribute a custom completion provider. You can get started with our [Inline Completions sample](https://github.com/microsoft/vscode-extension-samples/blob/main/inline-completions).