VSForces

VSForces bridges Codeforces with VS Code - giving you a full competitive programming workflow without leaving your editor.

• Browse and fetch random problems by rating
• Read the full problem statement (with LaTeX math) in the VS Code sidebar
• Test cases auto-load into CPH Judge in your currently open file - no new file created, no language prompt
• Track submission verdicts in real time
• Built-in per-problem stopwatch
• Auto-commit & push accepted solutions to GitHub with a detailed README

How It Works

VSForces is made of two parts that work together:

Codeforces Page
      │  (content script scrapes problem)
      ▼
Chrome Extension  ──────────────────────┐
      │  WebSocket  ws://127.0.0.1:6543  │
      ▼                                  │
VS Code Extension ◄─────────────────────┘
      ├── Sidebar (problem statement + timer)
      ├── Writes .prob file → CPH Judge auto-detects
      └── Auto-commit on Accepted → GitHub

You need both installed for VSForces to work.

Requirements

Node.js is NOT required - you are installing a pre-built extension, not building from source.

Installation

Step 1 - Install the VS Code Extension

Option A: From the VS Code Marketplace (recommended)

1. Open VS Code
2. Go to the Extensions view (Ctrl+Shift+X)
3. Search for VSForces
4. Click Install

Step 2 - Install CPH Judge

1. Open VS Code
2. Go to the Extensions view (Ctrl+Shift+X)
3. Search for Competitive Programming Helper
4. Install the extension by DivyanshuAgrawal

Step 3 - Install the Chrome Extension

The companion browser extension is required to connect Codeforces to VS Code.

1. Go to the VSForces-Bridge GitHub repository
2. Follow the instructions in the repository's README to load the extension into Chrome or Edge

Pin the extension to your toolbar for easy access.

Step 4 - Set CPH Default Language (Recommended)

To prevent CPH from prompting for a language every time:

1. Open VS Code Settings (Ctrl+,)
2. Search for cph.general.defaultLanguage
3. Set it to your preferred language: cpp, java, python, etc.

Usage

Before You Start

Open your solution file in VS Code (Main.java, solution.cpp, etc.) before browsing to a problem. CPH loads test cases into whichever file is currently active.

Fetch a Random Problem

1. Click the VSForces icon in the VS Code Activity Bar (left sidebar)
2. Set Min / Max rating in the sidebar
3. Click Get random problem
4. The problem opens in Chrome and the statement appears in the sidebar with test cases loaded in CPH automatically

Browse to Any Problem Manually

Navigate to any Codeforces problem page in Chrome - the sidebar and CPH update automatically.

Submit & Track Verdict

Submit on Codeforces as normal. The verdict appears in the sidebar within ~60 seconds.

Timer

A stopwatch starts automatically when a new problem loads. You can pause, resume, or reset it manually. It stops automatically on Accepted.

Auto-Commit & Push

When you get Accepted on a problem, VSForces can automatically commit your solution to a Git repository and push it to GitHub.

What Gets Committed

For each solved problem, a folder Codeforces/<Problem Title>/ is created containing:

• solution.<ext> — your accepted code
• README.md — a detailed summary including:
  • Problem link, rating, time/memory limits
  • Tags
  • Full problem statement (converted from HTML)
  • Sample test cases with input/output

Setup

1. Open VS Code Settings (Ctrl+,)
2. Search for autogitcommit
3. Enable the Autogitcommit: Enable setting

On first use, VSForces will guide you through setup:

• If your workspace isn't a Git repo → prompts to run git init
• If no remote is configured → asks you to enter a remote URL (e.g. https://github.com/user/repo.git)
• If no upstream branch is set → automatically runs git push -u origin <branch>

Robustness

The auto-commit feature handles common edge cases automatically:

• Unsaved files are saved before committing
• Special characters in problem titles (/, \, :, ?, etc.) are sanitized for valid folder names
• Remote changes are pulled (with rebase) before pushing to avoid rejection
• Dirty working tree changes are stashed before pull and restored after
• Rebase conflicts are auto-aborted to keep your workspace clean
• Duplicate submissions of the same solution show "Already committed" instead of erroring
• Concurrent verdicts are queued — only one commit runs at a time

Settings

Features

Troubleshooting

License

Proprietary - All rights reserved. See the LICENSE file for details.