Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Lens] Add a "Prove this holds" link on the Optimize screen's downsize candidates

Open Beginner friendly
  • Is something wrong?
#331 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
html
Domain
frontend

Research direction

Start in tokenjam/ui/index.html and read how the Optimize screen renders downsize candidates. Add the link only alongside those candidates, and show a copyable tjb run --original … --candidate … command where a specific candidate is available. Done when the link points to tokenjam-bench, the wording makes no safety or certification claim, and no render-time fetch is added.

Written by the indexing model from the issue text.

Description

enhancement good first issue help wanted

The Lens Optimize screen lists downsize candidates but offers no next step for the obvious question: will the cheaper model hold up? The companion tokenjam-bench measures exactly that.

What to do

On the Optimize screen in tokenjam/ui/index.html, add a small "Prove this holds →" affordance near the downsize candidates that links to the tokenjam-bench repo (and, where a specific candidate is shown, surfaces the matching tjb run --original … --candidate … command to copy).

Acceptance criteria
  • Link/affordance appears with downsize candidates only.
  • Offline-first preserved — an <a href> to github.com is fine (clickable links are allowed; no render-time fetch). See Critical Rule 18.
  • Copy honest: "prove this holds", never "safe"/"certified".
📦 Before you start — install and learn tokenjam-bench

This issue cross-links to tokenjam-bench, so please get hands-on with it first. The copy you add should come from actually understanding the tool, not a guess:

  1. Install it: pip install tokenjam-bench
  2. Run a proof to see what it produces: tjb run (offline, zero-flag), then explore tjb --help and tjb serve (the live proof dashboard).
  3. Read its README so you understand what it measures — pass-rate on a task suite with Wilson CI + McNemar, a hedged verdict like "HOLDS / REGRESSED" — and what it deliberately does not claim (never "certified", never "quality preserved").

Your wording in this change should match that honest framing before you open the PR.

Dominant language
Python
Stars
122
Forks
35
Avg merge
1d 18h
Merged PRs (30d)
8

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 Metabuilder-Labs/tokenjam

All issues in Metabuilder-Labs/tokenjam

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.