RepoPilot

coder / code-server

Search coder/code-server

GitHub

Code

How coder/code-server is laid out, and where to start for common changes.

There is no import map for this report yet.

Where to start reading

  1. Repository root
  2. Likely public API
  3. Likely public API
  4. Likely start-up file
  5. Likely start-up file
  6. Suggested starting pointAI
  7. Suggested starting pointAI
  8. Suggested starting pointAI

Find files for a task

AI

Add a new API route endpoint

  • Import and register the route in src/node/routes/index.ts by calling the route function with the app router.

Add a new browser page or UI element

  • Register the page route in src/node/app.ts or appropriate routes file to serve the HTML.

Add support for a new language/locale

  • Update src/node/i18n/index.ts to include the new locale in the loader if lazy-loaded.
  • Update CLI or settings to expose the locale option to end users.

Change the public API

Trace runtime behavior

Add or update tests

Change build or automation

RepoPilot lists up to 500 files, so a file missing here may still exist.

  • Files marked “likely” are guessed from their names.
  • Some entry points named in the manifest are build output or are missing from the file list, so their source is not shown.
  • 1 suggested change pattern has no matching file and is left out.

Code quality and hotspots

Largest source files

  • Branch points31 per file on average
  • Code issues1 error, 22 warnings
  • Largest file1,018 lines
  • Hotspot load1 high-risk file

Static checks on the 15 largest source files.

Tests, CI and tooling

  • CIGitHub Actions8 workflows
  • Tests64 test filesJest/Vitest · 1.9 test files per source file (file count, not coverage)
  • Dependency updatesDependabot · Renovate · Trivy

Test folders: test/e2e · test/e2e/extensions/test-extension · test

Hotspots

Files that change often and branch heavily, highest first. Branch points count if, loop, case, catch, ternary, && and || in the file.