Roadmap on preconfiguration.com

Introduction

Tue, 29 Sep 2026 00:00:00 +0000

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 on a clean machine before any agent starts.

Preconfiguration.com is a project to build that. Its engine, preconfig, is one small program. It reads a short spec, preconfig.yaml, writes the setup file each platform reads, checks the setup files a repository already has, and runs the whole setup on a clean machine to prove it works.

How It Works

Tue, 29 Sep 2026 00:00:00 +0000

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, and proves the setup on a clean machine. The agent doesn’t need to know any of this.

An AI coding agent in the cloud starts every task on a fresh machine. Something has to install the runtime, the packages and the services before the agent can build or test anything, and each platform reads that something from its own file, in its own format. GitHub Copilot’s cloud agent runs a workflow named copilot-setup-steps. Cursor’s cloud agents build a Dockerfile named in .cursor/environment.json. Codespaces and editors read .devcontainer/devcontainer.json. A fresh server reads cloud-init. Other agents take a script in their settings.

Next Uses: Six Places Where a Ready Machine Pays Off

Tue, 29 Sep 2026 00:00:00 +0000

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 what “working” means lives in one reviewed file, proven by a test. Coding agents came first because they start from an empty machine many times a day, on several platforms, with nobody watching.

The pattern turns up well beyond coding agents. None of the six uses below has been tested, and none is a goal of the Beta, though some would reuse what the Beta builds. This post sets out what each would ask of preconfig, what already carries over from the Alpha, and what would be new work. It is a map for choosing what to try after the Beta, ideally with the people who run these systems.

The Next Preconfiguration Prototype: A 12-Week Beta on the Agent Platforms Themselves

Tue, 29 Sep 2026 00:00:00 +0000

The Alpha answered one question. Can one short spec be compiled into every agent platform’s setup file, checked against each platform’s rules, and its setup run on a clean machine with the project’s tests? On one Linux machine, with sample repositories, the answer was yes. The next prototype, the Beta, takes on the harder question: do the files work on the platforms themselves, for real repositories, and does a team’s agent fail less often on them?

Where the Money Is in Preconfiguration: Fewer Failed Agent Sessions and Control Over Every Agent Machine

Tue, 29 Sep 2026 00:00:00 +0000

Preconfiguration is a prototype today, so its business case is a plan to test with customers. Nobody pays for the translation step by itself: compilers like this are cheap to write, and the engine that writes each platform’s file should be free, as most developer tools are. The money comes from teams that run several agents across many repositories, paying for fewer failed sessions, one view of every repository’s agent setup, and control over what agent machines install. Prebuilt machines, so sessions skip the install, come after that. None of it has been priced with a buyer yet.