docs(pricing-may-2026): cross-page cleanup for user-scoped Reload + leave-team warnings#112
Merged
Merged
Conversation
…eave-team warnings Update four pages that were written under the old pooled Add-on Credits model to align with the May 14, 2026 launch. * team-access-billing-and-identity.mdx — Rewrite the integration credit waterfall, the user-triggered / team API key / scheduled / agent identity run bullets, and the 'Staying aware of usage' summary to reflect the new self-serve model (user-scoped Reload credits, team-owner billing for service-account runs subject to the team-wide spend cap) plus the Enterprise team-scoped pool with PAYG fallback. Add a Related resources section linking to Reload credits, platform credits, and the credits overview. * reference/cli/api-keys.mdx — Rewrite the Personal vs team API keys bullets so personal keys no longer claim to draw from team Add-on Credits, and team keys describe the team-owner waterfall (self-serve) and team-scoped pool (Enterprise). * knowledge-and-collaboration/teams.mdx — Add cautions to 'Leaving and deleting teams' covering: leaving a paid team forfeits access to Reload credits (rejoining restores unused, non-expired ones), deleting a team removes everyone's access, and Reload credits require an active subscription (downgrading to Free forfeits). * enterprise/team-management/teams.mdx — Add an explicit 'Reload credit consequences when leaving or removing members' subsection covering the same scenarios, plus the admin-removes-member case specific to this surface, and the active-subscription requirement. No per-plan monthly credit counts are hard-coded; users are pointed at warp.dev/pricing and the new Reload credits / platform credits pages. The companion edit to agent-platform/cloud-agents/agents.mdx (the new Agent identities page) is deferred — that file lives on main via the orchestration-launch PR #98 and has not been merged into the hyc/plan-updates umbrella yet. It will be picked up after the umbrella is rebased onto main. 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 updates cross-page billing documentation for user-scoped Reload credits, team-owner billing for automated runs, and leave/delete-team warnings. The direction matches the stated pricing-model cleanup, and I did not find security concerns in this docs-only diff or spec drift because no approved spec context was provided.
Concerns
- Two new references still link to
credits/#cloud-agent-credits, but the credits page exposes the relevant section at#compute-credits, so those anchors will be broken. - The general Teams page describes user-scoped Reload-credit consequences as applying to any paid team, which conflicts with the PR's own Enterprise model where runs use a team-scoped credit pool.
Verdict
Found: 2 critical, 1 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
| When a user triggers an agent through an integration (like Slack or Linear), the run draws from credits in a specific order. It starts with any [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits) the user has, then moves to the user's base credits, followed by the team's Reload Credits, and finally the user's own Reload Credits. Enterprises may have different payment options and credit plans that affect this flow. If all applicable credit sources are exhausted, integrations and cloud agents will not work until credits are added. | ||
| When a user triggers an agent through an integration (like Slack or Linear), the run draws from credits based on who the run is billed to: | ||
|
|
||
| * **User-triggered runs on Build, Max, or Business** - Warp draws from any [cloud agent credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits) the user has, then the user's plan-included credits, then the user's Reload credits. Reload credits are scoped to the individual user and are not shared across the team. |
Contributor
There was a problem hiding this comment.
🚨 [CRITICAL] The #cloud-agent-credits anchor does not exist on the credits page; link this to the Compute credits section so readers don't hit a broken anchor.
Suggested change
| * **User-triggered runs on Build, Max, or Business** - Warp draws from any [cloud agent credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits) the user has, then the user's plan-included credits, then the user's Reload credits. Reload credits are scoped to the individual user and are not shared across the team. | |
| * **User-triggered runs on Build, Max, or Business** - Warp draws from any [cloud agent credits](/support-and-community/plans-and-billing/credits/#compute-credits) the user has, then the user's plan-included credits, then the user's Reload credits. Reload credits are scoped to the individual user and are not shared across the team. |
| * Runs are tied to the triggering user's identity | ||
| * Credits are consumed starting with any credit grants specifically allocated for cloud agent usage, then the user's base credits, followed by the team's Reload Credits, and finally the user's own Reload Credits | ||
| * Runs are tied to the triggering user's identity. | ||
| * On Build, Max, and Business plans, credits are consumed starting with any [cloud agent credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits) allocated to the user, then the user's plan-included credits, then the user's Reload credits. Reload credits are scoped to the individual user. |
Contributor
There was a problem hiding this comment.
🚨 [CRITICAL] This repeats the broken #cloud-agent-credits anchor; use the existing Compute credits anchor instead.
Suggested change
| * On Build, Max, and Business plans, credits are consumed starting with any [cloud agent credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits) allocated to the user, then the user's plan-included credits, then the user's Reload credits. Reload credits are scoped to the individual user. | |
| * On Build, Max, and Business plans, credits are consumed starting with any [cloud agent credits](/support-and-community/plans-and-billing/credits/#compute-credits) allocated to the user, then the user's plan-included credits, then the user's Reload credits. Reload credits are scoped to the individual user. |
Comment on lines
+68
to
+78
| :::caution | ||
| **Leaving a paid team forfeits access to Reload credits tied to it.** [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) are scoped to your individual user under your team. If you leave a paid team, you lose access to any remaining Reload credits attributed to you. If you rejoin the same team later, you regain access to any unused, non-expired credits. | ||
| ::: | ||
|
|
||
| :::caution | ||
| **Deleting a team removes all members' access to Reload credits.** If an admin deletes the team, every member loses access to any remaining [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) attributed to them under that team. | ||
| ::: | ||
|
|
||
| :::note | ||
| Reload credits require an active subscription. Downgrading to the Free plan also forfeits access to Reload credits. | ||
| ::: |
Contributor
There was a problem hiding this comment.
Suggested change
| :::caution | |
| **Leaving a paid team forfeits access to Reload credits tied to it.** [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) are scoped to your individual user under your team. If you leave a paid team, you lose access to any remaining Reload credits attributed to you. If you rejoin the same team later, you regain access to any unused, non-expired credits. | |
| ::: | |
| :::caution | |
| **Deleting a team removes all members' access to Reload credits.** If an admin deletes the team, every member loses access to any remaining [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) attributed to them under that team. | |
| ::: | |
| :::note | |
| Reload credits require an active subscription. Downgrading to the Free plan also forfeits access to Reload credits. | |
| ::: | |
| :::caution | |
| **Leaving a Build, Max, or Business team forfeits access to Reload credits tied to it.** [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) are scoped to your individual user under your team. If you leave one of these paid teams, you lose access to any remaining Reload credits attributed to you. If you rejoin the same team later, you regain access to any unused, non-expired credits. | |
| ::: | |
| :::caution | |
| **Deleting a Build, Max, or Business team removes all members' access to Reload credits.** If an admin deletes one of these teams, every member loses access to any remaining [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) attributed to them under that team. | |
| ::: | |
| :::note | |
| Reload credits require an active subscription. Downgrading to the Free plan also forfeits access to Reload credits. | |
| ::: |
hongyi-chen
added a commit
that referenced
this pull request
May 19, 2026
…dentities) Deferred from PR #112 (cross-page cleanup) because agents.mdx didn't exist on the umbrella branch at the time. Picked up after merging origin/main into the umbrella, which brought agents.mdx (added by PR #98 orchestration launch) into the tree. Adds a 'Billing for agent identity runs' subsection between 'Supporting multiple agent identities' and 'Plan limits' that mirrors the service-account billing waterfall on add-on-credits.mdx, credits.mdx, and team-access-billing-and-identity.mdx: - Self-serve (Build/Max/Business): bills the team owner. Waterfall is owner's plan-included credits, then owner's Reload credits, with auto-reload subject to the team-wide spend cap. - Enterprise: draws from the team-scoped credit pool with PAYG fallback when depleted, if enabled. Co-Authored-By: Oz <oz-agent@warp.dev>
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
1 participant
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.
This is the 5th sibling PR of the May 2026 pricing launch. Siblings:
This PR cleans up four cross-pages that were written under the old pooled Add-on Credits model and contained claims that will be incorrect once the May 14, 2026 changes ship. None of the per-plan monthly credit counts are hard-coded — readers are pointed at warp.dev/pricing and the new Reload credits / platform credits pages.
Files changed
src/content/docs/agent-platform/cloud-agents/team-access-billing-and-identity.mdx— Rewrote the integration credit waterfall, the user-triggered / team API key / scheduled / agent identity run bullets, and the "Staying aware of usage" summary. Added a Related resources section linking to Reload credits, platform credits, and the credits overview.src/content/docs/reference/cli/api-keys.mdx— Rewrote the Personal vs team API keys bullets so personal keys no longer claim to draw from team Add-on Credits, and team keys describe the team-owner waterfall (self-serve) and team-scoped pool (Enterprise).src/content/docs/knowledge-and-collaboration/teams.mdx— Added:::cautioncallouts to "Leaving and deleting teams" covering: leaving a paid team forfeits access to Reload credits (rejoining restores unused, non-expired ones), deleting a team removes everyone's access, and the active-subscription requirement.src/content/docs/enterprise/team-management/teams.mdx— Added an explicit "Reload credit consequences when leaving or removing members" subsection covering leaving, admin-removes-member, and admin-deletes-team scenarios, plus the active-subscription requirement.Model in one paragraph
On self-serve plans (Build, Max, Business), Reload credits are scoped to the individual user. User-triggered runs draw from the user's own pools (plan-included credits → user's Reload credits). Team API key, scheduled, and agent identity runs are billed to the team owner (owner's plan-included credits → owner's Reload credits), with auto-reload subject to a single team-wide monthly spend cap. On Enterprise plans, all runs draw from the team-scoped credit pool, with PAYG as a fallback if enabled in the contract. Leaving a paid team forfeits the leaving user's Reload credit access; rejoining restores any non-expired credits.
Follow-up
src/content/docs/agent-platform/cloud-agents/agents.mdx(the new Agent identities page) is deferred from this PR. That file landed onmainvia the orchestration-launch PR #98 and is not yet present on thehyc/plan-updatesumbrella (the umbrella is currently 14 commits behindmain). The orchestrator will rebase the umbrella ontomainafter the four siblings (#70/#71/#72/#73) and this PR land, and will pick up theagents.mdxbilling subsection then — either as part of the rebase commit or in a short follow-up PR.Conversation: https://staging.warp.dev/conversation/e425b99c-085f-4edc-8911-c277e14f196b
Run: https://oz.staging.warp.dev/runs/019e427e-b0e5-723d-8403-547bd920098e
This PR was generated with Oz.
Co-Authored-By: Oz oz-agent@warp.dev