SolveBase 1.0.0

SolveBase questions, answered.

SolveBase is a free Chrome extension that automatically saves newly accepted Codeforces, LeetCode, CSES, CodeChef, and GeeksforGeeks solutions to a public GitHub repository.

It organizes solution files by platform and updates your repository README. Start with the installation guide or find an answer below.

Maintained by Tushal Lohar. See the source code and technical documentation and the privacy policy.

For supporting references and a comparison with manual saving, read how SolveBase works.

About SolveBase

What does SolveBase do?

SolveBase is a free Chrome extension that detects newly accepted coding submissions and saves the source code to a public GitHub repository using platform-specific folders. It also updates the repository README with solution counts.

Which coding platforms does SolveBase support?

SolveBase supports Codeforces, standard LeetCode problem pages, CSES, CodeChef, and GeeksforGeeks. LeetCode contest and Explore editors are not supported in version 1.0.0.

Can I save Codeforces solutions to GitHub automatically?

Yes. SolveBase watches Codeforces verdicts, waits for the final accepted result, and commits the solution to a GitHub rating folder.

Can I save LeetCode solutions to GitHub automatically?

Yes. On standard LeetCode problem pages, SolveBase detects an accepted submission and saves the solution under an organized LeetCode topic folder in GitHub.

Does SolveBase support CodeChef, CSES, and GeeksforGeeks?

Yes. SolveBase supports accepted submissions from CodeChef, CSES, and GeeksforGeeks practice pages alongside Codeforces and standard LeetCode problems.

Does SolveBase upload source code to its own server?

No. The extension sends repository updates directly to GitHub. The SolveBase OAuth service handles only the short-lived GitHub authorization exchange.

Can SolveBase use an existing GitHub repository?

Yes. SolveBase can connect a compatible existing public solutions repository, index recognized solution files, and preserve content outside its managed README summary block. Private repositories and unrelated non-empty repositories are not supported.

Does SolveBase import every old solved problem automatically?

No. SolveBase focuses on live accepted submissions. Existing compatible files are indexed when you connect a repository, but old platform submissions are not scraped in bulk.

How do I save coding solutions to GitHub automatically?

Install SolveBase from the Chrome Web Store, choose a public repository name and your coding platforms, then connect GitHub. Stay signed in to a supported coding platform and submit a solution with the extension active. SolveBase saves newly accepted solutions directly to GitHub.

Is SolveBase free and which browsers support it?

SolveBase is free to install and works in Chromium-based browsers such as Chrome, Edge, Brave, and Arc. The extension uses Manifest V3 and does not require a SolveBase account.

Does SolveBase work for interview preparation?

Yes. It creates a searchable GitHub archive of accepted practice problems, making it easier to review patterns, show consistent practice, and keep a public coding portfolio up to date.

LeetCode

Can SolveBase save LeetCode solutions to GitHub?

Yes. SolveBase watches standard leetcode.com/problems/ pages and sends newly accepted solutions directly to the public GitHub repository you select while the extension is active.

How are LeetCode files organized?

Solutions are grouped under a leetcode folder and organized by topic, with problem names and README counts kept consistent as new solutions arrive.

Does SolveBase support LeetCode contests?

Version 1.0.0 supports standard LeetCode problem pages. LeetCode contest and Explore editors are not currently supported.

Can I bulk-export my previous LeetCode submissions with SolveBase?

No. SolveBase captures newly accepted submissions while the extension is active. It can index recognized solution files already in a compatible public GitHub repository, but it does not download your previous LeetCode submission history.

Codeforces

Does SolveBase save Codeforces solutions after pretests pass?

No. Passing pretests is not a final accepted verdict. SolveBase waits for system testing and commits the solution only after the final accepted result. It can track pending Codeforces verdicts for up to seven days, including after leaving the tab or restarting Chrome.

How are Codeforces solutions organized in GitHub?

SolveBase groups solutions under the codeforces folder by problem rating. Solution filenames identify the problem, and the repository README summary updates as accepted solutions are saved.

Can SolveBase connect my existing Codeforces solutions repository?

Yes, if it is a compatible public solutions repository. SolveBase recognizes platform folders and conventional solution filenames, including older Codeforces layouts with rating folders at the repository root. Existing recognized files keep their folder and filename stem.

Can SolveBase import all of my past Codeforces submissions?

No. SolveBase detects new submissions while the extension is active. Connecting an existing repository indexes recognized files already in GitHub; it does not bulk-download your Codeforces submission history.

CSES, CodeChef, and GeeksforGeeks

How do I save CSES solutions to GitHub automatically?

Install SolveBase, enable CSES, choose a public GitHub repository, and connect GitHub. Stay signed in to CSES and submit on its problem set task pages with the extension active. SolveBase saves newly accepted solutions under the cses folder, grouped by problem set section, and updates the repository README summary.

How do I save CodeChef solutions to GitHub automatically?

Install SolveBase, enable CodeChef, enter the requested username, and connect a public GitHub repository. Submit on a supported CodeChef problem or submission page while signed in and with the extension active. SolveBase saves newly accepted solutions under the codechef folder by problem rating; problems without an available rating use an Unrated folder.

How do I save GeeksforGeeks solutions to GitHub automatically?

Install SolveBase, enable GeeksforGeeks, enter the requested username, and connect a public GitHub repository. Submit a practice problem while signed in and with the extension active. SolveBase saves newly accepted solutions under the geeksforgeeks folder, grouped by problem difficulty, and updates the repository README summary.

Setup and troubleshooting

Why does SolveBase ask me to confirm that my solutions will be public?

SolveBase supports public GitHub repositories only. Anyone can read solutions committed to a public repository. The setup confirmation makes this visibility explicit before GitHub is connected; private repositories are not supported.

What GitHub permissions does SolveBase request?

SolveBase uses GitHub OAuth with the public_repo scope to create and update public repositories. This permission applies to public repositories on your account, although SolveBase uses the repository you select. You do not need to create or paste a personal access token. You can revoke access in GitHub Settings under Applications.

Why has my accepted solution not appeared in GitHub?

Check that SolveBase is enabled, the platform is selected, your requested username is correct, and you are signed in to the coding platform. Confirm that you submitted on a supported page and that GitHub is connected in the extension popup. Codeforces pretests are not a final accepted verdict. Accepted solutions that fail to reach GitHub can be retried locally for up to 24 hours; reconnect GitHub if the extension requests it.

What happens if I reconnect GitHub or change repositories?

Reconnecting the same GitHub account and repository preserves pending submissions. Changing the GitHub account or repository clears the old work queue. Files already committed to GitHub remain in the original repository.

What happens when I solve the same problem again?

SolveBase updates the existing solution file instead of counting the problem twice. Recognized files from an existing solutions repository keep their folder and filename stem; if the solution language changes, the file extension changes to match.

Will SolveBase overwrite my existing README?

SolveBase updates its marked summary block and preserves README content outside that block. When you connect a compatible public solutions repository, it rebuilds its local index from recognized platform folders and solution filenames. Unrecognized scratch files are ignored, and unrelated non-empty repositories are rejected.

GitHub access and public solutions

Do I need to give SolveBase my GitHub password or a personal access token?

No. SolveBase connects through GitHub OAuth: select Connect GitHub in the extension and authorize it on GitHub. You do not enter your GitHub password into SolveBase or create and paste a personal access token. The authorization token is stored in trusted Chrome extension storage on your device.

Does SolveBase support private GitHub repositories?

No. SolveBase 1.0.0 supports public GitHub repositories only and requests GitHub's public_repo OAuth scope. You must confirm that your repository and saved solutions will be publicly visible before connecting GitHub.

How do I disconnect SolveBase and revoke its GitHub access?

Disconnect GitHub in SolveBase to remove the authorization token from the extension. To revoke the OAuth grant, open GitHub Settings, choose Applications, and revoke SolveBase under Authorized OAuth Apps. Resetting or uninstalling SolveBase removes its local settings and connection data. Solutions already committed to GitHub remain in your repository until you delete them there.

Need help with a specific submission?

Open a support issue with the platform, extension version, expected behavior, and error message. Omit tokens and secrets.

Install SolveBase free