Bootstrapping Composer with autoinstall

Summary

RL training depends on runnable environments, because broken setup can consume tokens and compute without producing a reward signal or can make a task unsolvable. Composer autoinstall addresses this by using earlier Composer models to turn unconfigured repository checkouts into working mock environments. A Cursor agent first proposes 10 commands and expected outputs, while a separate Composer agent configures the checkout, mocks dependencies, and is evaluated against three selected commands. The process can create placeholder files, images, database tables, MinIO configurations, Docker containers, and startup scripts, restarting up to five times before discarding an environment. In a Celo monorepo experiment, the agent installed dependencies including Foundry and eventually mocked a user to run a minimal application; Composer 2 later scored 61.7% on Terminal-Bench versus 47.9% for Composer 1.5.

Takeaways

1. 1

   The first stage proposes 10 setup, test, or launch commands and describes the output expected from a correctly configured environment.

2. 2

   Autoinstall can create mock files, images, database tables, MinIO configurations, Docker containers, and startup scripts for missing project dependencies or long-running processes.

3. 3

   In the described benchmark, Composer 2 scored 61.7% on Terminal-Bench, compared with 47.9% for Composer 1.5.