Repository navigation
Conversation
skjnldsv
force-pushed
the
feature/weighted-score
branch
from
October 29, 2026 07:33
7878d19 to
f3fb3f2
Compare
skjnldsv
marked this pull request as ready for review
October 29, 2026 19:33
skjnldsv
force-pushed
the
feature/weighted-score
branch
from
October 29, 2026 20:13
bf9d02f to
f72dfaf
Compare
Assisted-by: ClaudeCode:claude-opus-5-5 Signed-off-by: John Molakvoæ <14975046+skjnldsv@users.noreply.github.com>
Sorting by date alone put whatever changed last on top. Each reason a file is recommended for now adds its weight, halved for every week it is old, so a file recommended for several reasons ranks higher. How often the user opened a file adds to it too, and a new "frequently opened" source brings in files opened often but not lately. The weights follow the RFC and can be tuned per instance with the app config keys weight_<reason>, e.g. weight_recently_opened. Assisted-by: ClaudeCode:claude-opus-5-5 Signed-off-by: John Molakvoæ <14975046+skjnldsv@users.noreply.github.com>
skjnldsv
force-pushed
the
feature/weighted-score
branch
from
October 29, 2026 20:16
f72dfaf to
5d5b995
Compare
Member
Author
|
Ah damn, I merged #1211 here. I thought I created the stack properly 🤦 EDIT/ adjusted |
The frequency part of the score never decayed, so a file opened 4 times weeks ago still ranked above a file shared today. It is now halved for every 30 days since the file was last opened, the time opens are kept. Assisted-by: ClaudeCode:claude-opus-5-5 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PzGjc7EoXAFppizM3nwWEz Signed-off-by: John Molakvoæ <14975046+skjnldsv@users.noreply.github.com>
Signed-off-by: John Molakvoæ <14975046+skjnldsv@users.noreply.github.com>
skjnldsv
force-pushed
the
feature/weighted-score
branch
from
October 29, 2026 20:24
5d5b995 to
8c84440
Compare
skjnldsv
enabled stacked auto-merge
October 29, 2026 21:59
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Recommendations were sorted by date only, so whatever changed last won. Now each reason adds its weight, halved for every week it's old, and how often you opened a file adds to it, fading over a month since you last opened it. A file recommended for several reasons ranks higher. A "frequently opened" source brings in files you open often but not lately.
Relates to #888. Stacked on #1208.
Weights follow the RFC: opened 0.3, frequently opened 0.2, favorite 0.2, edited, shared and commented 0.1. Any of them can be tuned per instance without a release, for example
occ config:app:set recommendations weight_favorite --value 0.3 --type float. These are a first guess, tuning them on real usage is the next step.👾 This pull request was assisted by Claude Code, commits carry an
Assisted-bytrailer.