CodeRunwayA kinder way to make one useful change
A CLEARER WAY TO FINISH ONE USEFUL CHANGE.

Move from a coding issue to evidence.

CodeRunway gives students and solo builders a small, visible path from a coding question to a change they can read, judge against fixed criteria, and explain.

A quiet, fixed sample path. No progress is claimed until evidence arrives.

ILLUSTRATIVE SAMPLE PATH

The next step stays in view.

Not started
  1. Understandname the outcome
  2. Planchoose the checkpoints
  3. Patchmake the small change
  4. Inspectread what changed
  5. Checkmatch fixed criteria
  6. Verifyleave with evidence
SIGN IN OR STAY A GUEST

A role for the way you want to look around.

The sample workspace is open to everyone. Signing in adds a small role badge and gives Judges a read-only operations view.

USER

Walk the full sample flow.

Choose User and use the demo password shown on the sign-in form. The workflow, review, and static fixture checks stay the same.

Sign in as user
JUDGE

Open the operations view.

Judges also see safe provider status and current limits. The default demo password appears on the sign-in form when this deployment uses it.

Judge sign-in
HOW IT WORKS

A small path is easier to understand.

Each page has one job, so the work can feel concrete without hiding the decisions that matter.

  1. 01

    Name the change

    Start with the outcome you want, using a small sample issue with a clear boundary.

  2. 02

    Review the path

    See the checkpoints before anything runs. Keep the plan, reject it, or begin again.

  3. 03

    Leave with evidence

    Read the changed files, see which static fixture criteria matched, and finish with a next step you can explain.

A STEADY WORKSPACE

Helpful, without taking the wheel.

The interface keeps the remaining work visible while leaving the decisions and understanding with you.

  • You review before anything runs.
  • Progress is based on evidence, not decoration.
  • The sample workspace is fixed and safe to explore.
  • You can pause, reject, or restart at any point.
COMMON QUESTIONS

A few honest answers.

The short version: the workspace is a fixed sample, the checks are static, and sign-in is a demo role switch.

Do I need an account?

No. The sample workspace is open. The optional sign-in uses one shared password per role and creates no personal profile.

What does the Judge role unlock?

A read-only Judge console with safe provider status, limits, and quick links. It does not expose secrets or change model settings.

Does CodeRunway run my code?

No. It checks fixed file contents against static fixture criteria. It does not compile TypeScript, execute generated code, or run tests.

Can I use my own repository?

Not in this build. The sample issue and the two editable files are fixed so the evidence stays honest and bounded.

Read all questions
A SMALL TECHNOLOGY NOTE

A transparent path under the surface.

The live path can use Nebius Token Factory with NVIDIA Nemotron. The deterministic fallback works without credentials, so the sample remains ready to explore.

READY WHEN YOU ARE

Bring one small issue to the runway.

Start with the fixed sample task and decide what happens next.