Successive requirements
Work unfolds across a sequence of development tasks, each introducing the next set of requirements.
Software keeps evolving.
Can coding agents keep up?
Multi-step-SWE evaluates coding agents across successive requirements in the same codebase.
Real development moves forward through new requirements, changing dependencies, and evolving standards. Multi-step-SWE brings that continuity into coding evaluation.
Work unfolds across a sequence of development tasks, each introducing the next set of requirements.
Changes become the starting point for subsequent work. Earlier implementation choices shape what comes next.
Step-level evaluation makes it possible to inspect progress throughout the sequence. The full evaluation protocol is coming with the paper.
Follow a packaging modernization task from its legacy build system to reproducible, standards-aligned releases.
Move the existing Python project from a legacy setup.py build to a PEP 517 build system.
The existing project and its behavior are the starting point for the migration.
Summarized task requirements. Evaluation results and complete task specifications will accompany the release.
We're preparing the paper, first evaluation results, and release materials. They'll be available right here.
Meet Klavis AITask construction, evaluation protocol, and findings.
Model comparisons and detailed evaluation results.
Release artifacts and instructions for getting started.