docs: clarify team credit spend order and dedupe Factories changelog - #683
Open
dannyneira wants to merge 3 commits into
Open
docs: clarify team credit spend order and dedupe Factories changelog#683dannyneira wants to merge 3 commits into
dannyneira wants to merge 3 commits into
Conversation
Document that plan-included credits drain before shared team grants, then user-scoped grants, with no personal-first option on a team. Remove duplicate Warp Factories Early Access bullets from 2026.08.18, 2026.08.19, and 2026.08.25. Co-Authored-By: Warp <agent@warp.dev>
…er-and-factories-changelog-cleanup
Co-Authored-By: Warp <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 |
![warp-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 clarifies the credit spend order across billing docs and removes duplicated Warp Factories changelog bullets. I found one non-blocking consistency issue in the troubleshooting page wording; no security or spec concerns apply to these docs-only changes.
Concerns
- The insufficient credits page narrows the shared grant step to add-on grants, while the other edited pages use the broader shared team grants language.
Verdict
Found: 0 critical, 0 important, 1 suggestions
Approve with nits
Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
| On self-serve plans (Build, Max, Business), the billed principal depends on how the run was triggered: | ||
|
|
||
| * **User-triggered runs** draw from the triggering user's plan-included credits first, then the team's shared add-on credit pool. | ||
| * **User-triggered runs** draw from the triggering user's plan-included credits first, then shared team add-on grants, then any remaining user-scoped grants that apply on the active team. There is no option to spend personal credits first while on a team. |
Contributor
There was a problem hiding this comment.
💡 [SUGGESTION] Use the same broader "shared team grants" language here so this page also covers shared bonus grants.
Suggested change
| * **User-triggered runs** draw from the triggering user's plan-included credits first, then shared team add-on grants, then any remaining user-scoped grants that apply on the active team. There is no option to spend personal credits first while on a team. | |
| * **User-triggered runs** draw from the triggering user's plan-included credits first, then shared team grants, then any remaining user-scoped grants that apply on the active team. There is no option to spend personal credits first while on a team. |
rachaelrenk
reviewed
Sep 3, 2026
| 2. Shared bonus or add-on grants available to the active team (team-wide pool first). | ||
| 3. Any remaining user-scoped bonus grants that apply on that team. | ||
| Leftover personal add-on balances from May–August 2026 are one example. | ||
| These are used only after shared grants are exhausted. |
Contributor
There was a problem hiding this comment.
fix for two orphaned lines
Suggested change
| These are used only after shared grants are exhausted. | |
| * On Build, Max, and Business plans, Warp consumes credits in a fixed order. You cannot prioritize user-scoped grants ahead of shared team grants: | |
| 1. The triggering user's monthly credits included with their plan. | |
| 2. Shared bonus or add-on grants available to the active team (team-wide pool first). | |
| 3. The triggering user's remaining user-scoped bonus or add-on grants that apply to the active team. This includes any remaining add-on credit balance purchased between May and August 2026. Warp uses these grants only after shared team grants are exhausted. |
rachaelrenk
approved these changes
Sep 3, 2026
rachaelrenk
reviewed
Sep 3, 2026
Comment on lines
+82
to
+84
| On a team, that add-on step is also fixed: shared team grants drain before any | ||
| remaining user-scoped grants. You cannot choose to spend personal credits first | ||
| while on a team. |
Contributor
There was a problem hiding this comment.
Suggested change
| On a team, that add-on step is also fixed: shared team grants drain before any | |
| remaining user-scoped grants. You cannot choose to spend personal credits first | |
| while on a team. | |
| On a team, that add-on step is also fixed: shared team grants drain before any remaining user-scoped grants. You cannot choose to spend personal credits first while on a team. |
rachaelrenk
reviewed
Sep 3, 2026
Comment on lines
+158
to
+160
| * **No personal-first option** — While you are on a team, you cannot spend | ||
| personal or user-scoped credits before the team's shared grants. | ||
| Team-first drawdown is intentional. |
Contributor
There was a problem hiding this comment.
Suggested change
| * **No personal-first option** — While you are on a team, you cannot spend | |
| personal or user-scoped credits before the team's shared grants. | |
| Team-first drawdown is intentional. | |
| * **No personal-first option** — While you are on a team, you cannot spend personal or user-scoped credits before the team's shared grants. Team-first drawdown is intentional. |
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.
Summary
Clarifies how Warp drains credits on multi-seat teams and removes repeated Warp Factories Early Access bullets from three August changelog entries.
Changes
Credit spend order
platform/team-access-billing-and-identity.mdx— fixed the user-triggered waterfall to plan-included → shared team grants → user-scoped grants; stated there is no personal-first optionplans-and-billing/pricing-faqs.mdx— same order and no personal-first callout for multi-seat teams and the May 2026 attribution FAQplans-and-billing/add-on-credits.mdx— team add-on step drains shared grants before leftover user-scoped balanceserrors/insufficient-credits.mdx— matched the same user-triggered orderChangelog cleanup
changelog/2026.mdx— removed duplicate Warp Factories Early Access new-feature bullets from 2026.08.18, 2026.08.19, and 2026.08.25 (kept the 2026.08.27 announcement and the 2026.08.18 Factory MCP bullet)Unverified claims
None — credit order verified against
ConsumeGrantCreditsForUser/ base-limit-before-bonus grant consumption in warp-server.Co-Authored-By: Warp agent@warp.dev