docs: document Warp file locations across macOS/Windows/Linux#110
Merged
Conversation
Adds a new reference page that lays out every Warp config, data, and state path across all three platforms and both release channels, plus fixes related pages whose Windows/Linux paths were inaccurate or incomplete: - New: terminal/settings/file-locations covering data_dir, config_local_dir, state_dir, ~/.warp, ~/.agents, and the WSL symlink workflow Windows + WSL users actually need. - Tab Configs page now lists per-OS tab_configs directories instead of only showing the macOS path. - Custom Themes background_image note now points at the per-OS themes directory instead of just ~/.warp/themes. - Uninstall doc fixes a Linux XDG_STATE_HOME -> XDG_DATA_HOME typo for themes/launch configs, calls out ~/.warp on Windows, and corrects the Windows Preview path to WarpPreview. - Settings file overview cross-links the new reference page. - Sidebar adds the new page under the Settings file group. Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Overview
This PR adds a cross-platform reference for Warp file locations and updates existing pages to stop using macOS-only paths. I found accuracy issues in the new WSL/home-directory guidance that would send Windows+WSL users to the wrong locations.
Concerns
- The cross-platform carve-out incorrectly says Preview may use
~/.warp-<channel>/for MCP/skills even though Stable and Preview share~/.warp/for those files. - The WSL symlink commands assume
$USERmatches the Windows profile name, which is not reliable. - The WSL section says
~/.warp/and~/.agents/are already shared between Windows and WSL, but WSL$HOMEis separate from Windows%USERPROFILE%.
Verdict
Found: 0 critical, 3 important, 0 suggestions
Request changes
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
| * **Non-portable config** - Local-only configuration that doesn't make sense to roam, such as `settings.toml` and `keybindings.yaml`. | ||
| * **Non-portable state** - Machine-specific state like logs, the local database, and the Codebase Context index. | ||
|
|
||
| In addition, a small set of cross-cutting files always live under `~/.warp/` (or `~/.warp-<channel>/` on macOS Preview) on every platform — currently MCP server config and bundled skills. These intentionally sit in the home directory so they're easy to reference from shell config, version control, or other tools. |
Contributor
There was a problem hiding this comment.
~/.warp-<channel>/, but the source-backed paths below say Stable and Preview share ~/.warp/ for those files. Remove the Preview exception so users do not look in ~/.warp-preview for MCP config or skills.
Collaborator
Author
There was a problem hiding this comment.
Addressed in adb1dd6. Reworded the cross-cutting carve-out paragraph in file-locations.mdx to state explicitly that both Stable and Preview share ~/.warp/ for MCP config and skills, and that Preview does not use ~/.warp-preview/ for these files. Only channels like OSS use a suffixed directory (e.g. ~/.warp-oss/). Also added matching clarifications to each bullet in the Preview channel paths section (macOS, Windows, Linux) so the same point is reinforced wherever a reader lands.
|
|
||
| ```bash | ||
| # Portable data: themes, tab configs, workflows, launch configurations. | ||
| ln -s "/mnt/c/Users/$USER/AppData/Roaming/warp/Warp/data" ~/.warp-windows-data |
Contributor
There was a problem hiding this comment.
$USER is the Linux account name, which often differs from the Windows profile directory, so this can create a symlink to a path that does not exist. Resolve %USERPROFILE% through Windows and convert it with wslpath, or tell users to replace the Windows user name explicitly.
Collaborator
Author
There was a problem hiding this comment.
Addressed in adb1dd6. Rewrote the WSL section in file-locations.mdx so the primary approach now resolves the Windows profile path through cmd.exe and converts it with wslpath:
WIN_HOME=$(wslpath "$(cmd.exe /C 'echo %USERPROFILE%' 2>/dev/null | tr -d '\r')")
ln -s "$WIN_HOME/AppData/Roaming/warp/Warp/data" ~/.warp-windows-data
# ...etcThis avoids the original WIN_USER=YourWindowsUserName step and the implicit assumption that the WSL $USER matches the Windows profile name. The hard-coded fallback (/mnt/c/Users/<your-windows-username>) is still mentioned at the bottom for users who would rather not pipe through cmd.exe.
| ln -s "/mnt/c/Users/$USER/AppData/Local/warp/Warp/config" ~/.warp-windows-config | ||
| ``` | ||
|
|
||
| `~/.warp/` (MCP config, skills) and `~/.agents/` are already shared because both Windows and WSL use the same user home directory layout for those files. |
Contributor
There was a problem hiding this comment.
$HOME is separate from Windows %USERPROFILE%, so ~/.warp/ and ~/.agents/ are not automatically shared. If users need WSL tools to read Windows-side MCP or agent config, document separate links to the Windows profile paths instead.
Collaborator
Author
There was a problem hiding this comment.
Addressed in adb1dd6. Rewrote the intro of the WSL section to call this out explicitly:
WSL
$HOME(typically/home/<wsl-user>/) is a separate Linux filesystem from your Windows profile (%USERPROFILE%, typicallyC:\Users\<Windows-user>\), so~/.warp/and~/.agents/inside WSL are not automatically the same as the Windows-side directories with those names — every Warp directory you want to share needs its own symlink that points back to the Windows path.
The symlinks below it then point the WSL-side ~/.warp and ~/.agents at the Windows-side $WIN_HOME/.warp and $WIN_HOME/.agents (where $WIN_HOME is resolved from %USERPROFILE% via wslpath), which is the "separate links to the Windows profile paths" pattern you suggested.
- Drop the inaccurate 'or ~/.warp-<channel>/ on macOS Preview' note from the cross-platform carve-out: Stable and Preview both use ~/.warp/ for MCP config and bundled skills per warp_home_config_dir_name() in warp_core/src/paths.rs. Other channels (OSS, Dev, etc.) get a suffix. - Rework the WSL symlink section: WSL $HOME is separate from Windows %USERPROFILE%, so ~/.warp/ and ~/.agents/ are not shared automatically. Use a WIN_USER variable instead of $USER (the WSL Linux account name, often different from the Windows profile), and document additional symlinks for ~/.warp and ~/.agents so users can share them too. Co-Authored-By: Oz <oz-agent@warp.dev>
Member
Windows Preview Registry key is incorrect pathThe Registry key for Warp Preview on Windows is documented as Why:
Fix 1 —
|
dannyneira
approved these changes
May 19, 2026
dannyneira
left a comment
dannyneira
left a comment
Member
There was a problem hiding this comment.
approving to unblock, with comments on a needed fix
… WSL setup Addresses review feedback on PR #110: - Fix the Windows Preview Registry key in two places: it is HKCU:\\Software\\Warp.dev\\WarpPreview (no hyphen). The hyphenated Warp-Preview form is the macOS bundle identifier (dev.warp.Warp-Preview), not the Windows app name. Confirmed against script/windows/bundle.ps1 ($APP_NAME = 'WarpPreview') and registry_backed.rs (Software\\Warp.dev\\<app_name>). - Reword the cross-cutting carve-out paragraph in file-locations.mdx so it states explicitly that both Stable and Preview share ~/.warp/ for MCP config and skills, and only channels like OSS use a suffixed directory. - Rewrite the WSL section to promote wslpath + %USERPROFILE% resolution as the primary approach (instead of hard-coding the Windows username) and call out that WSL $HOME is a separate Linux filesystem from %USERPROFILE%, so ~/.warp and ~/.agents on the WSL side are not automatically the same as their Windows-side counterparts. Co-Authored-By: Oz <oz-agent@warp.dev>
Collaborator
Author
|
Thanks for catching this! Fixed in adb1dd6:
Verified against |
hongyi-chen
added a commit
that referenced
this pull request
May 21, 2026
…remove preview-period notes, restore File locations sidebar - Restore the 'File locations' sidebar entry under Settings file (added on main by PR #110, accidentally dropped during the rebase). - Drop the 'CIE' abbreviation throughout the customer-supplied inference pages. Use the full name 'custom inference endpoint' (or 'your endpoint' / 'endpoint-routed model' in context) instead. - Narrow the 'never consumes Warp credits' claim to 'doesn't consume AI credits' on the BYOK and custom inference endpoint pages, since Business / Enterprise local agent runs still consume platform credits. - Rewrite the 'No Warp credits consumed' Key features bullet on the custom inference endpoint page so it accurately calls out the platform-credits caveat on Business / Enterprise. - Drop the 'Self-serve preview period' paragraph from the platform-credits :::note callouts on the BYOK and custom inference endpoint pages. The July 1, 2026 cutover lives only in pricing-faqs.mdx now \u2014 canonical feature pages don't carry the launch-period detail. Co-Authored-By: Oz <oz-agent@warp.dev>
hongyi-chen
added a commit
that referenced
this pull request
May 21, 2026
…LLM) (#115) * docs(pricing-may-2026): customer-supplied inference (BYOK + CIE + BYOLLM) Part of the May 14, 2026 pricing-and-packaging docs launch. - BYOK is now available on the Free plan; page rewritten to open eligibility, refresh model examples, and add the BYOK/CIE/BYOLLM comparison table. - New Custom Inference Endpoint (CIE) page for OpenAI Chat Completions– compatible endpoints (OpenRouter, LiteLLM, z.ai, internal gateways). Sidebar entry added under Plans and billing. - BYOLLM reframed as Enterprise-only managed inference. AWS Bedrock GA; Google Vertex AI and Azure AI Foundry on the roadmap. Cloud-native credentials now span IAM/OIDC across all three cloud providers. - 10-employee org rule applies to BYOK and CIE; larger orgs need Business or Enterprise. - Platform-credits caveats: on Business/Enterprise local agent runs, customer-supplied inference still consumes platform credits even though no AI credits are charged. - plans-and-billing/index.mdx updated to surface the new CIE page. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): note July 1 self-serve preview period in BYOK + CIE platform-credits callouts Both BYOK and CIE pages now spell out that self-serve billing for platform credits (including Business BYOK / CIE) doesn't start until July 1, 2026. Between May 14 and June 30, 2026, platform-credit consumption is visible in the Warp app's usage breakdown for transparency on Build, Max, and Business, but no platform credits are deducted from your Reload pool or counted against your spend cap. Enterprise plans are billed per contract from May 14 and aren't affected by this preview period. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): correct launch date May 14 \u2192 May 21, 2026 Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): revert BYOLLM page to main, keep changes minimal Per launch direction: keep the Enterprise BYOLLM page largely unchanged for this launch. The BYOK/CIE/BYOLLM comparison still lives on the BYOK and CIE pages, so readers landing on either of those will see the three-way framing. This restores: - The original AWS-Bedrock-focused frontmatter description and opening paragraph (instead of the cross-provider reframing). - The original 'BYOLLM currently supports AWS Bedrock only. Coming soon: Azure Foundry and Google Vertex support.' caveat. - The original 'Cloud-native credentials - Authenticate using each user's AWS IAM identity' key feature. - The original 'How is BYOLLM different from BYOK?' FAQ with its 4-row comparison table. - The original Related resources list. Drops the launch-era additions: - The 'How BYOLLM differs from BYOK and Custom inference endpoint' section with the three-way comparison table. - The :::note about centrally configured BYOK / CIE for Enterprise being a fast-follow. - The :::note about platform credits for BYOLLM-routed local runs. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): drop CIE abbreviation, narrow credit claims, remove preview-period notes, restore File locations sidebar - Restore the 'File locations' sidebar entry under Settings file (added on main by PR #110, accidentally dropped during the rebase). - Drop the 'CIE' abbreviation throughout the customer-supplied inference pages. Use the full name 'custom inference endpoint' (or 'your endpoint' / 'endpoint-routed model' in context) instead. - Narrow the 'never consumes Warp credits' claim to 'doesn't consume AI credits' on the BYOK and custom inference endpoint pages, since Business / Enterprise local agent runs still consume platform credits. - Rewrite the 'No Warp credits consumed' Key features bullet on the custom inference endpoint page so it accurately calls out the platform-credits caveat on Business / Enterprise. - Drop the 'Self-serve preview period' paragraph from the platform-credits :::note callouts on the BYOK and custom inference endpoint pages. The July 1, 2026 cutover lives only in pricing-faqs.mdx now \u2014 canonical feature pages don't carry the launch-period detail. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): de-emphasize billing in BYOK + custom inference endpoint openings, consolidate plan notes - Reframe the BYOK and custom inference endpoint opening copy around model selection and data routing instead of billing. Move the AI-credits-consumption details out of the intro and down into the dedicated billing sections where they belong. - Collapse the two stacked :::note callouts about plan availability and the 10-or-fewer-employees rule into a single, briefer note on each page. - Move the Business / Enterprise platform-credits caveat off the top of the BYOK page and into the 'Credit usage' subsection alongside the related credit details. - Trim the 'BYOK on Enterprise and Business plans' section on the BYOK page so it doesn't restate the org-size rule already covered up top. - Replace the redundant 'Plan availability' section on the custom inference endpoint page with a focused 'Centrally managed configuration' section that only covers what's still unique to that page (user-level config today, admin-managed coming later).\n - Light copy polish on phrasing in both files. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): restore original BYOK opening, narrow only the credits claim to AI credits Per follow-up review, undo the polish on the BYOK intro and restore the original three-paragraph opening verbatim: - Title back to 'Bring Your Own API Key' (Title Case) - 'Warp supports Bring Your Own Key (BYOK) for users who want to connect Warp's agents to their own Anthropic, OpenAI, or Google API accounts.' - 'This lets you use your own API keys to access models directly, giving you full control over model selection, billing, and data routing. See Model Choice for a list of supported models.' - 'BYOK provides greater flexibility in model access and ensures Warp never consumes your AI credits for requests routed through your own keys.' The only substantive change vs the original is narrowing 'credits' to 'AI credits' in that last sentence, per earlier feedback that the unqualified 'never consumes Warp credits' claim is too broad now that Business / Enterprise local runs can consume platform credits. The combined plan-availability + 10-employee :::note below the intro stays as-is. Everything below the intro (BYOK works, Enabling BYOK, billing behavior, Credit usage with the platform-credits note, ZDR, Enterprise/Business config, Related resources) is unchanged. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): soften absolute 'no AI credits / 0 credits' claims in BYOK + CIE credit sections - Drop the 'No AI credits are consumed' bullet and the 'credit transparency footer shows 0 credits used' sentence from BYOK's Credit usage subsection. Replaced with a more general framing that says inference is billed through your provider account rather than drawing from your Warp AI credits, alongside the existing platform credits caveat for Business / Enterprise. - Same softening on the custom inference endpoint page's Warp AI credits subsection \u2014 collapse the three firm bullets into one general sentence and keep the platform-credits note. This avoids the misleadingly absolute '0 credits' claim, which is inaccurate for Business / Enterprise local runs where platform credits can still apply. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): reframe custom inference endpoint intro to lead with powering Warp's agents Mirror the BYOK page's intro pattern so it's explicit upfront that a custom inference endpoint is used to power Warp's agents. New opening: Warp supports custom inference endpoints for users who want to power Warp's agents with any OpenAI-compatible inference endpoint \u2014 a model router, hosted gateway, or internal infrastructure they already run. This lets you route AI requests through your preferred provider, run inference behind your own gateway, or use a router like OpenRouter or LiteLLM, while keeping the agent experience inside Warp. No other changes. Co-Authored-By: Oz <oz-agent@warp.dev> * Cleanup pass: BYOK acronym + BYOLLM table scope - bring-your-own-api-key.mdx intro: fix the wrong BYOK expansion ('Bring Your Own Key (BYOK)') to match the page title and standard usage ('Bring Your Own API Key (BYOK)'). - bring-your-own-api-key.mdx + custom-inference-endpoint.mdx comparison tables: tighten the BYOLLM row so it reflects current launch scope ('AWS Bedrock today; Azure Foundry and Google Vertex coming soon') instead of implying all three ship at launch. Co-Authored-By: Oz <oz-agent@warp.dev> * PR #115 review: address Tyler's comments - bring-your-own-api-key.mdx 'Platform credits' note: Tyler correctly pointed out that platform credits also apply for cloud agent runs. Rewrite the line to lead with the cloud-agent case ('apply to every cloud agent run on any plan') and then cover the local-runs case ('and to local agent runs on Business and Enterprise when using BYOK, a custom inference endpoint, or BYOLLM'). - bring-your-own-api-key.mdx 'How BYOK works' opening: drop the misleading 'directly to the model provider' phrasing since requests still flow through Warp's infrastructure. Now reads 'Warp uses these API keys when routing your agent requests to the model provider you've configured.' Tyler's third comment was a stylistic preference for 'need' over 'require' on the page note, which already uses 'need' here. The parallel 'require' phrasing in pricing-faqs.mdx will be normalized on PR #116. Co-Authored-By: Oz <oz-agent@warp.dev> --------- Co-authored-by: Oz <oz-agent@warp.dev>
hongyi-chen
added a commit
that referenced
this pull request
May 22, 2026
* Open umbrella PR for May 21, 2026 pricing + packaging launch Umbrella tracker for the May 21, 2026 pricing and packaging docs launch. Populates as the three thematic PRs land: - #114 - Credits, billing, and cloud-agent team billing - #115 - BYOK + custom inference endpoint + BYOLLM - #116 - Plans summary, pricing FAQs, teams copy Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): customer-supplied inference (BYOK + CIE + BYOLLM) (#115) * docs(pricing-may-2026): customer-supplied inference (BYOK + CIE + BYOLLM) Part of the May 14, 2026 pricing-and-packaging docs launch. - BYOK is now available on the Free plan; page rewritten to open eligibility, refresh model examples, and add the BYOK/CIE/BYOLLM comparison table. - New Custom Inference Endpoint (CIE) page for OpenAI Chat Completions– compatible endpoints (OpenRouter, LiteLLM, z.ai, internal gateways). Sidebar entry added under Plans and billing. - BYOLLM reframed as Enterprise-only managed inference. AWS Bedrock GA; Google Vertex AI and Azure AI Foundry on the roadmap. Cloud-native credentials now span IAM/OIDC across all three cloud providers. - 10-employee org rule applies to BYOK and CIE; larger orgs need Business or Enterprise. - Platform-credits caveats: on Business/Enterprise local agent runs, customer-supplied inference still consumes platform credits even though no AI credits are charged. - plans-and-billing/index.mdx updated to surface the new CIE page. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): note July 1 self-serve preview period in BYOK + CIE platform-credits callouts Both BYOK and CIE pages now spell out that self-serve billing for platform credits (including Business BYOK / CIE) doesn't start until July 1, 2026. Between May 14 and June 30, 2026, platform-credit consumption is visible in the Warp app's usage breakdown for transparency on Build, Max, and Business, but no platform credits are deducted from your Reload pool or counted against your spend cap. Enterprise plans are billed per contract from May 14 and aren't affected by this preview period. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): correct launch date May 14 \u2192 May 21, 2026 Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): revert BYOLLM page to main, keep changes minimal Per launch direction: keep the Enterprise BYOLLM page largely unchanged for this launch. The BYOK/CIE/BYOLLM comparison still lives on the BYOK and CIE pages, so readers landing on either of those will see the three-way framing. This restores: - The original AWS-Bedrock-focused frontmatter description and opening paragraph (instead of the cross-provider reframing). - The original 'BYOLLM currently supports AWS Bedrock only. Coming soon: Azure Foundry and Google Vertex support.' caveat. - The original 'Cloud-native credentials - Authenticate using each user's AWS IAM identity' key feature. - The original 'How is BYOLLM different from BYOK?' FAQ with its 4-row comparison table. - The original Related resources list. Drops the launch-era additions: - The 'How BYOLLM differs from BYOK and Custom inference endpoint' section with the three-way comparison table. - The :::note about centrally configured BYOK / CIE for Enterprise being a fast-follow. - The :::note about platform credits for BYOLLM-routed local runs. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): drop CIE abbreviation, narrow credit claims, remove preview-period notes, restore File locations sidebar - Restore the 'File locations' sidebar entry under Settings file (added on main by PR #110, accidentally dropped during the rebase). - Drop the 'CIE' abbreviation throughout the customer-supplied inference pages. Use the full name 'custom inference endpoint' (or 'your endpoint' / 'endpoint-routed model' in context) instead. - Narrow the 'never consumes Warp credits' claim to 'doesn't consume AI credits' on the BYOK and custom inference endpoint pages, since Business / Enterprise local agent runs still consume platform credits. - Rewrite the 'No Warp credits consumed' Key features bullet on the custom inference endpoint page so it accurately calls out the platform-credits caveat on Business / Enterprise. - Drop the 'Self-serve preview period' paragraph from the platform-credits :::note callouts on the BYOK and custom inference endpoint pages. The July 1, 2026 cutover lives only in pricing-faqs.mdx now \u2014 canonical feature pages don't carry the launch-period detail. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): de-emphasize billing in BYOK + custom inference endpoint openings, consolidate plan notes - Reframe the BYOK and custom inference endpoint opening copy around model selection and data routing instead of billing. Move the AI-credits-consumption details out of the intro and down into the dedicated billing sections where they belong. - Collapse the two stacked :::note callouts about plan availability and the 10-or-fewer-employees rule into a single, briefer note on each page. - Move the Business / Enterprise platform-credits caveat off the top of the BYOK page and into the 'Credit usage' subsection alongside the related credit details. - Trim the 'BYOK on Enterprise and Business plans' section on the BYOK page so it doesn't restate the org-size rule already covered up top. - Replace the redundant 'Plan availability' section on the custom inference endpoint page with a focused 'Centrally managed configuration' section that only covers what's still unique to that page (user-level config today, admin-managed coming later).\n - Light copy polish on phrasing in both files. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): restore original BYOK opening, narrow only the credits claim to AI credits Per follow-up review, undo the polish on the BYOK intro and restore the original three-paragraph opening verbatim: - Title back to 'Bring Your Own API Key' (Title Case) - 'Warp supports Bring Your Own Key (BYOK) for users who want to connect Warp's agents to their own Anthropic, OpenAI, or Google API accounts.' - 'This lets you use your own API keys to access models directly, giving you full control over model selection, billing, and data routing. See Model Choice for a list of supported models.' - 'BYOK provides greater flexibility in model access and ensures Warp never consumes your AI credits for requests routed through your own keys.' The only substantive change vs the original is narrowing 'credits' to 'AI credits' in that last sentence, per earlier feedback that the unqualified 'never consumes Warp credits' claim is too broad now that Business / Enterprise local runs can consume platform credits. The combined plan-availability + 10-employee :::note below the intro stays as-is. Everything below the intro (BYOK works, Enabling BYOK, billing behavior, Credit usage with the platform-credits note, ZDR, Enterprise/Business config, Related resources) is unchanged. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): soften absolute 'no AI credits / 0 credits' claims in BYOK + CIE credit sections - Drop the 'No AI credits are consumed' bullet and the 'credit transparency footer shows 0 credits used' sentence from BYOK's Credit usage subsection. Replaced with a more general framing that says inference is billed through your provider account rather than drawing from your Warp AI credits, alongside the existing platform credits caveat for Business / Enterprise. - Same softening on the custom inference endpoint page's Warp AI credits subsection \u2014 collapse the three firm bullets into one general sentence and keep the platform-credits note. This avoids the misleadingly absolute '0 credits' claim, which is inaccurate for Business / Enterprise local runs where platform credits can still apply. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): reframe custom inference endpoint intro to lead with powering Warp's agents Mirror the BYOK page's intro pattern so it's explicit upfront that a custom inference endpoint is used to power Warp's agents. New opening: Warp supports custom inference endpoints for users who want to power Warp's agents with any OpenAI-compatible inference endpoint \u2014 a model router, hosted gateway, or internal infrastructure they already run. This lets you route AI requests through your preferred provider, run inference behind your own gateway, or use a router like OpenRouter or LiteLLM, while keeping the agent experience inside Warp. No other changes. Co-Authored-By: Oz <oz-agent@warp.dev> * Cleanup pass: BYOK acronym + BYOLLM table scope - bring-your-own-api-key.mdx intro: fix the wrong BYOK expansion ('Bring Your Own Key (BYOK)') to match the page title and standard usage ('Bring Your Own API Key (BYOK)'). - bring-your-own-api-key.mdx + custom-inference-endpoint.mdx comparison tables: tighten the BYOLLM row so it reflects current launch scope ('AWS Bedrock today; Azure Foundry and Google Vertex coming soon') instead of implying all three ship at launch. Co-Authored-By: Oz <oz-agent@warp.dev> * PR #115 review: address Tyler's comments - bring-your-own-api-key.mdx 'Platform credits' note: Tyler correctly pointed out that platform credits also apply for cloud agent runs. Rewrite the line to lead with the cloud-agent case ('apply to every cloud agent run on any plan') and then cover the local-runs case ('and to local agent runs on Business and Enterprise when using BYOK, a custom inference endpoint, or BYOLLM'). - bring-your-own-api-key.mdx 'How BYOK works' opening: drop the misleading 'directly to the model provider' phrasing since requests still flow through Warp's infrastructure. Now reads 'Warp uses these API keys when routing your agent requests to the model provider you've configured.' Tyler's third comment was a stylistic preference for 'need' over 'require' on the page note, which already uses 'need' here. The parallel 'require' phrasing in pricing-faqs.mdx will be normalized on PR #116. Co-Authored-By: Oz <oz-agent@warp.dev> --------- Co-authored-by: Oz <oz-agent@warp.dev> * docs: move BYOK + Custom Inference Endpoint + Model Choice into new 'Inference & providers' sub-section under Warp Agents (#122) Group three pages that all describe how the agent's model call happens into a new sub-section under Agents > Warp Agents: agent-platform/inference/ model-choice.mdx (moved from capabilities/) bring-your-own-api-key.mdx (moved from support-and-community/plans-and-billing/) custom-inference-endpoint.mdx (moved from support-and-community/plans-and-billing/) Why: BYOK and CIE were sidebared under 'Support & Community > Plans and billing' but they're really about agent inference routing, not billing. Grouping them with Model Choice gives readers a single place to learn about model selection + bring-your-own inference. BYOLLM (Enterprise) stays at its existing location and cross-links to the new section. Changes: * 3 files moved to src/content/docs/agent-platform/inference/. * sidebar.ts: new 'Inference & providers' sub-group under Warp Agents (between Agent context and Interactive code review). Model Choice removed from Capabilities, BYOK + CIE removed from Plans and billing. * vercel.json: 49 model-choice + 17 BYOK existing redirects re-pointed directly to /agent-platform/inference/... (no chain hops). 3 new 308 redirects added for the old slugs. * Comprehensive inbound-link sweep: every internal reference to the old URLs across all .mdx files updated to the new /agent-platform/inference/ URLs. capabilities/index.mdx and plans-and-billing/index.mdx pruned to reflect the move (with cross-links to the new section). Validated with npm run build (334 pages, no errors). Co-authored-by: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): credits, billing, and service-account model (#114) * docs(pricing-may-2026): credits, billing, and service-account model Part of the May 14, 2026 pricing-and-packaging docs launch. - Reload credits on self-serve plans are now user-scoped (Build/Max/Business); pre-launch pooled balances are grandfathered and drain first. - Team-wide auto-reload uses a single admin-managed monthly spend cap and triggers when any user drops below 100 credits. - Service-account / team-API-key billing waterfall on self-serve bills the team owner: owner's plan-included credits → owner's Reload credits. Attribution stays on the service account; billing rolls up to the owner. Auto-reload OFF and ON outcomes documented explicitly. - Enterprise service-account traffic draws from the team-scoped pool and falls to pay-as-you-go (PAYG) when depleted. - Membership-change consequences for Reload credits: user leaves, admin removes member, admin deletes team, user downgrades to Free. Rejoining restores non-expired credits. - Active-subscription requirement called out explicitly. - Platform credits draw from the same Reload pool as AI and compute credits. - Cross-page billing copy cleanup in team-access-billing-and-identity.mdx and api-keys.mdx aligns with the new model. - New 'Billing for agent identity runs' subsection on agents.mdx. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): add July 1 platform-credits preview note + trim legacy plan caution - credits.mdx: add a :::note in the Platform credits section explaining the self-serve preview period (May 14 \u2013 June 30, 2026). On self-serve plans, platform credits are visible in the usage breakdown for transparency but not billed; charging starts July 1, 2026. Enterprise unaffected and billed per contract from May 14. - add-on-credits.mdx: trim the legacy plan caution to a brief pointer at Overages (Legacy) rather than calling out Pro/Turbo/Lightspeed by name with extra context that's no longer current. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): correct launch date May 14 \u2192 May 21, 2026 Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): drop self-serve preview-period note from credits.mdx The July 1, 2026 cutover detail is launch-period guidance that lives only in pricing-faqs.mdx going forward \u2014 canonical feature pages describe the durable platform-credits model without the temporary preview window. Pricing FAQs still cover when self-serve billing starts. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): drop service-account / agent-identity / task-billing-principal terminology, use 'cloud agent runs' framing Per follow-up review, this terminology added noise without clarifying billing for readers. Simplify to talk about cloud agent runs directly: - add-on-credits.mdx: rename the 'Service account and team-scoped API key requests' subsection to 'Cloud agent runs on team plans'. Drop the 'task billing principal' framing and the 'attribution stays on the service account, billing rolls up' explanation. State the rule plainly: cloud agent runs not initiated by a specific team member are billed to the team owner on self-serve plans. - credits.mdx: same treatment on the 'Service account and team-scoped API key billing' section \u2014 now 'Cloud agent runs on team plans'. Drop the task-billing-principal explanation; keep the self-serve waterfall and the Enterprise team-pool + PAYG fallback. - agents.mdx: remove the 'Billing for agent identity runs' subsection entirely. It duplicated the billing model already covered on the cloud-agents billing page and used the disliked agent-identity framing. The Agent identities page is for the feature concept; the billing model is plan-level and lives elsewhere. - team-access-billing-and-identity.mdx: rename 'Team API key, scheduled, or agent identity runs' to 'Team API key or scheduled cloud agent runs' in the integration credit-precedence bullet, the Additional notes section, and the Staying aware of usage summary. Drop the 'attribution stays on the service account or agent identity' explanation. Co-Authored-By: Oz <oz-agent@warp.dev> * Remove PAYG mentions from Enterprise plan billing copy Drop the pay-as-you-go (PAYG) fallback language from the Enterprise bullets in cloud-agent team billing and credits — PAYG is an internal contract detail. The Enterprise sections now describe runs as drawing from the team-scoped credit pool, with overage behavior governed by the Enterprise contract terms. Co-Authored-By: Oz <oz-agent@warp.dev> * Remove legacy plan / Overages mentions from launch-touched docs - add-on-credits.mdx: drop the 'replaces Warp's old pay-as-you-go Overages' intro sentence and the Pro/Turbo/Lightspeed legacy caution. - team-access-billing-and-identity.mdx: collapse the supported / not-supported plan sub-bullets into a single Build/Max/Business (or Enterprise) line; the Pro/Turbo/Lightspeed not-supported note is no longer relevant. Co-Authored-By: Oz <oz-agent@warp.dev> * Cleanup pass: PAYG, BYOLLM scope, model versions - reference/cli/api-keys.mdx: drop the lingering '(with pay-as-you-go fallback if enabled in the contract)' parenthetical from the Personal API keys Enterprise bullet, matching the phrasing used elsewhere on this PR. - credits.mdx: tighten BYOLLM scope to reflect actual launch state (AWS Bedrock today; Azure Foundry and Google Vertex coming soon) in both the AI/compute/platform overview and the platform-credits eligibility bullets. Also normalizes 'Amazon Bedrock' to 'AWS Bedrock' to match the canonical BYOLLM page. - credits.mdx: refresh the example model list from Claude Opus 4.6 / 4.5 / GPT-5.4 / GPT-5.3 Codex / Gemini 3 Pro to the current set (Claude Opus 4.7, Claude Sonnet 4.6, GPT-5.5, Gemini 3.1 Pro) so PR #114 and PR #115's BYOK page cite the same models. Co-Authored-By: Oz <oz-agent@warp.dev> * PR #114 review: address Isaiah's comments - team-access-billing-and-identity.mdx integrations requirement bullet: separate Enterprise from the Add-on Credits framing. Enterprise has its own team credit pool per contract, so grouping it under 'plan that supports Add-on Credits' is incorrect. The new bullet covers Build/Max/Business with Add-on Credits and Enterprise with the team credit pool separately. - add-on-credits.mdx: normalize 'Reload credits' references in the body to 'Add-on credits' so the page is internally consistent with its title and the first half of the page. The switch in the second half was a leftover from an earlier rename attempt. - add-on-credits.mdx 'When membership or subscription changes' section: rewrite to clarify that individual Add-on credits stay with the user across plan changes (Isaiah pointed out the old 'downgrade to Free forfeits Reload credits' claim is no longer accurate). The remaining bullets now scope explicitly to team-pooled grandfathered credits, and the surrounding 'requires an active subscription' caution is removed since individual credits persist regardless. Co-Authored-By: Oz <oz-agent@warp.dev> * Drop 'no longer pooled' historical framing on add-on-credits.mdx The 'Teams using Add-on Credits' lead-in said 'Add-on credits are tied to individual users — they are no longer pooled across the team.' Readers don't need the 'no longer' transition framing; the current state is the only one that matters. Now reads 'Add-on credits are scoped to individual users.' Co-Authored-By: Oz <oz-agent@warp.dev> * Remove the pre-May 2026 grandfathering caution callout Drops the 'Grandfathering for pre-May 2026 pooled credits' :::caution block from add-on-credits.mdx. The historical transition isn't worth calling out in a permanent doc page. Co-Authored-By: Oz <oz-agent@warp.dev> * Restore 'active subscription' caution and 12-month qualifier Earlier I over-interpreted Isaiah's 'this isn't right anymore... if you churn you still can use your individual reload credits' comment and removed the broader 'Add-on credits require an active subscription' caution + the trailing 'as long as you have an active subscription' qualifier. Isaiah's correction was narrower than that — he was flagging the specific 'Downgrading to Free forfeits Reload credits tied to your previous team' bullet, which incorrectly conflated team-pooled and individual credits. Restoring both pieces of copy: - The active-subscription caution before 'When membership or subscription changes'. - The 'as long as you have an active subscription' qualifier on the bottom 12-month-validity note. The lead-in for the 'When membership or subscription changes' section is rewritten so it no longer over-claims 'even across plan changes'. It now reads: 'Individual Add-on credits stay with the user who purchased or was allocated them, so they're not lost when team membership changes alone.' This keeps Isaiah's narrower correction while staying consistent with the restored caution. Co-Authored-By: Oz <oz-agent@warp.dev> * PR #114 review pass: align with Isaiah's Slack clarifications - add-on-credits.mdx: rework the "active subscription" caution and the "When membership or subscription changes" intro to match Isaiah's confirmation that Add-on credits are tied to the team, not to the user's service agreement. Drop the "team-pooled" qualifier from the membership bullets (Add-on credits are tied to the team regardless of whether they came from a pooled or individual purchase), and rename the section header to "When team membership changes" since subscription lapses are no longer in scope. Keep the existing restrictive "Plan changes and cancellations" paragraph and 12-month note untouched per Hong Yi's "let's leave it as is" comment. - Normalize "Reload credits" / "Reload pool" / "Reload settings" to "Add-on credits" / "Add-on credit pool" / "Add-on credit settings" across the four other PR files (team-access-billing-and-identity, credits, api-keys, enterprise billing) so the launch copy matches the canonical product name in AGENTS.md's glossary and the title of add-on-credits.mdx. "auto-reload" stays lowercase as the action. Co-Authored-By: Oz <oz-agent@warp.dev> * PR #114: drop "paid" qualifier from "leaves a team" bullet Isaiah's nit on line 115: any team that owns Add-on credits is by definition on a paid plan (Free can't buy them), so "paid" is redundant in the bullet header. Drop the qualifier. Co-Authored-By: Oz <oz-agent@warp.dev> --------- Co-authored-by: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): plans, FAQs, and team-management copy (#116) * docs(pricing-may-2026): plans, FAQs, and team-management copy Part of the May 14, 2026 pricing-and-packaging docs launch. - May 2026 plan summary on plans-pricing-refunds.mdx — qualitative blurbs for Free/Build/Max/Business/Enterprise. Links out to warp.dev/pricing. Platform-credits one-liners on Business and Enterprise bullets. - Pricing FAQs overhaul on pricing-faqs.mdx: - Removed superseded Oct 30 2025 pricing change FAQ section. - Refreshed plan recommendations (Build/Max/Business/Enterprise). - Added evergreen FAQs: multi-seat credits, 'more AI usage' options, auto-reload for teams, service-account waterfall, BYOK/CIE, and 'How do platform credits factor in?'. - New 'Warp's pricing change FAQs (May 14 2026)' section covering seat limits, Reload-credit attribution change, Max plan allowance change + grandfathering, BYOK on Free, CIE, and ZDR clarifications. - Replaced 'automatically enforced team-wide ZDR' with the new model-provider ZDR vs admin-configurable data controls distinction. - Renamed 'Add-on Credits' references to 'Reload credits' (slug stays). - Team-management consequences added to teams.mdx in both knowledge-and-collaboration and enterprise/team-management: ::caution callouts covering leave/remove/delete + Reload-credit forfeiture + rejoin restoration + active-subscription requirement. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): add platform-credits preview FAQ, trim legacy plan content - Add a new 'When do platform credits start being charged on self-serve plans?' FAQ in the May 14, 2026 pricing change section. Explains the May 14 → June 30 preview window (visible but not billed) and the July 1, 2026 cutover for self-serve cloud agent runs and Business BYOK / CIE usage. Calls out that the date aligns with the rest of the May 2026 self-serve transition and that Enterprise is billed per contract from May 14 and isn't affected. - Remove the per-legacy-plan Pro / Turbo / Lightspeed bulleted feature descriptions from the plan recommendation section. Keep a single pointer to Overages (Legacy) instead. - Remove the two stale 'continue to use Overages (Legacy) until their first renewal after December 1, 2025' caveats from the Lite-model and credit-reset FAQs — that cutoff passed months ago. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): correct launch date May 14 \u2192 May 21, 2026 Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): drop Max credit-allowance reduction from launch The Max plan is no longer changing its monthly credit allowance as part of the May 21, 2026 launch, so remove the associated FAQ and grandfathering content: - Drop 'Max plan credit allowance changes' from the FAQ-section intro list. - Remove the 'Is the Max plan's monthly credit allowance changing?' FAQ in full, including the grandfathering bullets for annual and monthly Max subscribers. - Trim 'Max credit allowance change' from the 'This date lines up with...' sentence in the platform-credits preview FAQ, leaving seat limits, user-scoped Reload credits, and related grandfathering as the surviving transition items. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): drop service-account framing from FAQs, clarify Free plan platform-credits billing Two changes to pricing-faqs.mdx: 1. Rewrite the 'How are service account / team-scoped API key requests billed on self-serve plans?' FAQ to drop the 'service account', 'agent identity', and 'task billing principal' terminology. New heading reads 'How are cloud agent runs on team plans billed when no individual user triggered them?'. Body is plain-language: cloud agent runs not initiated by a specific team member are billed to the team owner on self-serve plans, with the existing waterfall and auto-reload behavior preserved. 2. Clarify the platform-credits preview FAQ to call out that Free plan is unchanged. The preview period and July 1 cutover are self-serve paid plan transitions; Free plan cloud agent runs already consume from your plan allowance and don't change on July 1. Tightens the FAQ to say 'self-serve paid plans (Build,\n Max, Business)' instead of 'self-serve customers' so the scope is\n unambiguous, and adds an explicit 'Free plan' callout next to the\n Enterprise callout. Co-Authored-By: Oz <oz-agent@warp.dev> * Drop PAYG mention from Enterprise note in cloud-agent-runs FAQ Co-Authored-By: Oz <oz-agent@warp.dev> * Address PR #116 review feedback - Convert Reload-credit team-membership :::caution / :::note callouts to plain prose under their existing subsections (enterprise teams.mdx, knowledge-and-collaboration/teams.mdx). - Remove the May 2026 plan snapshot from plans-pricing-refunds.mdx and drop legacy Overages bullets in the same file. - Strip legacy-plan (Pro/Turbo/Lightspeed) mentions and the Overages (Legacy) page entirely: delete overages-legacy.mdx, drop the index bullet, drop the sidebar entry, and repoint vercel.json's four legacy-overages redirects to add-on-credits. - Stop calling Build and Max single-user; describe them as for individual developers (teams up to 10). - Drop explicit Reload denominations ($10 / 400, etc.) from pricing-faqs and point readers to add-on-credits. - Remove the What happened to the Lite model? FAQ. - Trim the platform-credits-preview FAQ tail (date-lines-up, Free plan, Enterprise wrap-up paragraphs). - Drop the CIE acronym in the Custom Inference Endpoint FAQ. - Remove (formerly/previously called Add-on Credits) parentheticals; Reload credits has always been the name. Co-Authored-By: Oz <oz-agent@warp.dev> * Add SOC 2, ZDR, BYOLLM, and multi-harness orchestration FAQs Five new FAQs added to the main pricing-faqs.mdx body: - Does Warp have a SOC 2 Type 2 attestation? - points to Trust Center. - Does Warp have Zero Data Retention policies with LLM providers? - lists the providers (Anthropic, OpenAI, Google, Fireworks AI) and the contractual commitments (no training, deletion within fixed window). - How can I enable Zero Data Retention in Warp? - individual (Help Improve Warp toggle) and organization-wide (Admin Panel on Business and Enterprise) options. - Does Warp support other model routers or 'Bring Your Own LLM'? - clarifies that BYOLLM covers AWS Bedrock, Google Vertex AI, and Azure AI Foundry on Enterprise, and that arbitrary in-house routers aren't supported by default today. - What features are available during multi-harness orchestration beta? - flags that multi-harness orchestration is beta and Agent Memory is in Research Preview, with the standard 'availability, limits, and pricing may change' caveat. The launch-section ZDR FAQ is trimmed to point at the new general FAQs instead of repeating the provider list and setup details. Co-Authored-By: Oz <oz-agent@warp.dev> * Cleanup pass: BYOLLM scope, naming, AI token FAQ - Enterprise plan answer + platform-credits FAQ + Custom Inference Endpoint FAQ + new BYOLLM/multi-router FAQ: tighten BYOLLM scope so it reflects current launch state (AWS Bedrock today; Azure Foundry and Google Vertex coming soon) instead of implying all three ship. - New BYOLLM/multi-router FAQ: normalize provider names ('Google Vertex AI' -> 'Google Vertex', 'Azure AI Foundry' -> 'Azure Foundry') to match the canonical short forms used by the BYOLLM page. - 'What counts as an AI token?' FAQ: drop the outdated claim that paid plans get temporarily disabled at the monthly limit. Paid plans now continue via Reload credits and auto-reload; only the Free plan pauses access. Cross-link to the 'more AI usage' FAQ for the full list of options. Co-Authored-By: Oz <oz-agent@warp.dev> * PR #116 review: normalize 'require' -> 'need' for plan-availability copy Tyler's stylistic preference (raised on PR #115) was for 'need' over 'require' on the BYOK/CIE plan-availability sentences. The PR #115 page already uses 'need'; the equivalent phrasing in pricing-faqs.mdx ('Companies or organizations with more than 10 employees require a Warp Business or Enterprise plan to use these features') now reads 'need' in both places (BYOK FAQ + Custom Inference Endpoint FAQ). Co-Authored-By: Oz <oz-agent@warp.dev> * Align teams.mdx Reload credit consequences wording with PR #114 PR #116's "Reload credit consequences when leaving or removing members" section in both `enterprise/team-management/teams.mdx` and `knowledge-and-collaboration/teams.mdx` used "scoped to the individual user under your team" framing, which read as inconsistent with PR #114's authoritative `add-on-credits.mdx` model: - PR #114 establishes that Add-on Credits are *both* user-scoped (each user has their own balance) AND tied to the team they were purchased under (lose access on membership changes). - PR #114 also says "The admin pays a prorated rate for your seat on rejoin", which PR #116 was missing. - The team-deletion bullet now matches PR #114 verbatim ("Any remaining Reload credits tied to the team are no longer usable"). This commit rewrites the section in both files to: - Lead with "scoped to each individual user but tied to the team they were purchased under" to capture both halves of the model. - Mirror PR #114's bullets exactly, including the prorated-rate detail. - Keep the grandfathered pooled balance :::note unchanged. Validated with npm run build (334 pages, no broken links). Co-Authored-By: Oz <oz-agent@warp.dev> * Align auto-reload FAQ with PR #114's add-on-credits.mdx constraints PR #114's `add-on-credits.mdx` documents two auto-reload constraints that PR #116's "How does auto-reload work for teams?" FAQ was missing: - **Auto-reload on**: "While auto-reload is on, individual users cannot purchase Add-on credits manually." - **Auto-reload off**: "When auto-reload is off, eligible team members can purchase Add-on credits for themselves, as long as the team stays below the team-wide spend cap." This commit folds both into the FAQ so the pricing-faqs.mdx and add-on-credits.mdx descriptions match. Validated with npm run build (334 pages, no broken links). Co-Authored-By: Oz <oz-agent@warp.dev> * Remove ephemeral grandfathered Reload credits note from canonical teams.mdx pages Per review feedback, the grandfathered pooled Reload credits :::note is launch-ephemeral messaging that doesn't belong on canonical docs pages. It still lives on the pricing FAQs page (under "How do credits work for multi-seat teams?" and the auto-reload-for-teams FAQ), which is the appropriate home for time-bound launch context. Removes the :::note block from: - src/content/docs/enterprise/team-management/teams.mdx - src/content/docs/knowledge-and-collaboration/teams.mdx Validated with npm run build (334 pages, no broken links). Co-Authored-By: Oz <oz-agent@warp.dev> * Update src/content/docs/enterprise/team-management/teams.mdx Co-authored-by: Rachael Rose Renk <91027132+rachaelrenk@users.noreply.github.com> * Update src/content/docs/knowledge-and-collaboration/teams.mdx Co-authored-by: Rachael Rose Renk <91027132+rachaelrenk@users.noreply.github.com> --------- Co-authored-by: Oz <oz-agent@warp.dev> Co-authored-by: Rachael Rose Renk <91027132+rachaelrenk@users.noreply.github.com> * docs(pricing-may-2026): polish pass on umbrella PR #119 (#126) * docs(polish): pre-release polish pass on the May 21, 2026 pricing umbrella Polish sweep across the May 21 pricing+packaging changes before #119 ships: Pass 1 — Terminology and capitalization * Standardize on 'add-on credits' (sentence case, common noun) across the umbrella. Mid-sentence is lowercase 'add-on credits'; sentence/heading/ bullet-start is 'Add-on credits'. Page H1 + frontmatter title updated. * Drop the now-redundant 'Reload credits = Add-on credits' callout from add-on-credits.mdx and the inline '(also known as add-on credits)' parentheticals. * Treat 'custom inference endpoint' as a descriptive noun, not a proper noun: sentence case in headings, lowercase mid-sentence/link text. * BYOK: Title Case as the feature name first reference per page, BYOK acronym thereafter. Fix 'bring your own API key (BYOK)' → 'Bring Your Own API Key (BYOK)'. * Standardize 'Auto reload' → 'auto-reload' (hyphenated, lowercase mid- sentence). Pass 2 — Structural and rendering fixes * Restore the 8-tab indentation regression on the Settings file sidebar group in src/sidebar.ts. * Fix the broken permissions table in enterprise/team-management/teams.mdx (extra leading | on rows caused phantom empty column). * Fix the same broken table in knowledge-and-collaboration/teams.mdx. * Remove three '{/* TODO: Add screenshot */}' MDX comments from enterprise teams.mdx left over from drafting. * knowledge-and-collaboration/teams.mdx: 'pressing ENTER' → 'pressing Enter' per style-guide key-name capitalization, drop trailing ' ' GitBook artifact, fix duplicate 'A user leaves a team' bullet (second one should have been 'An admin removes a member'). * Same duplicate-bullet fix in enterprise/team-management/teams.mdx. * plans-and-billing/index.mdx: 'Inference & providers' pointer now targets /agent-platform/inference/model-choice/ (the section landing) instead of the BYOK page. Pass 3 — Content polish * custom-inference-endpoint.mdx: 'Oz Cloud Agents' → 'Cloud Agents' (per the 'no Oz prefix on agents' terminology rule; BYOK already used 'Cloud Agents'). * bring-your-own-api-key.mdx: heading 'How BYOK differs from Custom inference endpoint and BYOLLM' → 'How BYOK differs from custom inference endpoints and BYOLLM' (sentence case). * custom-inference-endpoint.mdx 'Other AI features' section: replace vague one-liner with a link to BYOK's feature table (single source of truth). * bring-your-own-api-key.mdx: move 'You can update or replace your keys anytime' out of the conditional 'If your key:' list and into its own paragraph. Pass 4 — Cross-page consistency * Cloud-agent-runs-on-team-plans waterfall: pricing-faqs.mdx is the canonical source. credits.mdx and add-on-credits.mdx now summarize and link there instead of duplicating the mechanics. * BYOLLM scope language: every BYOLLM mention now reads 'AWS Bedrock today (with Azure Foundry and Google Vertex coming soon)' rather than 'AWS Bedrock or Google Vertex' (which implied Vertex is GA). Validated: npm run build passes (334 pages, no errors); zero stale /support-and-community/plans-and-billing/(bring-your-own-api-key| custom-inference-endpoint) or /agent-platform/capabilities/model-choice URLs remain in src/content/docs/. Co-Authored-By: Oz <oz-agent@warp.dev> * revert BYOLLM scope wording in enterprise/billing.mdx per user request Co-Authored-By: Oz <oz-agent@warp.dev> * trim repetitive BYOLLM scope mentions from passing references Keep 'AWS Bedrock today, with Azure Foundry and Google Vertex coming soon' only where it's the canonical BYOLLM explanation: * Comparison tables on the BYOK and CIE pages. * The dedicated 'Does Warp support other model routers or BYOLLM?' FAQ in pricing-faqs.mdx. * The May 21 'What is the new custom inference endpoint feature?' FAQ comparison block that explains each of the three options. Drop the scope parenthetical from passing mentions on: * platform-credits.mdx (4 sites) * credits.mdx (2 sites) * pricing-faqs.mdx Enterprise plan description and 'How do platform credits factor in?' answer (2 sites) Co-Authored-By: Oz <oz-agent@warp.dev> --------- Co-authored-by: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): cleaner anchor for May 21, 2026 pricing FAQ section (#127) * shorten May 2026 pricing FAQ section header for cleaner shareable anchor Renames the section header from 'Warp's pricing change FAQs (May 21, 2026)' to 'May 21, 2026 pricing changes' so the auto-generated anchor is #may-21-2026-pricing-changes (shorter, easier to share). Co-Authored-By: Oz <oz-agent@warp.dev> * capitalize '[Platform credits]' link text at bullet start in enterprise/billing.mdx Co-Authored-By: Oz <oz-agent@warp.dev> * shorten heading to 'May 2026 pricing changes' Co-Authored-By: Oz <oz-agent@warp.dev> --------- Co-authored-by: Oz <oz-agent@warp.dev> * Polish May 2026 pricing FAQ section (#128) * Polish May 2026 pricing FAQ section Rewrites the section to read more naturally, fix factual errors, drop the ZDR sub-FAQ, and add two new FAQs. - Reduce em dashes and AI-sounding tone throughout - Fix platform credits FAQ: remove false claim about consumption being visible in the Warp app, and correct that ALL self-serve plans (including Free) are in the May 21 - June 30, 2026 preview period - Delete the ZDR sub-FAQ (nothing changes there) - Add note in the add-on credits FAQ that anyone on the team can now purchase add-on credits - New FAQ: 'What if my team is already above the new seat limit?' - New FAQ: 'I'm a team admin. What do I need to do?' Co-Authored-By: Oz <oz-agent@warp.dev> * Add FAQ: What happens to my add-on credits if I leave the team? Mirrors the team-membership behavior already documented on the add-on-credits page (leave/removed/team-deleted) and links back to it for full details. Closes the loop on user-scoped add-on credits: each user has their own balance, but that balance is still tied to the team that paid for it. Co-Authored-By: Oz <oz-agent@warp.dev> * Apply suggestion from @oz-for-oss[bot] Co-authored-by: oz-for-oss[bot] <277970191+oz-for-oss[bot]@users.noreply.github.com> --------- Co-authored-by: Oz <oz-agent@warp.dev> Co-authored-by: oz-for-oss[bot] <277970191+oz-for-oss[bot]@users.noreply.github.com> * Pre-ship consistency audit fixes for May 21, 2026 launch (#133) * Pre-ship consistency audit fixes for May 21, 2026 launch Sweeps the umbrella branch one last time for terminology drift, factual gaps, and broken cross-references before shipping to main. Plans & billing: - index.mdx: list platform credits and call out the three credit buckets in the opening paragraph; rename Plans & Pricing link to match its page title; use canonical 'auto-reload' wording. - platform-credits.mdx: add a preview-period callout (May 21 - June 30, 2026, all self-serve plans); flag that no platform-credit deductions appear in usage views during preview; lowercase compute-credits link text. - pricing-faqs.mdx: align preview-period scope at line 154-155 with the canonical 'all self-serve plans (Free, Build, Max, Business)' framing used elsewhere in the file. - credits.mdx: add the missing auto-reload-off case ('blocked, insufficient credits') to the cloud-agents-on-team-plans summary; lowercase compute-credits link text. - plans-pricing-refunds.mdx: sentence-case sidebar label; canonical 'auto-reload' wording. - enterprise/support-and-resources/billing.mdx: use canonical BYOLLM scope ('AWS Bedrock today, with Azure Foundry and Google Vertex coming soon') instead of implying all three are live. Inference & providers: - bring-your-own-api-key.mdx: 'Business and Enterprise' ordering for the BYOK config heading and intro bullet. - bring-your-own-llm.mdx: Title Case the frontmatter title; bump three Claude Sonnet 4.5 examples to 4.6 (the launch-canonical version); fix 'Bring Your Own Key' -> 'Bring Your Own API Key' in the BYOK FAQ comparison. Cross-references: - cloud-agents/faqs.mdx: 'Bring Your Own Key (BYOK)' -> 'Bring Your Own API Key (BYOK)' in the BYOK note; replace the stale 'will support AWS Bedrock and Google Vertex' line with a BYOLLM pointer. - cloud-agents/overview.mdx: BYOK rename in the cloud-agents note; drop the stale 'Not supported: Pro, Turbo, Lightspeed, legacy Business' bullet (the supported list above already covers it). - cloud-agents/team-access-billing-and-identity.mdx: lowercase 'Add-on credits' mid-sentence across the waterfall blocks; tag platform-credit references with the May 21 - June 30, 2026 preview-period caveat. - cloud-agents/warp-hosting.mdx: capitalize 'Enterprise' plan name. - reference/cli/api-keys.mdx: lowercase 'Add-on credits' mid-sentence; add the missing auto-reload-off case to the team API key waterfall. - reference/api-and-sdk/troubleshooting/errors/insufficient-credits.mdx: full rewrite for the user-scoped add-on credits model. Distinguishes user-triggered (own pool) vs team-API-key/scheduled (team owner's pool); fixes a malformed JSON example with duplicate keys; links to add-on credits, platform credits, and the canonical pricing FAQ. Verification: npm run build = 334 pages, no broken links. Grep returns zero hits for ZDR May-2026 anchor, Reload Credits, Pro/Turbo/ Lightspeed plan names, Custom Inference Endpoint Title Case, and unhyphenated 'Auto reload'. Co-Authored-By: Oz <oz-agent@warp.dev> * Use Claude Opus 4.7 (the latest model) in BYOLLM examples Co-Authored-By: Oz <oz-agent@warp.dev> * Title-case 'Bring Your Own API Key' and 'Bring Your Own LLM' feature names in BYOK and CIE pages These are product feature names per the docs style guide; sentence-case treatment was inconsistent with the page titles and intro bodies that already use Title Case. Co-Authored-By: Oz <oz-agent@warp.dev> * Apply suggestion from @oz-for-oss[bot] Co-authored-by: oz-for-oss[bot] <277970191+oz-for-oss[bot]@users.noreply.github.com> * Drop redundant preview-period inline notes Removes four inline May 21 - June 30, 2026 preview-period mentions that were redundant given the dedicated FAQ in pricing-faqs.mdx (#when-do- platform-credits-start-being-charged-on-self-serve-plans). Co-Authored-By: Oz <oz-agent@warp.dev> --------- Co-authored-by: Oz <oz-agent@warp.dev> Co-authored-by: oz-for-oss[bot] <277970191+oz-for-oss[bot]@users.noreply.github.com> --------- Co-authored-by: Oz <oz-agent@warp.dev> Co-authored-by: Rachael Rose Renk <91027132+rachaelrenk@users.noreply.github.com> Co-authored-by: oz-for-oss[bot] <277970191+oz-for-oss[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds documentation that covers where Warp stores files on each platform, motivated by customer feedback that Warp's Windows config layout is undocumented and that
docs.warp.dev/terminal/windows/tab-configs/references the macOS-only~/.warp/tab_configs/path. Filed concurrently as warpdotdev/warp#11356.What's in this PR
New page:
terminal/settings/file-locationsSingle reference that lists every directory and file Warp reads or writes on disk, organized into three buckets (portable user data, non-portable config, non-portable state) plus the cross-platform
~/.warp/carve-out. Covers macOS, Windows, and Linux for both Stable and Preview channels, and includes a "Symlinking Warp's config from WSL" section for users running Warp on Windows alongside WSL — the exact workflow the original customer feedback called out.Sidebar entry added under Terminal → Settings file, after All settings reference.
Updates to existing pages
terminal/windows/tab-configs.mdx— replaces the bare~/.warp/tab_configs/mention with a per-OS Tabs block (macOS / Windows / Linux for both Stable and Preview), and links to the new reference page.terminal/appearance/custom-themes.mdx— fixes thebackground_image: path:YAML note to call out the per-OS themes directory instead of only the macOS path.terminal/settings/index.mdx— cross-links the new reference page from the File location section and Related pages.support-and-community/troubleshooting-and-support/logging-out-and-uninstalling.mdx:XDG_STATE_HOME→XDG_DATA_HOMEfor themes/launch configs (the variable was wrong; the fallback path happened to land in the right place).\warp\Warp-Preview\to\warp\WarpPreview\(verified againstdirectories::ProjectDirsbehavior withapplication_name = "WarpPreview"and confirmed by warp_core tests).~/.warpremoval on Windows and Linux (MCP config and skills live in the home directory on every platform).src/sidebar.ts— adds the new page to the Settings file group.How the paths were verified
Paths in this PR were validated against
warp-internalsource rather than inferred from the docs:warp_core::paths::data_dir,config_local_dir,state_dir,cache_dir, and thewarp_home_*helpers inwarp-internal/crates/warp_core/src/paths.rs.paths_tests.rscases that assert the exact Windows project path iswarp\Warp(Stable),warp\WarpPreview(Preview), andwarp\WarpOss(OSS), withcache_dir=AppData\Local\warp\WarpOss\cacheandstate_dir=AppData\Local\warp\WarpOss\data.app/src/user_config/mod.rs(themes, tab_configs, default_tab_configs, launch_configurations, workflows all live underdata_dir()).app/src/keyboard.rs(keybindings.yaml atconfig_local_dir().join("keybindings.yaml")).feedbackskill'sreferences/logs.mdfor log paths.Validation
python3 .agents/skills/check_for_broken_links/check_links.py --internal-only→ 0 broken links across 2586 internal links / 331 files.python3 .agents/skills/style_lint/style_lint.py --changed→ no new issues introduced by this PR. The 6 warnings it surfaces are all on pre-existing lines I didn't touch (the "Tab Configs" headers — a proper Warp feature name explicitly exempted byAGENTS.md— and asettings.tomlfilename reference flagged as a UI element).Conversation: https://staging.warp.dev/conversation/4d92f7ea-4b06-4887-81a2-2441323b14fb
Run: https://oz.staging.warp.dev/runs/019e4250-e3ba-7642-bc98-74b891ed569c
This PR was generated with Oz.