Automated SEO fixes: improve docs link anchors

src/content/docs/agent-platform/agent-memory/index.mdx

@@ -9,7 +9,7 @@ sidebar:
 import VideoEmbed from '@components/VideoEmbed.astro';
 
 :::caution
-Agent Memory is in **research preview** and is enabled per team for design partners. [Join the waitlist](https://warp.dev/oz/agent-memory#waitlist) to request access for your team.
+Agent Memory is in **research preview** and is enabled per team for design partners. [Join the waitlist](https://www.warp.dev/oz/agent-memory#waitlist) to request access for your team.
 :::
 
 Agent Memory is a persistent memory system that lives on Oz and is shared across every supported agent harness, including the built-in Warp Agent, Claude Code, Codex, and others as they're added. Agents read from and write to this memory system as they run, so durable facts, decisions, and outcomes from one conversation are available to the next — regardless of which harness, machine, or teammate triggers the work.
@@ -20,7 +20,7 @@ Watch this short preview to see Agent Memory in context.
 
 <VideoEmbed url="https://www.youtube.com/watch?v=ED9g1shmiEE" title="Agent Memory" />
 
-[Join the Agent Memory waitlist](https://warp.dev/oz/agent-memory#waitlist).
+[Join the Agent Memory waitlist](https://www.warp.dev/oz/agent-memory#waitlist).
 
 ## Key features
 
@@ -72,7 +72,7 @@ Attach stores to agents with read-only or read-write access. Each attachment can
 
 ## Join the waitlist
 
-Agent Memory is rolling out to design partner teams during research preview. [Join the waitlist](https://warp.dev/oz/agent-memory#waitlist) to request access.
+Agent Memory is rolling out to design partner teams during research preview. [Join the waitlist](https://www.warp.dev/oz/agent-memory#waitlist) to request access.
 
 ## Related pages
 

src/content/docs/agent-platform/capabilities/codebase-context.mdx

@@ -71,7 +71,7 @@ For large projects, indexing may take a few minutes. Agents will not use Codebas
 You can view and manage your indexed codebases in **Settings** > **Code** > **Indexing and projects** under "Initialized / indexed folders". You can also choose whether to automatically index new folders as you navigate them.
 :::
 
-<VideoEmbed url="https://youtu.be/11rz9OYQ8Hg" />
+<VideoEmbed url="https://youtu.be/11rz9OYQ8Hg" title="Codebase Context video 1" />
 
 ### **Codebase indexing states**
 
@@ -140,7 +140,7 @@ Agents will only reference other repositories if they are already indexed. Durin
 
 Here's an example from [Warp Guides](/guides/), where Zach demonstrates how Warp uses Codebase Context to search for and use the relevant files as context:
 
-<VideoEmbed url="https://www.youtube.com/watch?v=11rz9OYQ8Hg" />
+<VideoEmbed url="https://www.youtube.com/watch?v=11rz9OYQ8Hg" title="Codebase Context video 2" />
 
 ---
 

src/content/docs/agent-platform/capabilities/full-terminal-use.mdx

@@ -11,7 +11,7 @@ Full Terminal Use lets Warp's agent operate directly inside interactive terminal
 
 The agent can see the live terminal buffer (terminal state), write to the PTY to run commands, respond to prompts, and continue working inside the running process while you stay in control.
 
-<VideoEmbed url="https://youtu.be/gBdehHrtb94?si=-vvl4ipGwwoWxEJq" />
+<VideoEmbed url="https://youtu.be/gBdehHrtb94?si=-vvl4ipGwwoWxEJq" title="Full Terminal Use video 1" />
 
 ## Overview
 
@@ -138,7 +138,7 @@ Note that this only affects the agent's messages and proposals; your terminal st
 * When agent responses are hidden, your own agent requests automatically dismiss after **4 seconds** to keep the terminal clear.
 * You can also manually dismiss any user query at any time by hovering over it and clicking the X.
 
-<VideoEmbed url="https://www.loom.com/share/c639fb4ab33343a39037b2083c66858a" />
+<VideoEmbed url="https://www.loom.com/share/c639fb4ab33343a39037b2083c66858a" title="Full Terminal Use video 2" />
 
 ---
 
@@ -209,7 +209,7 @@ To learn more about what goes into a credit and how to get more value from AI us
 
 Here’s a demo from one of our engineers, Maggie, that walks through a couple of Full Terminal Use examples.
 
-<VideoEmbed url="https://www.loom.com/share/d47ee09153df417983df65a339a9d6f2" />
+<VideoEmbed url="https://www.loom.com/share/d47ee09153df417983df65a339a9d6f2" title="Full Terminal Use video 3" />
 
 Below are some common interactive tools where Full Terminal Use is particularly useful: database shells (Postgres, MySQL, SQLite), debuggers such as gdb, language-specific REPLs like python or node, text editors and file explorers, and long-running dev servers or monitoring tools such as top and htop.
 

src/content/docs/agent-platform/capabilities/planning.mdx

@@ -10,7 +10,7 @@ import VideoEmbed from '@components/VideoEmbed.astro';
 
 Warp has native planning functionality that helps you break down complex engineering tasks into structured, executable steps. Planning is tightly integrated with Warp's coding agent and provides a persistent plan editor, version history, selective execution, and deep links into your workspace.
 
-<VideoEmbed url="https://youtu.be/DawcFWyudV0?si=OzvuInMl8DoNR97R" />
+<VideoEmbed url="https://youtu.be/DawcFWyudV0?si=OzvuInMl8DoNR97R" title="Planning in Warp" />
 
 ---
 
@@ -101,7 +101,7 @@ You can configure whether your plans will be automatically added and synced to W
 
 Plans are reusable across tasks and sessions. You can reference them in future prompts, continue where you left off, or build follow-up plans that rely on earlier work.
 
-The **@plans** command helps you quickly search for and reopen previously saved plans, making planning a consistent part of your development workflow rather than a one-off step. Learn more about attaching context using @ [here](/agent-platform/local-agents/agent-context/using-to-add-context/).
+The **@plans** command helps you quickly search for and reopen previously saved plans, making planning a consistent part of your development workflow rather than a one-off step. See [attaching context with @ references](/agent-platform/local-agents/agent-context/using-to-add-context/) for more ways to add files, folders, diffs, and saved objects to an agent conversation.
 
 ![Searching for and reopening previously saved plans with the @plans command.](../../../../assets/agent-platform/@-reference-plans.png)
 

src/content/docs/agent-platform/capabilities/rules.mdx

@@ -13,7 +13,7 @@ Warp’s **Rules** feature lets you create reusable guidelines that inform how a
 
 Warp supports two types of rules: **Global Rules** and **Project Rules**.
 
-<VideoEmbed url="https://youtu.be/fDr0-3bLxMQ" />
+<VideoEmbed url="https://youtu.be/fDr0-3bLxMQ" title="Rules for agents video" />
 
 ## Global Rules
 

src/content/docs/agent-platform/capabilities/web-search.mdx

@@ -10,7 +10,7 @@ import VideoEmbed from '@components/VideoEmbed.astro';
 
 Warp includes native web search for models that support first-party search tools. When enabled, agents can look up information in real time, consult documentation, retrieve current version numbers, and cite the sources used to generate responses.
 
-<VideoEmbed url="https://www.loom.com/share/06a4ba98f2e0446d80cb37aa4c23848c" />
+<VideoEmbed url="https://www.loom.com/share/06a4ba98f2e0446d80cb37aa4c23848c" title="Web search in Warp" />
 
 This page covers how web search works, supported models, what you can expect inside Warp, configuration options, and how this differs from attaching URLs directly to a prompt.
 
@@ -52,8 +52,8 @@ Web search is available only for models that offer a native web search integrati
 
 Warp uses each vendor’s official tool:
 
-* **Claude Web Search**: [https://docs.claude.com/en/docs/agents-and-tools/tool-use/web-search-tool](https://docs.claude.com/en/docs/agents-and-tools/tool-use/web-search-tool)
-* **OpenAI Web Search**: [https://developers.openai.com/api/docs/guides/tools-web-search](https://developers.openai.com/api/docs/guides/tools-web-search)
+* **Claude Web Search**: [Claude web search tool documentation](https://docs.claude.com/en/docs/agents-and-tools/tool-use/web-search-tool)
+* **OpenAI Web Search**: [OpenAI web search tool documentation](https://developers.openai.com/api/docs/guides/tools-web-search)
 
 :::note
 **Note**: We plan to add native web search for additional models as soon as their APIs fully support it. We’ll continue updating the list of search-capable models as vendors roll out broader tooling. We're also exploring custom web search tools that'll work across all models.

src/content/docs/agent-platform/cloud-agents/agents.mdx

@@ -43,7 +43,7 @@ Scoping each identity to a single workflow gives every run the minimum credentia
 
 ## Plan limits
 
-Every team starts with a default agent identity. Additional identities are subject to plan-based limits. See [warp.dev/pricing](https://warp.dev/pricing) for current limits per plan.
+Every team starts with a default agent identity. Additional identities are subject to plan-based limits. See [Warp pricing](https://www.warp.dev/pricing) for current limits per plan.
 
 When a team is over its plan limit (for example, after downgrading), the extra identities remain visible in the list but are marked as unavailable. Unavailable identities cannot be used to start runs, cannot have new API keys generated for them, and cannot be edited.
 

src/content/docs/agent-platform/cloud-agents/integrations/cloud-providers.mdx

@@ -12,7 +12,7 @@ Cloud agents can securely access AWS, GCP, and other cloud providers using short
 
 ## Prerequisites
 
-* A Warp account ([create an account at oz.warp.dev](https://oz.warp.dev))
+* A Warp account. You can [create an account in the Oz web app](https://oz.warp.dev).
 * A cloud provider account
 
 Follow the section for your cloud provider.
@@ -25,7 +25,7 @@ Follow the section for your cloud provider.
 
 The first step is to configure your AWS account to trust OIDC tokens produced by Oz.
 
-1. Open the AWS IAM console at [https://console.aws.amazon.com/iam](https://console.aws.amazon.com/iam).
+1. Open the [AWS IAM console](https://console.aws.amazon.com/iam).
 2. Click **Identity Providers**, then click **Add provider**.
 3. Set the provider type to **OpenID Connect**.
 4. Set the **Provider URL** to `https://app.warp.dev`.
@@ -45,7 +45,7 @@ Verify that the provider was created correctly by:
 
 Next, you will need to set up an AWS IAM role with a trust policy that links it to the OIDC provider.
 
-1. Open the AWS IAM console at [https://console.aws.amazon.com/iam](https://console.aws.amazon.com/iam).
+1. Open the AWS IAM console at [AWS IAM console](https://console.aws.amazon.com/iam).
 2. Click **Roles**, then click **Create role**.
 3. Select **Custom trust policy**, and fill in the following JSON trust policy:
 
@@ -126,7 +126,7 @@ To allow multiple specific principals, use a list of subjects:
 
 Finally, configure the cloud agent environment to use your new AWS role.
 
-1. Open the Oz web app at [https://oz.warp.dev](https://oz.warp.dev).
+1. Open the [Oz web app](https://oz.warp.dev).
 2. Create or edit an environment. See [Environments](/agent-platform/cloud-agents/oz-web-app/#environments) for instructions.
 3. Expand the **AWS** section and enter the AWS role ARN from Step 2.
 4. Save the environment.
@@ -212,7 +212,7 @@ for the full syntax supported.
 
 Finally, configure the cloud agent environment to use your Workload Identity Federation provider.
 
-1. Open the Oz web app at [https://oz.warp.dev](https://oz.warp.dev).
+1. Open the Oz web app at [Oz web app](https://oz.warp.dev).
 2. Create or edit an environment. See [Environments](/agent-platform/cloud-agents/oz-web-app/#environments) for instructions.
 3. Expand the **GCP** section and enter the project number, pool ID, and provider ID from Step 1.
 4. Save the environment.

src/content/docs/agent-platform/cloud-agents/integrations/github-actions.mdx

@@ -16,7 +16,7 @@ If you're comparing GitHub Actions with schedules, Slack, Linear, the Oz CLI, or
 
 Watch this demo to see the integration in action:
 
-<VideoEmbed url="https://www.loom.com/share/534f88b6a98e43ca9769ca09de6424b5" />
+<VideoEmbed url="https://www.loom.com/share/534f88b6a98e43ca9769ca09de6424b5" title="GitHub Actions video" />
 
 In this demo
 

src/content/docs/agent-platform/cloud-agents/integrations/index.mdx

@@ -27,7 +27,7 @@ All of this is powered by the [Oz CLI](/reference/cli/).
 
 Use the setup walkthrough below for a quick look at how environments connect to integrations, then choose the guide that matches what you want to do next.
 
-<VideoEmbed url="https://www.youtube.com/watch?v=ahFfInVD0HQ" />
+<VideoEmbed url="https://www.youtube.com/watch?v=ahFfInVD0HQ" title="Integrations Overview video" />
 
 * [Integrations quickstart](/agent-platform/cloud-agents/integrations/quickstart/) - Trigger your first agent from Slack and watch the run from start to finish.
 * [Integration setup](/reference/cli/integration-setup/) - Configure environments, GitHub authorization, CLI flags, and integrations in more detail.

src/content/docs/agent-platform/cloud-agents/integrations/linear.mdx

@@ -12,7 +12,7 @@ The Linear integration lets your team delegate development work directly to agen
 
 Agents keep you updated inside Linear, generate pull requests using your GitHub account, and provide a link to join a live remote session so you can watch or steer the workflow in real time.
 
-<VideoEmbed url="https://youtu.be/FNefNmbSdmg?si=PxvDuW6OfNZBvhSl" />
+<VideoEmbed url="https://youtu.be/FNefNmbSdmg?si=PxvDuW6OfNZBvhSl" title="Linear integration video 1" />
 
 This guide explains what the integration does, how it works end-to-end, and how to configure it for your Warp team.
 
@@ -129,7 +129,7 @@ To remove the Oz integration from Linear:
 4. Select Oz from the list of installed agents.
 5. Click **Revoke access** to remove the integration for your workspace.
 
-<VideoEmbed url="https://www.loom.com/share/2f1648586d8148dc80561c00a09ca334" />
+<VideoEmbed url="https://www.loom.com/share/2f1648586d8148dc80561c00a09ca334" title="Linear integration video 2" />
 
 After revoking access, Warp will no longer be able to read issues, receive triggers, or create updates in Linear. If you reinstall later, you’ll need to authorize Warp again during setup. Events for a disabled integration can return [`integration_disabled`](/reference/api-and-sdk/troubleshooting/errors/integration-disabled/).
 

src/content/docs/agent-platform/cloud-agents/integrations/quickstart-github-actions.mdx

@@ -78,7 +78,7 @@ To verify the workflow ran:
 
 Each `oz-agent-action` step creates a cloud agent run you can inspect from the Oz dashboard:
 
-* **Oz web app** - Go to [oz.warp.dev/runs](https://oz.warp.dev/runs) to see the full run transcript: status, commands executed, files changed, and agent output. See [Viewing Cloud Agent Runs](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) for a complete walkthrough.
+* **Oz web app** - Go to [Runs page in the Oz web app](https://oz.warp.dev/runs) to see the full run transcript: status, commands executed, files changed, and agent output. See [Viewing Cloud Agent Runs](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) for a complete walkthrough.
 * **Warp app** - Open the conversations panel to see the run alongside your other agent activity.
 
 When the run completes, the agent posts feedback as inline review comments on the PR.

src/content/docs/agent-platform/cloud-agents/integrations/quickstart.mdx

@@ -27,7 +27,7 @@ Oz integrations let you trigger cloud agents directly from the tools your team a
 
 The simplest way to set up the integration is **using the Oz web app**:
 
-1. Navigate to the Oz web app at [oz.warp.dev/integrations](https://oz.warp.dev/integrations).
+1. Navigate to the Oz web app at [Integrations page in the Oz web app](https://oz.warp.dev/integrations).
 2. Click **Slack**.
 3. Follow the guided flow to select your environment and authorize Oz in your Slack workspace.
 
@@ -73,7 +73,7 @@ You can also tag @Oz inside an existing thread. Oz picks up the full thread hist
 While the agent works, progress updates appear directly in the Slack thread. To inspect the run in more detail:
 
 * **Click the session link** - Oz posts a link in the thread to open a live terminal view of the agent. Watch in real time, add follow-up instructions, or let it run to completion.
-* **Go to [oz.warp.dev/runs](https://oz.warp.dev/runs)** - See the full run transcript: status, commands executed, files changed, and agent output. See [Viewing Cloud Agent Runs](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) for a complete walkthrough.
+* **Go to [Runs page in the Oz web app](https://oz.warp.dev/runs)** - See the full run transcript: status, commands executed, files changed, and agent output. See [Viewing Cloud Agent Runs](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) for a complete walkthrough.
 
 When the task is complete, Oz posts a summary back to the original Slack thread.
 

src/content/docs/agent-platform/cloud-agents/managing-cloud-agents.mdx

@@ -8,7 +8,7 @@ sidebar:
 ---
 import VideoEmbed from '@components/VideoEmbed.astro';
 
-Warp provides two management surfaces for tracking and observing agent activity across your account and, where applicable, your team: the **Agent Management Panel** in the Warp app and the [**Runs** page in the Oz web app](/agent-platform/cloud-agents/oz-web-app/#runs) at [oz.warp.dev](https://oz.warp.dev), which works on mobile devices. In Warp, open the Agent Management Panel from the Agent Management Panel button in the tab bar; in the web app, go to the Runs page.
+Warp provides two management surfaces for tracking and observing agent activity across your account and, where applicable, your team: the **Agent Management Panel** in the Warp app and the [**Runs** page in the Oz web app](/agent-platform/cloud-agents/oz-web-app/#runs) at [Oz web app](https://oz.warp.dev), which works on mobile devices. In Warp, open the Agent Management Panel from the Agent Management Panel button in the tab bar; in the web app, go to the Runs page.
 
 Use these surfaces as the starting point for real-time agent observability in Warp. They help you see which agents are active, which runs are blocked or failed, where each run started, and which session link opens the prompt, plan, commands, logs, outputs, and follow-up messages behind the work.
 
@@ -23,7 +23,7 @@ The Agent Management Panel and Oz web app Runs page are designed to answer, at a
 
 Warp's agent observability is run- and session-oriented. It is not a replacement for full APM, OpenTelemetry, or Datadog-style tracing across arbitrary agent frameworks. Use Warp to track agent run status, trigger/source, owner, parent-child relationships, transcripts, commands, logs, outputs, and replayable session links.
 
-<VideoEmbed url="https://www.loom.com/share/679c267ddd2d44519abf79edcb1122c7" />
+<VideoEmbed url="https://www.loom.com/share/679c267ddd2d44519abf79edcb1122c7" title="Managing cloud agents video" />
 
 These management surfaces include your **local (interactive) agents** and [cloud agent](/agent-platform/cloud-agents/overview/) runs.
 

src/content/docs/agent-platform/cloud-agents/overview.mdx

@@ -18,20 +18,20 @@ To understand what a cloud agent did, start from the [Agent Management Panel](/a
 
 For a full walkthrough, see [Viewing cloud agent runs](/agent-platform/cloud-agents/viewing-cloud-agent-runs/). If the run came from Slack, Linear, GitHub Actions, a schedule, the CLI, or the API, it still produces a reviewable cloud agent run record.
 
-<VideoEmbed url="https://youtu.be/poLkJhO7fdo" />
+<VideoEmbed url="https://youtu.be/poLkJhO7fdo" title="Cloud agents overview" />
 
 ### What cloud agents are designed for
 
 Cloud agents are designed for situations where:
 
 * **You need agents to react to system events.**
-  * Examples include crashes, bug reports, Slack interactions, cron timers, or CI steps.
+  * Examples include crashes, bug reports, [Slack interactions](/agent-platform/cloud-agents/integrations/slack/), cron timers, or CI steps.
 * **You want observability into agent activity across a team or system.**
   * This includes being able to see what ran, when it ran, what triggered it, what the agent did, and how teammates can review or share the result.
 * **You need more parallelism than local execution typically allows.**
   * For example, running many agent tasks concurrently in the cloud, sharding a repo-wide task into multiple runs, or fanning out the same task across multiple targets.
 * **You want agents to operate continuously as part of engineering infrastructure.**
-  * This includes scheduled maintenance tasks and integration-driven automation.
+  * This includes [scheduled maintenance tasks](/agent-platform/cloud-agents/triggers/scheduled-agents/) and integration-driven automation.
 
 ![Oz use cases across the development lifecycle: Plan, Prototype, Build, Validate, Review + Merge, Deploy + Monitor](../../../../assets/agent-platform/oz-use-cases.png)
 

src/content/docs/agent-platform/cloud-agents/oz-web-app.mdx

@@ -15,7 +15,7 @@ The Oz web app works on mobile devices, so you can monitor and manage your cloud
 :::
 
 Watch this short demo to create an environment and run an agent using the Oz web app:
-<VideoEmbed url="https://youtu.be/h9Wd77leIYg" />
+<VideoEmbed url="https://youtu.be/h9Wd77leIYg" title="Oz web app for cloud agents video" />
 
 ## Quick reference