A Brief History of Ralph
humanlayer.dev
A Brief History of Ralph
1–10 of 42 posts
Re: A Brief History of Ralph
#2Just look at the code quality produced by these loops. That's all you need to know about it.
It's complete garbage, and since it runs in a loop, the amount of garbage multiplies over time.
Re: A Brief History of Ralph
#3So it took the author 6 months and several 1-to-1s with the creator to get value from this. As in he literally spent more time promoting it than he did using it.
And it all ends with the grift of all grifts: promoting a crypto token in a nonchalant 'hey whats this??!!??' way...
Re: A Brief History of Ralph
#4There's a lot of irrelevant detail, but the article never actually explains what "Ralph" does or how it works.
Re: A Brief History of Ralph
#5I've been working with the Ralphosophy? for iterative behavior in my workflow and it seems pretty promising for cutting out a few manual steps.
I still have a manual part which is breaking the design document down into multiple small gh issues after a review but I think that is fine for now.
Using codex exec, we start working on a github issue with a supplied design document, creating a PR on completion. Then we perform a review using a review skill madeup which is effectively just a "cite your sources" skill on the review along with Open Questions.
Then we iterate through open questions doing a minimum of 3 reviews (somewhat arbitrary but sometimes multiple reviews catch things). Then finally I have I have a step in for checking Sonarcloud, fixing them and pushing the changes. Realistically this step should be broken out into multiple iterations to avoid large context rot.
What I miss the most is output, seeing whats going on in either Codex or Claude in real time. I can output the last response but it just gets messy until I make something a bit more formal.
Re: A Brief History of Ralph
#6There's a lot of irrelevant detail, but the article never actually explains what "Ralph" does or how it works.
It's explained under the July 2025 heading with link to the blog post where it was first shared.
The key bit is right under that though. Ralph is literally just this:
while :; do cat PROMPT.md | npx --yes @sourcegraph/amp ; doneRe: A Brief History of Ralph
#7So it took the author 6 months and several 1-to-1s with the creator to get value from this. As in he literally spent more time promoting it than he did using it. And it all ends with the grift of all grifts: promoting a crypto token in a nonchalant 'hey whats this??!!??' way...
the note about the crypto token was intended to “okay this is now hype slop and it’s time to move on”
Re: A Brief History of Ralph
#8There's a lot of irrelevant detail, but the article never actually explains what "Ralph" does or how it works.
there are hundreds of useful resources, including many linked in the article itself
Re: A Brief History of Ralph
#9Just look at the code quality produced by these loops. That's all you need to know about it. It's complete garbage, and since it runs in a loop, the amount of garbage multiplies over time.
I don’t think anyone serious would recommend it for serious production systems. I respect the Ralph technique as a fascinating learning exercise in understanding llm context windows and how to squeeze more performance (read: quality) from today’s models
Even if in the absolute the ceiling remains low, it’s interesting the degree to which good context engineering raises it
Re: A Brief History of Ralph
#10There's a lot of irrelevant detail, but the article never actually explains what "Ralph" does or how it works.
It's explained under the July 2025 heading with link to the blog post where it was first shared. The key bit is right under that though. Ralph is literally just this: while :; do cat PROMPT.md | npx --yes @sourcegraph/amp ; done
Thanks!