llm logs --count should return a count of matching logs
Open
Beginner friendly
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 12.5k
- Forks
- 998
- Avg merge
- 6d 12h
- Merged PRs (30d)
- 15
Description
This is technically a breaking change because -n has the longer form --count and is used to set the number of results to return.
I'm pre-1.0 so I'm going to break it!
It's really useful to be able to get a quick count for how many results are matching. For example:
llm logs --tools --count
Contributor guide
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.
Research direction
Start at the llm logs command entry point and inspect how -n and --count are currently parsed and applied. Run llm logs --tools --count before and after the change; done means --count reports the number of matching logs without returning the log entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100