CP Sync

CP Sync watches your submissions on Codeforces, CodeChef, LeetCode, HackerRank, AtCoder, vJudge, GeeksforGeeks, CSES, NeetCode etc. When a solution is accepted, the extension fetches your source code and commits it to a GitHub repo, organized by platform, difficulty, and contest.

You don’t need to copy‑paste or remember to update your repo at the end of a session. The extension handles everything in the background.

Features

• Auto‑detects Accepted verdicts on nine major judges.
• Manual Push with Autofill- for judges not yet supported or when detection misses a submission. The autofill reads problem name, link, and difficulty from your current tab.
• Duplicate prevention- identical solutions are not re‑committed.
• Streak tracking and push history- see your daily streak and a log of every commit.
• Automatic retry- transient GitHub errors are retried with exponential backoff.
• Fully customisable- commit message templates, language handling, and folder structure.

Supported platforms: Codeforces, CodeChef, LeetCode, HackerRank, AtCoder, vJudge, GeeksforGeeks, CSES, NeetCode and others using manual push.

Setup

1. Install the extension.
2. On GitHub, create a fine-grained Personal Access Token with Contents: Read and write permission and grant it access to the repository where you want to store your solutions.
3. Open CP Sync and enter:

GitHub Username/Organization: the owner of the repository Repository Name: the repository name only, without .git Personal Access Token: the token created in Step 2 Branch: the branch where you want your solutions committed 4. Click Test Connection to verify that CP Sync can access the repository. 5. Select the competitive programming platforms you want to sync and click Save Settings.

Once connected, solve problems normally. When CP Sync detects an Accepted submission, it automatically pushes the solution to your configured GitHub repository.

Tutorial Watch the video above to see how CP Sync works and how to set it up: https://youtu.be/VFVmT0_PKoY

Privacy: Your GitHub token is stored locally in Chrome’s storage and is never sent anywhere except to GitHub’s API. The extension does not collect any personal data.

License: MIT Copyright © 2026 nafiuw_nebir