Add Star-us prompts across TUI, CLI, and README - #51
Merged
Conversation
Three new hooks for community growth: 1. `support.py` helper prints a subtle "If ClawBench helped, please star us" line. Used from `run.py` on successful completion and from `batch.py` after the summary. Honors `CLAWBENCH_NO_STAR=1` and skips when stdout isn't a TTY (CI, pipes). 2. TUI gets a "Star us on GitHub" entry in the main menu that opens the repo page in the default browser; on exit we print the same rich prompt so users leave with the link visible. 3. README (both EN and zh-CN) gets a "Support ClawBench" section with a big shields.io star button, contrib.rocks contributors wall, and a link to CONTRIBUTING.md. Sits right above the Star History chart so the growth narrative is self-reinforcing.
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
1 participant
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.
Summary
Community-growth hooks at the three touchpoints users actually end their sessions on:
run.py/batch.pyprint a one-line star prompt after completion. Opt-out viaCLAWBENCH_NO_STAR=1or non-TTY stdout (CI, pipes)Why
Benchmark repos live or die by community reach. A gentle ask at the moment a user has just seen their run complete is the highest-converting star moment we'll ever get — peer repos (AnythingLLM, crawl4ai, MetaGPT) all use variants of this pattern.
Test plan
clawbench run <case> <model>— star line appears after "INTERCEPTED — results in ..."clawbench batch ...— star line appears after summaryCLAWBENCH_NO_STAR=1 clawbench run ...— star line suppressedclawbench tuishows "Star us on GitHub" between "Change theme" and "Exit"; selecting it opens the repo page