[_pdp_]

It is nice.

But!

The reason these tools exist is not because of non-professional developers, but quite the opposite.

A lot more professionals are now working on more projects simultaneously- something that was not practical just a year ago.

Though, while this is nice, considering that all of the action is happening on the same device, I am worried this is going to increase supply chain risks. Before, a developer would work on clearly designated projects for practical reasons. Now, the same developer can work across many projects that are quite different - for example, the marketing site and the backend - and because of an obscure and unimportant component on the marketing site, there can be an impact on backend systems.

I wrote more about this here: https://chatbotkit.com/reflections/everyone-is-a-vip-now

[sebmellen]

If I'm interpreting this correctly, GitHub will use their existing actions infrastructure to run versions of the code in isolated worktrees. I think this could be a very beneficial process.

What I've done on my end is created a project where I have a remote Linux workstation. I can create multiple worktrees for each repo in that workstation, and then my agent can push PRs to GitHub and use the actions infrastructure to see if the integration tests that it writes for itself are successful without needing to run those integration tests on the local environment. It's expensive in terms of runner hours, but the automaticity of it is incredible.

[jerezzprime]

There is full support for GitHub sandboxes today, and in the near future the remote session experience will improve, so your laptop (or your phone, or the web) can be the control plane.