아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
최근 완료된 8시간 회차 사이 GitHub 스타 증가량 순
FactCircuit는 불변 출처와 단계별 검증, 제한된 검색, 재현 가능한 평가를 제공하는 감사 가능한 주장·증거 검증 루프입니다
AI 에이전트를 위한 경량 Postgres, Rust로 구현, 하나의 런타임에서 수천 개의 격리된 데이터베이스 제공
그래프 엔진으로 컨텍스트를 조립하고, 객체 저장소 기반에서 에이전트가 코드처럼 그래프 데이터를 분기·타입·검토·병합·감사·거버넌스합니다
SeekStorm – 러스트 기반 벡터·전체 텍스트 검색, 임베드 라이브러리·자체 서버·클라우드 서비스 중 선택 가능
대규모 언어 모델을 위한 확장 가능한 데이터 전처리·정제 툴킷
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기🌐 Where Claude Code Developers Gather - Real-time global leaderboard for CC usage tracking
저장소 README에서 가져옴
README 전체를 불러오는 중입니다.
README 전문 보기 ↗Global Leaderboard | Community | Levels & Badges | PWA App
Website · Report Bug · Request Feature
📎 hero.gif
Claude Code only keeps usage history for 30 days — then your work disappears. The leaderboard service I was using stopped working one day, and no fix came. So I decided: "I'll just build it myself."
Token usage is NOT a measure of skill. More tokens mean more attempts, more experiments, more exploration. This number represents your spirit of exploration and passion.
"One tool, one community, no borders."
Developers worldwide use the same tools, but struggle to communicate due to different languages. The community feature breaks down these barriers with AI-powered automatic translation.
This is just the beginning. CCgather will evolve into a platform where Claude Code developers can showcase projects, share knowledge, and find collaborators—regardless of nationality.
I'm a non-developer from South Korea. I started vibe coding in August 2025 with Cursor and Lovable, then discovered Claude Code. For months, I spent 16+ hours daily—not using automation tools, but engaging in every conversation, asking Claude to explain concepts at a 15-year-old's level so I could truly understand. I still can't read code on my own, but I've worked hard to understand how the pieces connect.
CCgather was built in about 3 weeks.
On February 2, 2026, I launched CCgather on Product Hunt with zero marketing budget. It earned 116 upvotes and 106 followers on launch day alone — the community responded to the story of a non-developer building a full-featured platform through vibe coding and solving a real pain point.
Developers spend hours staring at gray text on dark backgrounds—I wanted to give them something worth looking at. I aimed for an MVP, but ended up trying many features for the sake of learning—and went through 2 major refactoring overhauls along the way. Countless trade-offs were made between the 3D globe, animations, visual polish, and rendering performance.
I tried to bring every UX detail I imagined to life.
| Feature | CCgather | Others |
|---|---|---|
| Active Maintenance | Daily updates, open-source | Varies |
| Open Source | Apache 2.0 | Limited or closed |
| Community | AI-translated multilingual | Basic or none |
| Country Leagues | Yes | No |
| Level System | 10-tier (Rookie → Immortal) | No |
| Badges | 27 badges, 4 tiers | No |
| 3D Globe Visualization | Yes | No |
| Activity Heatmap | GitHub-style | No |
| PWA & Push Notifications | Yes | No |
| Product Hunt | 116 upvotes on day one, zero marketing | — |
See your passion among developers worldwide. Track your ranking by token usage and compete in country-based leagues that give you a sense of belonging.
📎 leaderboard.gif
Visualize developer activity worldwide in real-time. See at a glance which countries are actively coding.
Write in your native language. Posts are automatically translated by AI and displayed in the reader's language. Share posts, comments, and celebrate top contributors in the Hall of Fame.
📎 community.gif
10-tier level system based on token usage
27 badges · 4 tiers
Categories:
npx ccgather
📎 cli.gif
npx ccgather@latest submit
Submits your usage without any prompt, so it can run from a scheduler. Log in once with npx ccgather first; submit never opens the login flow. It prints one timestamped result line and exits with:
Claude Code keeps about 30 days of local data, so once a day is plenty. Auto-submit (npx ccgather@latest autosubmit on) sets that up for you. To schedule it yourself instead:
# cron (macOS/Linux), every day at 21:17 — Node must be on cron's PATH
17 21 * * * npx --yes ccgather@latest submit >> ~/ccgather.log 2>&1
# Windows Task Scheduler (run in Command Prompt), every day at 21:17; a console window shows while it runs
schtasks /create /tn "CCgather submit" /sc daily /st 21:17 /tr "cmd /c npx --yes ccgather@latest submit >> \"%USERPROFILE%\ccgather.log\" 2>&1"
Pick a minute of your own rather than copying 21:17: everyone who keeps the example would reach the server in the same second. Task Scheduler skips a run on battery power by default, and both schedulers skip a run while the machine is asleep or off, so pick a time the machine is usually awake and plugged in.
A scheduler does not see the API key or cloud-provider variables your shell profile sets, so a submit it runs reports the Claude Code sign-in it can see (your claude.ai login, say), and your plan badge can switch between that and what a terminal submit reports. Auto-submit avoids this: its runs send no plan, so the badge follows your own submits.
Let the CLI set up the daily job for you, using your operating system's own scheduler:
npx ccgather@latest autosubmit on # turn it on, or update/repair it
npx ccgather@latest autosubmit status # what the scheduler has, and what the last run did
npx ccgather@latest autosubmit off # remove it
npx ccgather@latest autosubmit on --at 21:30 # pick the time yourself
Without --at it runs every day at the time you turned it on plus five minutes (turn it on at 14:17 and it runs at 14:22), in your local time. People turn it on at different moments, so not everyone submits at once, and your machine is usually awake at that time. The main menu has the same thing as its second item, right under Submit usage data: 🔁 Auto-submit: OFF turns it on, and Auto-submit: ON · daily 14:23 offers Change time, Turn off and Back. If the machine was off at that time, the job catches up later (except with the Linux cron fallback, which skips that day); a run is skipped if you submitted in the 20 hours before it, so the first one may be. Running on again when it is already on refreshes the job and keeps its time. status shows what the scheduler has and what the last run did:
Auto-submit: ON
Schedule: daily at 14:23 (systemd user timer)
Runs: the newest ccgather release each day, via npx
Last run: 2026-10-12 14:23 · skipped: submitted 10 minutes ago
Next run: 2026-10-13 14:23
Log: journalctl --user -u ccgather-autosubmit
When the scheduler reports a run that failed before the CLI could record it (for example npx could not fetch the package), status shows a Problem: line.
When turning it on, you are offered the GitHub star prompt unless you have already starred.
The macOS setup is covered by tests but has not yet been run on a real Mac; Windows and Linux (systemd and cron) have. If the job misbehaves, npx ccgather@latest autosubmit off removes it.
Set up through npx, the job runs the newest ccgather release each day (npx --yes ccgather@latest), so upgrades reach it on their own; --pin keeps it on the version you set it up with, and running on again moves it. A global install runs its own copy and follows npm install -g ccgather; --auto-update makes even a global install run ccgather@latest. Jobs created through npx with v2.3.0 or v2.3.1 are pinned to that version: run npx ccgather@latest autosubmit on once to update them (an npm older than 9.6.5 keeps running a cached copy of npx ccgather without @latest).
loginctl enable-linger $USER yourself.CC = Claude Code
Gather = Come together + Collect
"Where Claude Code developers worldwide gather"
This project was inspired by the following projects:
This project is distributed under the Apache License 2.0. See LICENSE for details.
Record. Track. Grow.