You could accomplish all of it with claude -p (headless mode).

Admittedly I might be missing a flag or two with claude, but how are multiple loops and comparisons of solutions done with just headless mode?

You have building blocks like "--resume <sessionId>" and "--fork-session".

For example, one thing you can do is curate the context of an "immutable" conversation and then reuse it as a base context for other prompts.

It's just a prompt.

Via skills.

Indeed.

Where are people finding time for these sort of projects.

They bootstrap a workflow with a prompt then build an orchestrator off that then prompt it to be converted to an opencode plugin and then prompt a website to be generated advertising it and then prompt a tool that reviews hacker news feedback and automatically incorporates feedback into next generation of the tool. At the end of the week they go to their manager and complain they are out of tokens for the actual job they are being paid for.

Haha, not far off. Only difference is I'm not spending my tokens at work. I use this on a side project video game that I'm developing.