diff --git a/src/assets/agent-platform/editting_diff.png b/src/assets/agent-platform/editing_diff.png similarity index 100% rename from src/assets/agent-platform/editting_diff.png rename to src/assets/agent-platform/editing_diff.png diff --git a/src/content/docs/agent-platform/local-agents/code-diffs.mdx b/src/content/docs/agent-platform/local-agents/code-diffs.mdx index 562e20676..0c0b167ae 100644 --- a/src/content/docs/agent-platform/local-agents/code-diffs.mdx +++ b/src/content/docs/agent-platform/local-agents/code-diffs.mdx @@ -56,7 +56,7 @@ You can open up code files in Warp in various different ways, refer to: [Opening :::
-![Editing a code diff directly in Warp's native code editor](../../../../assets/agent-platform/editting_diff.png) +![Editing a code diff directly in Warp's native code editor](../../../../assets/agent-platform/editing_diff.png)
Editing a code diff in Warp's code editor.
diff --git a/src/content/docs/changelog/2021.mdx b/src/content/docs/changelog/2021.mdx index 124a28a3d..e067957c0 100644 --- a/src/content/docs/changelog/2021.mdx +++ b/src/content/docs/changelog/2021.mdx @@ -144,7 +144,7 @@ Submit bugs and feature requests on our [GitHub board!](https://github.com/warpd **New features** * Switch theme based on OS appearance - [068](https://github.com/warpdotdev/warp/issues/068) -* Toggles instead of buttons in the setttings! +* Toggles instead of buttons in the settings! * Link to Custom themes documentation in the settings **Bug fixes** diff --git a/src/content/docs/changelog/2022.mdx b/src/content/docs/changelog/2022.mdx index 6ebc47242..68e91a9c5 100644 --- a/src/content/docs/changelog/2022.mdx +++ b/src/content/docs/changelog/2022.mdx @@ -317,7 +317,7 @@ Submit bugs and feature requests on our [GitHub board!](https://github.com/warpd * Bookmark a Block (or multiple) for quick access via the scroll-bar * Added a referral counter to the Settings > Account screen and the referral screen * Added support for rendering text with a lower visual weight; enable the thin strokes option in Settings > Appearance (enabled by default for low-DPI displays) -* Togglable settings, overflow menu items, and settings pages are now accessible through the Command Palette +* Toggleable settings, overflow menu items, and settings pages are now accessible through the Command Palette * CLI options are now surfaced by default without needing to type '-' * Press SHIFT-CMD-C while in VSCode (Visual Studio Code) to open a new Warp session @@ -336,7 +336,7 @@ Submit bugs and feature requests on our [GitHub board!](https://github.com/warpd * Bookmark a Block (or multiple) for quick access via the scroll-bar * Added a referral counter to the Settings > Account screen and the referral screen * Added support for rendering text with a lower visual weight; enable the thin strokes option in Settings > Appearance (enabled by default for low-DPI displays) -* Togglable settings, overflow menu items, and settings pages are now accessible through the Command Palette +* Toggleable settings, overflow menu items, and settings pages are now accessible through the Command Palette * CLI options are now surfaced by default without needing to type '-' * Press SHIFT-CMD-C while in VSCode (Visual Studio Code) to open a new Warp session diff --git a/src/content/docs/changelog/2023.mdx b/src/content/docs/changelog/2023.mdx index d9ecb6525..8b5be90b8 100644 --- a/src/content/docs/changelog/2023.mdx +++ b/src/content/docs/changelog/2023.mdx @@ -79,7 +79,7 @@ Submit bugs and feature requests on our [GitHub board!](https://github.com/warpd **Bug fixes** * The Input Editor now refocuses correctly after pasting terminal contents and running a command -* Fixed issue with missing toolbelt buttons when using fish wih Vim Mode +* Fixed issue with missing toolbelt buttons when using fish with Vim Mode ### 2023.11.30 (v0.2023.11.28.08.02) diff --git a/src/content/docs/changelog/2026.mdx b/src/content/docs/changelog/2026.mdx index 92ce8e494..dd54b5ff8 100644 --- a/src/content/docs/changelog/2026.mdx +++ b/src/content/docs/changelog/2026.mdx @@ -1050,7 +1050,7 @@ Submit bugs and feature requests on our [GitHub board!](https://github.com/warpd #### Introducing Oz: orchestration for cloud agents -![Introducting Oz image showing the new Oz logo and a preview of the oz.warp.dev site](https://releases.warp.dev/changelog_images/v0.2026.02.09.06.06.stable.png) +![Introducing Oz image showing the new Oz logo and a preview of the oz.warp.dev site](https://releases.warp.dev/changelog_images/v0.2026.02.09.06.06.stable.png) Oz is Warp's orchestration platform for cloud agents: launch parallel agents, automate recurring engineering work, and build apps on top of agents with full visibility and control. diff --git a/src/content/docs/platform/quickstart.mdx b/src/content/docs/platform/quickstart.mdx index 4947762e3..90252574d 100644 --- a/src/content/docs/platform/quickstart.mdx +++ b/src/content/docs/platform/quickstart.mdx @@ -107,20 +107,14 @@ Follow the prompts to save your task definition. Once created, you can run it ag ## Next steps -{/* TODO: When advanced guides exist, refactor this section to link to them instead of providing instructions here. - Goal: Create a chain of "next steps" throughout docs that users can "fall into" and keep learning. - Each next step should link to a dedicated guide where they can learn more, rather than explaining everything here. - Example structure: - - "Schedule agents for recurring tasks" -> link to scheduling guide - - "Connect integrations" -> link to integrations guide - - "Build with the API" -> link to API guide - This creates a learning path rather than a single long quickstart. */} +Now that you've run your first cloud agent, try these next steps: -Now that you've run your first cloud agent, here are some next steps: +* [**Schedule recurring work**](/platform/triggers/scheduled-agents-quickstart/) - Create a scheduled agent for maintenance tasks like dependency checks, cleanup, or triage. +* [**Trigger agents from Slack or Linear**](/platform/integrations/quickstart/) - Connect Oz to team tools so mentions and issue updates can launch cloud agent runs. +* [**Turn successful prompts into reusable skills**](/platform/skills-as-agents/) - Save repeatable agent workflows and run them again from the CLI, web app, API, or a schedule. +* [**Build programmatic automations**](/reference/api-and-sdk/quickstart/) - Start cloud agent runs from your own systems with the Oz API or SDKs. -### Automate recurring tasks - -[Schedule agents](/platform/triggers/scheduled-agents/) to run on cron schedules for maintenance tasks like weekly dependency checks or daily dead code cleanup. +For example, schedule a recurring agent from the CLI: ```bash oz schedule create \ @@ -130,22 +124,10 @@ oz schedule create \ --prompt "check for dependency updates and open PR" ``` -### Trigger agents from integrations - -**Slack integration** - Tag @Oz in any Slack channel to get immediate help with code reviews, debugging, or incident response. Your team can discuss problems in Slack while Oz analyzes code, opens PRs, or investigates issues in the background. Results post directly back to the thread. See [Slack integration setup](/platform/integrations/slack/). - -**Linear integration** - Connect Oz to Linear to automate bug triage and fixes. Tag @Oz on an issue to reproduce the bug, identify root causes, and open a PR with a fix—closing the loop from bug report to resolution without leaving Linear. See [Linear integration setup](/platform/integrations/linear/). - -**GitHub Actions** - Run agents in CI/CD pipelines to automate tasks like generating release notes, running security audits, or validating migrations. Trigger agents on PRs, commits, or releases to keep workflows moving without manual intervention. See [GitHub Actions integration setup](/platform/integrations/github-actions/). - :::note Integrations require a team on Build, Max, or Business plan. ::: -### Build automations and apps on top of agents - -Use the [Oz API & SDK](/reference/api-and-sdk/) to trigger agents programmatically from your own systems and workflows. - --- ## Troubleshooting @@ -164,13 +146,3 @@ Your team needs at least 20 credits available. Check your credit balance in Sett * [Environments deep dive](/platform/environments/) * [Cloud Agents FAQs](/platform/faqs/) * [Managing Cloud Agents](/platform/managing-cloud-agents/) - ---- - -## What to explore next - -Now that you've run your first cloud agent, automate recurring work or connect agents to your team's tools. - -* **[Scheduled Agents quickstart](/platform/triggers/scheduled-agents-quickstart/)** - Set up an agent to run on a cron schedule for recurring tasks like weekly dependency checks. -* **[Integrations quickstart](/platform/integrations/quickstart/)** - Connect Oz to Slack and Linear so your team can trigger agents from mentions and issues. -* **[Skills](/agent-platform/capabilities/skills/)** - Turn successful agent workflows into reusable instructions you can schedule, trigger, or share. diff --git a/src/content/docs/reference/cli/index.mdx b/src/content/docs/reference/cli/index.mdx index 9aad722de..bca55034a 100644 --- a/src/content/docs/reference/cli/index.mdx +++ b/src/content/docs/reference/cli/index.mdx @@ -223,9 +223,6 @@ To start an agent, use the `oz agent run` subcommand. You'll need to specify a p ```sh oz agent run --prompt "set up a new Rust crate named warp-cli" -I'll run a few terminal commands to: -- Check if this is a Git repo and Cargo workspace -- Create a new binary crate named warp-cli ``` **Key flags:** diff --git a/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx b/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx index 42a5376d3..afb04de11 100644 --- a/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx @@ -30,7 +30,7 @@ See [Warp pricing](https://www.warp.dev/pricing) for the latest plans and what Please review the details of our refund policies below. To request a refund, email [**billing@warp.dev**](mailto:billing@warp.dev) with information about your situation — the more context you provide, the faster we can resolve your request. :::caution -In case of product defect, we require [Conversation ID](/support-and-community/troubleshooting-and-support/sending-us-feedback/#gathering-ai-conversation-id), [Logs](/support-and-community/troubleshooting-and-support/sending-us-feedback/#gathering-warp-logs), and "[Help improve Warp](/support-and-community/privacy-and-security/privacy/#how-to-disable-telemetry-and-crash-reporting)" must be enabled in order for us to identify the issue before we can provide any refunds or credits. +To request a refund or credit for a product defect, we require your [Conversation ID](/support-and-community/troubleshooting-and-support/sending-us-feedback/#gathering-ai-conversation-id) and [logs](/support-and-community/troubleshooting-and-support/sending-us-feedback/#gathering-warp-logs). You must have **Help improve Warp** enabled, so we can identify the issue before issuing any refund or credit. Learn how to enable it in [Crash reports and telemetry](/support-and-community/privacy-and-security/privacy/#how-to-disable-telemetry-and-crash-reporting). ::: #### Subscription refund policy diff --git a/src/content/docs/support-and-community/troubleshooting-and-support/known-issues.mdx b/src/content/docs/support-and-community/troubleshooting-and-support/known-issues.mdx index 2338e1d97..02a563c8e 100644 --- a/src/content/docs/support-and-community/troubleshooting-and-support/known-issues.mdx +++ b/src/content/docs/support-and-community/troubleshooting-and-support/known-issues.mdx @@ -23,7 +23,7 @@ To enable Blocks over SSH, Warp uses an SSH Wrapper function; navigate to **Sett ### Online features don't work -There is a known issue that can occur that causes online features to break ([Agent](/agent-platform/local-agents/overview/), [Generate](/agent-platform/local-agents/overview/), [Block Sharing](/terminal/blocks/block-sharing/), [Refer a Friend](/support-and-community/community/refer-a-friend/) ). This is due to the login token going stale, typically due to a password change, and can be resolved by the following steps: +There is a known issue that can occur that causes online features to break ([Agent](/agent-platform/local-agents/overview/), [Generate](/agent-platform/local-agents/generate/), [Block Sharing](/terminal/blocks/block-sharing/), [Refer a Friend](/support-and-community/community/refer-a-friend/) ). This is due to the login token going stale, typically due to a password change, and can be resolved by the following steps: @@ -117,7 +117,7 @@ If Warp is not working with your dotfile configuration, you can run your shell i You can set up clean configs for Bash (Bourne Again SHell) by moving or commenting out your `.bashrc`\ \ - If Warp starts working correctly then Warp is incompatible with something in the current dotfiles. We can isolate what is incompatible by iteratively disabling sections of our dotfiles with the `WarpTerminal` flag until we find the culprit. See the list of incompatible tools below and comment them out just for Warp with the following conditionals: + If Warp starts working correctly then Warp is incompatible with something in the current dotfiles. We can isolate what is incompatible by iteratively disabling sections of your dotfiles with the `WarpTerminal` flag until we find the culprit. See the list of incompatible tools below and comment them out just for Warp with the following conditionals: ```bash # bash (See ~/.bashrc) @@ -131,7 +131,7 @@ If Warp is not working with your dotfile configuration, you can run your shell i You can set up clean configs for Zsh (Z SHell) by moving or commenting out your `.zshrc`\ \ - If Warp starts working correctly then Warp is incompatible with something in the current dotfiles. We can isolate what is incompatible by iteratively disabling sections of our dotfiles with the `WarpTerminal` flag until we find the culprit. See the list of incompatible tools below and comment them out just for Warp with the following conditional: + If Warp starts working correctly then Warp is incompatible with something in the current dotfiles. We can isolate what is incompatible by iteratively disabling sections of your dotfiles with the `WarpTerminal` flag until we find the culprit. See the list of incompatible tools below and comment them out just for Warp with the following conditional: ```bash # zsh (See ~/.zshrc) @@ -145,7 +145,7 @@ If Warp is not working with your dotfile configuration, you can run your shell i You can set up clean configs for Fish (Friendly Interactive SHell) by moving or commenting out your `config.fish`\ \ - If Warp starts working correctly then Warp is incompatible with something in the current config file. We can isolate what is incompatible by iteratively disabling sections of our config file with the `WarpTerminal` flag until we find the culprit. See the list of incompatible tools below and comment them out just for Warp with the following conditional: + If Warp starts working correctly then Warp is incompatible with something in the current config file. We can isolate what is incompatible by iteratively disabling sections of your config file with the `WarpTerminal` flag until we find the culprit. See the list of incompatible tools below and comment them out just for Warp with the following conditional: ```bash # fish (see ~/.config/fish/config.fish) @@ -159,7 +159,7 @@ If Warp is not working with your dotfile configuration, you can run your shell i You can set up clean configs for pwsh (PowerShell) by moving or commenting out your `$PROFILE` - If Warp starts working correctly then Warp is incompatible with something in the current profile. We can isolate what is incompatible by iteratively disabling sections of our profile with the WarpTerminal flag until we find the culprit. See the list of incompatible tools below and comment them out just for Warp with the following conditional: + If Warp starts working correctly then Warp is incompatible with something in the current profile. We can isolate what is incompatible by iteratively disabling sections of your profile with the WarpTerminal flag until we find the culprit. See the list of incompatible tools below and comment them out just for Warp with the following conditional: ```powershell # pwsh (see $PROFILE) diff --git a/src/content/docs/support-and-community/troubleshooting-and-support/sending-us-feedback.mdx b/src/content/docs/support-and-community/troubleshooting-and-support/sending-us-feedback.mdx index 504e2c43c..6d83a604f 100644 --- a/src/content/docs/support-and-community/troubleshooting-and-support/sending-us-feedback.mdx +++ b/src/content/docs/support-and-community/troubleshooting-and-support/sending-us-feedback.mdx @@ -8,7 +8,7 @@ sidebar: --- import { Tabs, TabItem } from '@astrojs/starlight/components'; -### Sending Warp feedback +## Sending Warp feedback * Use the [`/feedback`](#using-feedback-in-warp) slash command inside Warp to open the static feedback experience. * Open a new bug or feature request in our [GitHub repository](https://github.com/warpdotdev/warp/issues/new/choose). @@ -16,7 +16,7 @@ import { Tabs, TabItem } from '@astrojs/starlight/components'; * For security issues or questions, email [security@warp.dev](mailto:security@warp.dev). * For questions about privacy, email [privacy@warp.dev](mailto:privacy@warp.dev). -#### Subscriber and Enterprise +### Subscribers and Enterprise * For subscriber technical issues or questions (bugs, credits, etc.), email [support@warp.dev](mailto:support@warp.dev). * For subscriber billing issues or questions (refunds, cancellation, etc.), email [billing@warp.dev](mailto:billing@warp.dev). diff --git a/src/content/docs/terminal/entry/command-corrections.mdx b/src/content/docs/terminal/entry/command-corrections.mdx index d1a8aac08..7998a574f 100644 --- a/src/content/docs/terminal/entry/command-corrections.mdx +++ b/src/content/docs/terminal/entry/command-corrections.mdx @@ -41,7 +41,7 @@ This feature was built on top of the open-source project [nvbn/thefuck](https:// | conda | | cp | | docker | -| generic (command agnostic, e.g. mis-spelling executable name) | +| generic (command agnostic, e.g. misspelling executable name) | | git | | go | | grep |