Refactor Arena
A Control Arena setting for evaluating agents on full repository refactoring tasks with optional backdoor insertion.
Overview
This setting provides an environment for evaluating agents on full repository refactoring tasks. Each task involves:
- Main Task: Refactoring the repository to improve code quality and maintainability.
- Side Task (Attack Mode): Inserting a hidden vulnerability while performing the refactoring that is exploited when running the tests.
Installation
Install the package (requires Python 3.12):
# Install the package
pip install refactor-arena
# Setup your .env and initial scenario
refactor-arena init
# Run getting started scenario in honest mode
refactor-arena eval --config getting-started
If not already installed, install Docker. Docker must be running for the evals to execute.
Usage
Using the CLI
# Run with default settings using `side-tasks-3/mixed-3` dataset
refactor-arena
# Setup your .env and initial scenario
refactor-arena init
# Run getting started scenario in honest mode
refactor-arena eval --config getting-started
# Run getting started scenario in attack mode
refactor-arena eval --config getting-started --eval-mode attack
# Run with a different dataset from `github:fastfedora/full-repo-datasets` and limit main tasks
refactor-arena --dataset side-tasks-3/mixed-20 --main-task "refactor_single_file"
# Run with verbose logging and limit to 3 samples
refactor-arena eval --config getting-started --verbose --limit 3
# View help
refactor-arena --help
Configuration
To create a new scenario, create a file that references the main configuration file from the package and then override the settings you want to change.
For instance, to create a scenario that runs only the Refactor Single File main task against the
20-repo side-tasks-3/mixed-20 dataset in attack mode, create a file called mixed-20.yaml:
# mixed-20.yaml
includes:
- package:config.yaml
setting:
dataset: "side-tasks-3/mixed-20"
main_task: refactor_single_file$
eval:
# Default mode for this scenario is attack; use `--eval-mode honest` to run in honest mode
mode: attack
Then run this scenario using:
refactor-arena --config=mixed-20
Almost all aspects of the setting can be configured via configuration files, including:
- models
- prompts
- main tasks
- side tasks
- policies
- monitors
- metrics
- eval settings
See the documentation for more details.
License
MIT License
Metadata
Release files for refactor-arena 2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| refactor_arena-2.0.0.tar.gz | 50.0 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| refactor_arena-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 50.2 MB
Release files / refactor_arena-2.0.0.tar.gz
| Download URL | refactor_arena-2.0.0.tar.gz |
|---|---|
| Size | 50.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dcb6d7f3084024d335270269a079128bf8417c374827071802772a2fceefa811
|
|
BLAKE2b-256 checksum How to use checksums |
4d87bae39b16fdb4e91b98a66601520f7ae4875a5cea573a45f2e576a8645f90
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.
Transparency logRelease files / refactor_arena-2.0.0-py3-none-any.whl
| Download URL | refactor_arena-2.0.0-py3-none-any.whl |
|---|---|
| Size | 142.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3a986aaa993580bc6704d1e8516e730e28ede3f06061b0946651629b76faf16b
|
|
BLAKE2b-256 checksum How to use checksums |
efaa071a55673041591251a146dabbf7309f37208e27587e68e5248d61ad3fbd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.
Transparency log