[Feat] show credit usage in chat responses and session popover

Open
#345 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
java
Domain
developer-experience

Research direction

Start by locating the Eclipse plugin's chat response rendering and session information popover, then trace how credit consumption and context-window usage are available to the UI. Done means a response hover shows per-turn credit usage and the session popover shows total credits and cumulative context tokens, with behavior comparable to the linked VS Code guidance.

Written by the indexing model from the issue text.

Description

enhancement

Is your feature request related to a problem? Please describe.
I can't see how many credits I've been using.

Describe the solution you'd like
I expect the credit usage to be shown similar to Copilot for VS Code:
https://code.visualstudio.com/docs/agents/guides/optimize-usage#_monitor-your-usage

In particular:

To view the cost for a single request, hover over the chat response to see the credit consumption for that turn.

and

The session info popover shows the total cost in credits and the cumulative context window token usage for the whole session

Describe alternatives you've considered
I have to run my prompt in VS Code if I want to see how many credits are being consumed by that prompt.

Additional context
Organizations on GitHub may configure a monthly credit limit. When that limit is reached then we start asking ourselves how we can watch how many credits each of us are consuming. Not being able to see the credit usage is problematic for developers using the Eclipse plugin.

Dominant language
Java
Stars
126
Forks
60
Avg merge
2d 6h
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/copilot-for-eclipse

All issues in microsoft/copilot-for-eclipse

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.