Post

We have reached a moment where instead of releasing software you simply release the detailed spec for software and tell people to prompt their agent to build it themselves From the README of OpenAI’s new Symphony orchestrator: github.com/openai/symph...

Daniel Grant

@djgrant.bsky.social

5 Mar

If they had released the code, critics would likely be scouring it for bugs and incoherence – which at 1m loc, it almost certainly has. Sensible move on their part – keeps the discussion on the ideas, and saves them having to own something they like don't want to maintain for general audience.

Patrick Johanneson 🚀👻 🇨🇦

@patrickjohanneson.com

5 Mar

I'm unclear on how every single installation of this having its very own set of bespoke, inevitable bugs is an improvement over a model where you find a bug and you release a patch for that bug.

Maggie Appleton

@maggieappleton.com

The canonical implementation gets patched. And then they update the spec with the patch too. I should have emphasised more the “implement in your programming language of choice” part. Where “own lang” could be any variety of design preferences. So you only prompt bespoke versions when needed.

5/3/26, 7:22 pm0 reposts1 like

Mike Samuel 🟣

@mvsamuel.bsky.social

5 Mar

Is there a bit of "we don't need to define configuration parsing; just prepend your config choices to the prompt." If the spec includes "if X is desired" it is less a description of a configurable program and more a lens through which instances with hard-coded config choices can be projected.