feat(ai): Show context window usage as absolute tokens Closes by sikongyue · Pull Request #14628 · warpdotdev/warp

sikongyue · 2026-08-01T16:48:17Z

Display absolute token counts alongside percentages in AI Agent context window usage UI, so users can judge when to compact or hand off based on actual token counts rather than relative percentages.

Add context_window_tokens and context_window_limit fields to ConversationUsageInfo
Add context_window_tokens() method in conversation.rs, computed by summing segment token counts
Pass context window token data through terminal/view.rs
Update conversation_usage_view.rs display format:
- With limit: "112k / 1M (41%)"
- Without limit: "112k (41%)"
- Fallback: "41%" (when no segment data available)
Update agent input footer tooltip: "41% context remaining (112k / 1M)"
Fix struct initialization in gql_convert.rs and test files

Closes #14629: Show context window usage as absolute tokens

Description

Linked Issue

The linked issue is labeled ready-to-spec or ready-to-implement.
Where appropriate, screenshots or a short video of the implementation are included below (especially for user-visible or UI changes).

Testing

I have manually tested my changes locally with ./script/run

Screenshots / Videos

Agent Mode

Warp Agent Mode - This PR was created via Warp's AI Agent Mode

cla-bot · 2026-08-01T16:48:20Z

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: sikongyue.
This is most likely caused by a git client misconfiguration; please make sure to:

check if your git client is configured with an email to sign commits git config --list | grep email
If not, set it up using git config --global user.email email@example.com
Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

oz-for-oss · 2026-08-01T16:48:24Z

@sikongyue

Every PR must be linked to a same-repo issue before Oz can review it.

This PR is linked to #14629, but no linked issue is marked ready-to-implement yet. Only repository maintainers apply that label, so please wait for a maintainer to mark the issue. Once it is marked, push a new commit or comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

oz-for-oss

@sikongyue

Every PR must be linked to a same-repo issue before Oz can review it.

Next step: open or find a same-repo issue describing this change, then link it to this PR by adding Closes #123 to the PR description (or using the "Development" sidebar on GitHub). A maintainer will mark the issue ready-to-implement when it is ready. Once it is marked, comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

cla-bot · 2026-08-01T16:57:06Z

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: sikongyue.
This is most likely caused by a git client misconfiguration; please make sure to:

check if your git client is configured with an email to sign commits git config --list | grep email
If not, set it up using git config --global user.email email@example.com
Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

sikongyue · 2026-08-01T17:15:37Z

/oz-review

oz-for-oss

@sikongyue

Every PR must be linked to a same-repo issue before Oz can review it.

Next step: open or find a same-repo issue describing this change, then link it to this PR by adding Closes #123 to the PR description (or using the "Development" sidebar on GitHub). A maintainer will mark the issue ready-to-implement when it is ready. Once it is marked, comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

sikongyue · 2026-08-01T17:20:28Z

/oz-review

oz-for-oss

@sikongyue

Every PR must be linked to a same-repo issue before Oz can review it.

This PR is linked to #14629, but no linked issue is marked ready-to-implement yet. Only repository maintainers apply that label, so please wait for a maintainer to mark the issue. Once it is marked, push a new commit or comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

sikongyue · 2026-08-01T17:22:03Z

/oz-review

oz-for-oss

@sikongyue

Every PR must be linked to a same-repo issue before Oz can review it.

This PR is linked to #14629, but no linked issue is marked ready-to-implement yet. Only repository maintainers apply that label, so please wait for a maintainer to mark the issue. Once it is marked, push a new commit or comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

sikongyue · 2026-08-01T17:24:04Z

/oz-review

oz-for-oss

@sikongyue

Every PR must be linked to a same-repo issue before Oz can review it.

This PR is linked to #14629, but no linked issue is marked ready-to-implement yet. Only repository maintainers apply that label, so please wait for a maintainer to mark the issue. Once it is marked, push a new commit or comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

sikongyue · 2026-08-01T17:26:07Z

/oz-review

oz-for-oss

@sikongyue

Every PR must be linked to a same-repo issue before Oz can review it.

Next step: open or find a same-repo issue describing this change, then link it to this PR by adding Closes #123 to the PR description (or using the "Development" sidebar on GitHub). A maintainer will mark the issue ready-to-implement when it is ready. Once it is marked, comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

sikongyue · 2026-08-01T17:26:53Z

/oz-review

oz-for-oss

@sikongyue

Every PR must be linked to a same-repo issue before Oz can review it.

Next step: open or find a same-repo issue describing this change, then link it to this PR by adding Closes #123 to the PR description (or using the "Development" sidebar on GitHub). A maintainer will mark the issue ready-to-implement when it is ready. Once it is marked, comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

sikongyue · 2026-08-01T17:31:34Z

/oz-review

oz-for-oss

@sikongyue

Every PR must be linked to a same-repo issue before Oz can review it.

This PR is linked to #14629, but no linked issue is marked ready-to-implement yet. Only repository maintainers apply that label, so please wait for a maintainer to mark the issue. Once it is marked, push a new commit or comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

sikongyue · 2026-08-01T17:43:45Z

/oz-review

oz-for-oss

@sikongyue

Every PR must be linked to a same-repo issue before Oz can review it.

This PR is linked to #14629, but no linked issue is marked ready-to-implement yet. Only repository maintainers apply that label, so please wait for a maintainer to mark the issue. Once it is marked, push a new commit or comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

Display absolute token counts alongside percentages in AI Agent context window usage UI, so users can judge when to compact or hand off based on actual token counts rather than relative percentages. - Add context_window_tokens and context_window_limit fields to ConversationUsageInfo - Add context_window_tokens() method in conversation.rs, computed by summing segment token counts - Pass context window token data through terminal/view.rs - Update conversation_usage_view.rs display format: - With limit: "112k / 1M (41%)" - Without limit: "112k (41%)" - Fallback: "41%" (when no segment data available) - Update agent input footer tooltip: "41% context remaining (112k / 1M)" - Fix struct initialization in gql_convert.rs and test files Closes issue: Show context window usage as absolute tokens

cla-bot · 2026-08-01T17:48:01Z

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: sikongyue.
This is most likely caused by a git client misconfiguration; please make sure to:

check if your git client is configured with an email to sign commits git config --list | grep email
If not, set it up using git config --global user.email email@example.com
Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

sikongyue · 2026-08-01T17:51:41Z

/oz-for-oss

sikongyue · 2026-08-01T17:52:25Z

/oz-review

oz-for-oss

@sikongyue

Every PR must be linked to a same-repo issue before Oz can review it.

This PR is linked to #14629, but no linked issue is marked ready-to-implement yet. Only repository maintainers apply that label, so please wait for a maintainer to mark the issue. Once it is marked, push a new commit or comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

sikongyue · 2026-08-02T03:53:40Z

/oz-review

oz-for-oss

@sikongyue

Every PR must be linked to a same-repo issue before Oz can review it.

This PR is linked to #14629, but no linked issue is marked ready-to-implement yet. Only repository maintainers apply that label, so please wait for a maintainer to mark the issue. Once it is marked, push a new commit or comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

github-actions Bot added the external-contributor Indicates that a PR has been opened by someone outside the Warp team. label Aug 1, 2026

oz-for-oss Bot requested changes Aug 1, 2026

View reviewed changes

sikongyue force-pushed the feat/context-window-absolute-tokens branch from 716b9bd to 25a36e6 Compare August 1, 2026 16:57

oz-for-oss Bot requested changes Aug 1, 2026

View reviewed changes

sikongyue changed the title ~~feat(ai): Show context window usage as absolute tokens (e.g. 112k / 1M)~~ feat(ai): Show context window usage as absolute tokens Aug 1, 2026

oz-for-oss Bot requested changes Aug 1, 2026

View reviewed changes

sikongyue force-pushed the feat/context-window-absolute-tokens branch from 25a36e6 to 1d6df7f Compare August 1, 2026 17:47

oz-for-oss Bot requested changes Aug 1, 2026

View reviewed changes

sikongyue changed the title ~~feat(ai): Show context window usage as absolute tokens~~ feat(ai): Show context window usage as absolute tokens Closes #14629 Aug 1, 2026

sikongyue changed the title ~~feat(ai): Show context window usage as absolute tokens Closes #14629~~ feat(ai): Show context window usage as absolute tokens Closes Aug 1, 2026

oz-for-oss Bot requested changes Aug 2, 2026

View reviewed changes

Uh oh!

Conversation

sikongyue commented Aug 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Linked Issue

Testing

Screenshots / Videos

Agent Mode

Uh oh!

cla-bot Bot commented Aug 1, 2026

Uh oh!

oz-for-oss Bot commented Aug 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

oz-for-oss Bot left a comment

Choose a reason for hiding this comment

Uh oh!

cla-bot Bot commented Aug 1, 2026

Uh oh!

sikongyue commented Aug 1, 2026

Uh oh!

oz-for-oss Bot left a comment

Choose a reason for hiding this comment

Uh oh!

sikongyue commented Aug 1, 2026

Uh oh!

oz-for-oss Bot left a comment

Choose a reason for hiding this comment

Uh oh!

sikongyue commented Aug 1, 2026

Uh oh!

oz-for-oss Bot left a comment

Choose a reason for hiding this comment

Uh oh!

sikongyue commented Aug 1, 2026

Uh oh!

oz-for-oss Bot left a comment

Choose a reason for hiding this comment

Uh oh!

sikongyue commented Aug 1, 2026

Uh oh!

oz-for-oss Bot left a comment

Choose a reason for hiding this comment

Uh oh!

sikongyue commented Aug 1, 2026

Uh oh!

oz-for-oss Bot left a comment

Choose a reason for hiding this comment

Uh oh!

sikongyue commented Aug 1, 2026

Uh oh!

oz-for-oss Bot left a comment

Choose a reason for hiding this comment

Uh oh!

sikongyue commented Aug 1, 2026

Uh oh!

oz-for-oss Bot left a comment

Choose a reason for hiding this comment

Uh oh!

cla-bot Bot commented Aug 1, 2026

Uh oh!

sikongyue commented Aug 1, 2026

Uh oh!

sikongyue commented Aug 1, 2026

Uh oh!

oz-for-oss Bot left a comment

Choose a reason for hiding this comment

Uh oh!

sikongyue commented Aug 2, 2026

Uh oh!

oz-for-oss Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

sikongyue commented Aug 1, 2026 •

edited

Loading

oz-for-oss Bot commented Aug 1, 2026 •

edited

Loading