Deficit/Reserve calculation

Open
#3,079 9 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
swift
Domain
analytics

Research direction

No files, tests, or entry points are named. Start by locating the current deficit/reserve calculation and how reset-period measurements are stored, then assess whether a rolling window using prior-week data can be specified and tested as complete.

Written by the indexing model from the issue text.

Description

clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr impact:ux-friction issue-rating: 🌊 off-meta tidepool P3

I have noted that just after the weekly reset (Claude), I tend to drop relatively quickly into a deficit, however it levels up after a few days in general.

This reminds me of the time estimate for copying files in older Windows OS: at the beginning small fluctuations make the estimate vary a lot, and the more progress is made, the more precise the estimate becomes, and of course toward the end it is no longer really an estimate, i.e. if 99% of the time has passed, the estimate remaining time is bang on.

I feel the same is happening with CodexBar, now it could be that I change my behavior because of CodexBar (which might be at least partially correct) or that the estimate is based on a too short baseline to be a robust estimate. I cannot say which is which.

In the event my assumption around a too short baseline is right, have you tried to use the previous week as an estimator helper, basically calculating the deficit/reserve on a rolling window until the current time and projecting the rate of usage until the end of the reset period? This would require to store some data from reset to reset, but I don't think that a lot of measures are necessary to improve the estimate.

I would love to look into it, but I am swamped unfortunately.

Dominant language
Swift
Stars
21.6k
Forks
2k
Avg merge
1d 9h
Merged PRs (30d)
385

Contributor guide

No contributing guide indexed for this repository

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 steipete/CodexBar

All issues in steipete/CodexBar

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.