whatisgithub

What is swe-interact?

scaleapi/swe-interact — explained in plain English

Analysis updated 2026-05-18

24ShellAudience · researcherComplexity · 4/5Setup · hard

In one sentence

A 75-task benchmark that tests AI coding agents on realistic, multi-turn conversations with a simulated user, not a coding tool itself.

Mindmap

A visual breakdown will appear here once this repo is fully enriched.

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Evaluate how well a coding agent like Claude Code or Codex handles multi-turn developer requests.

USE CASE 2

Compare different AI models on the same set of realistic software engineering tasks.

USE CASE 3

Use the included run configs as a starting point to benchmark a custom agent or model.

USE CASE 4

Cite the accompanying research paper when using the benchmark results in academic work.

What is it built with?

ShellHarborModal

How does it compare?

scaleapi/swe-interactalexwortega/claude-ml-intern-skillbusybee3333/sol-governed-codex
Stars242424
LanguageShellShellShell
Setup difficultyhardmoderatemoderate
Complexity4/54/53/5
Audienceresearcherresearcherdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1h+

Requires installing Harbor, setting up Modal for sandboxes, and configuring multiple API keys before a run works.

So what is it?

SWE-Interact is a benchmark, a set of test tasks used to measure how well AI coding agents perform, rather than a tool you would use to build your own software directly. It contains 75 tasks that test coding agents on multi-turn software engineering work, meaning the agent has to go back and forth with a simulated user over several exchanges instead of getting one instruction and producing one answer. The goal is to evaluate agents in a setting closer to how a real developer actually works with feedback and follow-up requests, rather than a single isolated coding request. The repository holds the task data itself along with example run configurations for a system called Harbor, which is the framework used to actually execute these benchmark tasks. To use it, you install Harbor from its own separate repository, and set up Modal, a service used to provide sandboxed environments where the tasks run safely. Running a benchmark requires setting several credentials in an environment file, including API keys for the AI models involved. One model plays the role of the simulated user asking for changes, and a separate model is used to grade the agent's work against a rubric. The README lists several ready-made run configurations for different coding agents and models, including Codex, Claude Code paired with different Claude models, Gemini through OpenCode, and Kimi, each needing its own specific API key set in the environment file. Once configured, you launch a benchmark run with a single shell command from the repository root, and results are written to a results folder. There is also a simpler single-turn version of the benchmark included for baseline comparison. The project accompanies a research paper describing the motivation for reimagining these coding benchmarks around realistic, user-driven, multi-turn sessions rather than one-shot tasks, and the README asks that the paper be cited if the benchmark is used in research.

Copy-paste prompts

Prompt 1
I want to run the SWE-Interact benchmark using Claude Code, what API keys and environment variables do I need to set up in harbor/.env?
Prompt 2
Explain the difference between the multi-turn and single-turn task modes in SWE-Interact.
Prompt 3
Walk me through installing Harbor and Modal so I can execute a SWE-Interact run config.
Prompt 4
I want to create a custom run config for a new model, how should I copy and modify an existing script in run_configs?
Prompt 5
What does it mean that SWE-Interact uses a simulated user model to grade coding agents over multiple turns?

Frequently asked questions

What is swe-interact?

A 75-task benchmark that tests AI coding agents on realistic, multi-turn conversations with a simulated user, not a coding tool itself.

What language is swe-interact written in?

Mainly Shell. The stack also includes Shell, Harbor, Modal.

How hard is swe-interact to set up?

Setup difficulty is rated hard, with roughly 1h+ to a first successful run.

Who is swe-interact for?

Mainly researcher.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.