Add the consumption of tokens and remaining tokens
Maintainers usually reply within 1 day
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
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start by locating the UI that displays CPU and RAM usage and tracing how it receives live provider data. The issue asks to show token consumption and remaining tokens before each provider's plan reset, including multiple providers; the payload names no files or tests. Confirm which providers expose this data and how reset windows are represented before estimating the implementation; done means users can see those values alongside CPU and RAM.
Written by the indexing model from the issue text.
Description
Just an idea, but it would be great for the people who use plans per window of time, like Codex or Claude Max plan, to see how many tokens there is before the reset. If there are multiple providers used, show them all.
It could go next to the one where we see the CPU & RAM usage
WDYT ?
- Dominant language
- TypeScript
- Stars
- 36
- Forks
- 11
- Avg merge
- 4h 8m
- Merged PRs (30d)
- 161
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AgentSystemLabs/agent-office
-
Worker-Erstellung bricht langsame Git-Worktree-Checkouts nach 20 Sekunden abPossibly taken @KajoVanBuyten claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
AgentSystemLabs/agent-office#367 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
AgentSystemLabs/agent-office#297 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
AgentSystemLabs/agent-office#319 ·
Maintainers usually reply within 1 day
-
Not a cat option???Open
Difficulty 3/5 Half a day Newbie friendliness 45/100
AgentSystemLabs/agent-office#314 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 42/100
AgentSystemLabs/agent-office#309 ·
Maintainers usually reply within 1 day
All issues in AgentSystemLabs/agent-office
Similar issues
-
affected/v17 affected/v18 area/frontend type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
umbraco/Umbraco-CMS#24186 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
better-auth/better-auth#11723 · 1 reaction ·
Maintainers usually reply within 1 day
-
area: docs difficulty: easy documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
automation missing-model model-sync provider:aimlapi
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
anomalyco/models.dev#9734 ·
Maintainers usually reply within 1 day