[Resource]: tallyline

Open Beginner friendly
  • Is something wrong?
#3,229 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
65/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
content

Research direction

Read the resource entry format and nearby entries in the repository, then check the linked tallyline project to confirm the description and link. Add tallyline under the matching category, Observability & Monitoring > Usage & Cost, following the surrounding formatting. Done when the entry accurately summarizes the project and its link works.

Written by the indexing model from the issue text.

Description

resource-submission validation-passed
Display Name

tallyline

Category

Observability & Monitoring > Usage & Cost

Link

https://github.com/nhinata/tallyline

Author Name

nhinata

Author Link

https://github.com/nhinata

Description

A status line written in Python with only the standard library that shows context size, Pro/Max rate limits, and day/month/year token totals with API-equivalent cost across all sessions. tallyline diagnose breaks usage down by cause (cache rewrites after idle gaps, tool outputs kept in context, long context), and tallyline sessions lists open sessions with the cost of resuming each one after its cache expires.

Checklist
  • I have visited this repo before with my own eyes, and I have confirmed that this resource is sufficiently distinct from any existing resource
  • All links are working and publicly accessible
  • This resource is specific to Claude Code
  • I have read the CONTRIBUTING.md
  • I promise I actually did these things and not doing so is shameful and lazy
  • Do not check the following box - leave it unchecked. By checking this box, I admit that I am not reading any of these statements.
Dominant language
Python
Stars
55.2k
Forks
4.8k
Avg merge
46m
Merged PRs (30d)
56

Getting set up

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 hesreallyhim/awesome-claude-code

All issues in hesreallyhim/awesome-claude-code

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.