Setup · about 10 minutes

Set up CP Lang on your machine

The browser runs the same compiler, but contests go faster in your own editor. Tick each step as you go; this page remembers your progress.

0 of 6 done

  1. 1. Install cpl

    One line installs a prebuilt binary. It is available from the first release not published yet:

    curl -fsSL https://cp-lang.org/install.sh | sh

    That installs the latest stable release. Add --edge for the newest build of main that passed every check:

    curl -fsSL https://cp-lang.org/install.sh | sh -s -- --edge

    Until then, or on a platform without a binary, build it with Rust:

    cargo install --locked --git https://github.com/ryanbai1412/cp-lang cpl-cli
    cpl --version
  2. 2. Install the editor extension

    Every editor talks to the same language server, cpl lsp: diagnostics as you type, hover, completion, go to definition, rename and quick fixes.

    A .vsix on the releases page, and Marketplace and Open VSX (Cursor, Windsurf, VSCodium) installs, not published yet. Until then, package it from the repository:

    cd editors/vscode
    npm install
    npm run package
    code --install-extension cp-lang.vsix
  3. 3. Check it works

    Open a .cp file and type let x = ; an error should appear as you type. Then:

    echo 'print("hi")' > hi.cp
    cpl run hi.cp
  4. 4. Pick your judge

    A judge profile fixes the compiler, flags, stack and source limit, so local runs behave like the judge. See all profiles.

    cpl judges
    cpl build --judge codeforces a.cp
  5. 5. Set up the contest loop

    Create a problem, keep its tests running on every save, stress it against a brute, then check it's ready.

    cpl new a
    cpl watch a
    cpl stress a.cp
    cpl submit a.cp

    One-click problem import from Competitive Companion not published yet.

  6. 6. Optional: point your AI assistant at the docs

    /llms.txt indexes the docs and /llms-full.txt is all of them in one file, ready to paste into a rules file.