d37e7a8ccf
## Description Resolves a UI bug Jeff flagged: the "Usage" rows on the Billing & Usage v2 page showed credits as `total_credits / base_limit` for individual user rows, with the numerator summing every cost type (base + add-on + payg + cloud-only) while the denominator was base-only. After certain plan transitions add-on credits get spent before the base limit is exhausted, so the ratio looks alarming even though plenty of base credits remain (e.g. `7,559 / 18,000` when only ~3.4K of those credits were actually drawn from the base limit). Two changes to decouple the "base credits remaining" story from "total credits this row consumed": 1. The **Base credits** balance card now shows the cycle's base limit alongside the remaining count — `14,624 remaining (of 18,000)`. This is the authoritative base-only figure because the underlying `request_limit_info` comes from `GetCurrentUsageForBaseLimits` on the server (which is explicitly base-only and clamped to the limit). Personal/Team grant cards keep their existing "remaining" sub-label since they don't have a fixed denominator. 2. The per-row credit cluster drops the `/limit` suffix and just shows the total credits used by that row. The stacked bar above the row + the hover breakdown tooltip still surface the base / add-on / payg split, which is the cleaner place to convey that information. Why not just compute "base credits used" for the numerator? For the TeamAggregate visibility tier (the typical Build Business setup), `collapseToTeamAggregate` on the server rolls every non-caller entry into a single `Aggregate`-cost-type entry, so the "Other members" row can't be reliably split into base vs. non-base. Also drops `MemberUsageRow.base_limit` and helpers (`member_base_limit`, `viewer_base_limit`) that are no longer read, plus the now-unused `workspace` argument to `render_own_usage_with_workspace_row` (per the WARP.md "remove unused parameters completely" guideline). ## Testing Note: no denom in usage rows anymore, but we do have the `/ 60` in the top left box now <img width="881" height="565" alt="image" src="https://github.com/user-attachments/assets/f0c58643-e23b-479a-9739-a3a4521b6f7c" /> --------- Co-authored-by: Oz <oz-agent@warp.dev>
Website · Code · Agents · Terminal · Drive · Docs · How Warp Works
Note
OpenAI is the founding sponsor of the new, open-source Warp repository, and the new agentic management workflows are powered by GPT models.
About
Warp is an agentic development environment, born out of the terminal. Use Warp's built-in coding agent, or bring your own CLI agent (Claude Code, Codex, Gemini CLI, and others).
Installation
You can download Warp and read our docs for platform-specific instructions.
Warp Contributions Overview Dashboard
Explore build.warp.dev to:
- Watch thousands of Oz agents triage issues, write specs, implement changes, and review PRs
- View top contributors and in-flight features
- Track your own issues with GitHub sign-in
- Click into active agent sessions in a web-compiled Warp terminal
Oz for OSS
Maintaining a popular open-source project? Apply for Oz credits to explore Oz for OSS.
Oz for OSS is our partner program for bringing the same agentic open-source management workflows used in this repository to select partner repositories. We work directly with maintainers to implement workflows for issue triage, PR review, community management, and contributor coordination in a way that fits each project.
Licensing
Warp's UI framework (the warpui_core and warpui crates) are licensed under the MIT license.
The rest of the code in this repository is licensed under the AGPL v3.
Open Source & Contributing
Warp's client codebase is open source and lives in this repository. We welcome community contributions and have designed a lightweight workflow to help new contributors get started. For the full contribution flow, read our CONTRIBUTING.md guide.
Tip
Chat with contributors and the Warp team in the
#oss-contributorsSlack channel — a good place for ad-hoc questions, design discussion, and pairing with maintainers. New here? Join the Warp Slack community first, then jump into#oss-contributors.
Issue to PR
Before filing, search existing issues for your bug or feature request. If nothing exists, file an issue using our templates. Security vulnerabilities should be reported privately as described in CONTRIBUTING.md.
Once filed, a Warp maintainer reviews the issue and may apply a readiness label: ready-to-spec signals the design is open for contributors to spec out, and ready-to-implement signals the design is settled and code PRs are welcome. Anyone can pick up a labeled issue — mention @oss-maintainers on an issue if you'd like it considered for a readiness label.
Building the Repo Locally
To build and run Warp from source:
./script/bootstrap # platform-specific setup
./script/run # build and run Warp
./script/presubmit # fmt, clippy, and tests
See WARP.md for the full engineering guide, including coding style, testing, and platform-specific notes.
Joining the Team
Interested in joining the team? See our open roles.
Support and Questions
- See our docs for a comprehensive guide to Warp's features.
- Join our Slack Community to connect with other users and get help from the Warp team — contributors hang out in
#oss-contributors. - Try our Preview build to test the latest experimental features.
- Mention @oss-maintainers on any issue to escalate to the team — for example, if you encounter problems with the automated agents.
Code of Conduct
We ask everyone to be respectful and empathetic. Warp follows the Code of Conduct. To report violations, email warp-coc at warp.dev.
Open Source Dependencies
We'd like to call out a few of the open source dependencies that have helped Warp to get off the ground: