Even a good pipeline cannot simply be “handed over” to a game designer or a developer on another team: it changes constantly and depends on the operating system, tools, secrets, and local environment.
An agentic prototyping pipeline can be configured for a game designer once, but a week later the original harness will have evolved while its copy remains stale. The roles should be divided differently: the engineer responsible for the harness develops the agentic pipeline, while the user runs it without reproducing the entire infrastructure locally.
Isolation also gets in the way of ordinary teamwork. A client developer should not necessarily wait for a server developer to become available: they could ask the server agent to build a temporary stub and begin integration. In turn, the server programmer could ask the client agent about implementation details for supporting the server contract. Today, every agent is confined within its owner and runtime.