Skip to content

Concepts

Four ideas explain most of how cg behaves. Worth ten minutes before the guides.

  • Authentication — CodinGame has no API tokens, so cg login drives a real browser and captures the resulting session cookies.
  • Profiles — named identities with their own credentials and defaults, plus the config.yaml / settings.json split and how the two resolve.
  • Working directories — the data/ + .meta/ layout both managers share: what's yours, what's a disposable cache, and why puzzles have no git repo but contributions do.
  • Languages and toolchains — how a language is chosen, and how compiled languages build and run in Docker without you installing a toolchain.

See also the design notes for decisions that aren't obvious from the code.