How Codevalanche works

Give the task a brief. Follow it through.

One example: change trip durations from minutes to hours and minutes. Start with a narrow request, follow the activity and inspect what changed.

Codevalanche on Windows: a finished task in a sample project. The agent lists its steps and a summary, and two changed files wait for review.
The sample task, after execution. The assistant summary is not independent test evidence.

From the first message to the diff.

  1. Open the project

    Use a small example repository on disk. Check its starting state so you can distinguish existing edits from the task’s changes.

  2. Choose the connection and write the brief

    Select an available agent or local model. For Claude Code and Codex, check the chosen account. Ask for durations above one hour to use hours and minutes, and request tests.

  3. Follow the activity

    Read the agent’s steps and any request for input. When a command needs permission, inspect the command and its scope before allowing or denying it.

  4. Inspect the changes

    Open the changed files and read the diff. Check the duration examples yourself and run the project’s relevant tests before accepting the result.

Three views of the same example.

These are separate application captures, not a live demonstration or a verified continuous recording. Open an image to inspect the full view.

A new task in Codevalanche with a written brief in the message box, ready to send.
The brief names the desired output: 90 minutes becomes 1 h 30 min.
An approval request in Codevalanche: the agent asks to run npm test, with Allow once and Deny buttons.
This permission request concerns running a command; it does not approve every edit.
The changes view in Codevalanche, showing the diff of two edited files.
Two changed files are available for review. Read the diff and check the behavior.