technology
Introduction
Ready machines for coding agents: describe what a project needs once, and each agent platform gets a setup file it can read, checked against its rules, with the setup run …
technology
Ready machines for coding agents: describe what a project needs once, and each agent platform gets a setup file it can read, checked against its rules, with the setup run …
technology
The idea. Describe the machine a project needs in one short file. preconfig writes the setup file each agent platform reads, checks the files a repository already has, …
case studies
Most repositories already say what they need. A .python-version file names the Python, requirements.txt the packages, a compose file the databases the developers run, …
case studies
A team that uses two or three agents writes the same setup two or three times: once as a Copilot workflow, once as a Cursor environment, once as a dev container. Each …
case studies
A setup file that looks right proves nothing. The only proof is a machine that starts empty, runs the setup, and then passes the project’s own tests. That is what …
case studies
Setup files are written once and changed many times. Every upgrade of a runtime or a database has to reach every file that installs it: the dev container, the Copilot …
next uses
The four case studies share one pattern. A machine that starts empty has to become a known, working machine before anyone can do useful work on it, and the knowledge of …
releases
Five targets covered the platforms that were reading setup files when preconfig started: dev containers, GitHub Copilot, Cursor, cloud-init and a plain script. Since then …
releases
A setup file for a coding agent breaks quietly. Someone bumps Python in the dev container and forgets the Copilot workflow, or edits the generated setup script by hand, …
doctor
When the Alpha ran orders-api’s setup with Redis left out of the spec, the machine printed 1,096 lines. The setup itself worked: every package installed and …