Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FrontEnd] Display API cost and token usage in frontend #7099

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

AutoLTX
Copy link

@AutoLTX AutoLTX commented Mar 4, 2025

  • This change is worth documenting at https://docs.all-hands.dev/
  • Include this change in the Release Notes. If checked, you must provide an end-user friendly description for your change below

End-user friendly description of the problem this fixes or functionality that this introduces.


Give a summary of what the PR does, explaining any non-trivial design decisions.
This will expose API cost and usage info to customers in on-demand mode.

  • Expose cost and usage info in default mode.
  • User can click the hide cost button and hide the Cost and Usage. Then chat will show as original and cover all left channel.
    Some screenshots:
    Expose mode in default:
image image Hide mode: image

Link of any specific issues this addresses.
#5257

@AutoLTX
Copy link
Author

AutoLTX commented Mar 4, 2025

This PR needs to wait for backend PR #7082 merge first. And I may still change some details of the PR. But the inital design is finished. Let's make sure it can meet your requirement first!

Tagging reviewers for best design discussion: @neubig, @rbren, @enyst, @amanape. All the screenshots
are already uploaded in the PR description.

Now I use tilin/testFrontendE2E branch to test and get the screenshots. Feel free to try it if you need it.

@enyst enyst changed the title [FrontEnd][Waiting for backend PR merged, open for best design discussion in parallel] Display API cost and token usage in frontend [FrontEnd] Display API cost and token usage in frontend Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant