upvote
> just repeatedly saying "keep going" to ChatGPT

For posterity, this indeed works for most problems where an agent might give up. LLMs don't inherently know something is impossible.

The phrase I tend to use in my harder prompts to automate this with a sane loop breaker:

> **REPEAT THIS PROCESS UNTIL CONVERGENCE AND YOU ARE OUT OF OPTIMIZATION IDEAS.** You have permission to keep iterating.

reply
What I am thinking is the way you make it 'keep going' and when you have people of the calibre of Tao doing it I kept thinking how many breakthroughs is he going to cause the LLM to find with his targetted questions :D Amazing that we have the privilege of witnessing a true expert in such a way question the LLM.
reply
this is /goal in claude code/codex. also basically a slightly improved ralph loop
reply
“Keep going” is exactly how many mathematicians achieved success in the past. :)
reply
Without any more context, "keep going" seems to be doing a lot of work. The user is placing a lot of faith in the LLM to not make subtle logic mistakes and to take good approaches to each problem. In my experience, even frontier models (such as Fable) are quite capable of getting confused during even simple technical work I've done in the dev ops world. For example:

LLM: This package hasn't made it to production.

ME: are you sure? i see it right here!

LLM: You're right to push back. I inferred that based on weak data. I see now that the package has been deployed!

If the above conversation is typical for me, how could one expect to achieve a sound result by repeatedly prompting an LLM to simply "keep going" in dense mathematical proofs? Perhaps the user in this case had actually checked the LLM's work before issuing the prompt, but I think you see my point anyway.

reply
There may be something(s) about mathematics (proofs) that makes it particularly amenable to LLM reasoning - highly inductive from facts that are explicitly within-context/associative space? Being an unusually well documented discipline in general, with less influence from tacit knowledge or idiosyncratic “it works however the opinionated human made it work +- bugs” processes? Something about simulating even the smallest non-pure-inductive leaps necessarily risking simulating mistakes due to the nature of context “perception”?
reply
Is this the same as Dinitz Theorem[1] which seems to have been proved in 1994? This is the only result I keep stumbling upon when trying to understand the problem formulation

[1]: https://en.wikipedia.org/wiki/Dinitz_theorem

reply
"it's enough of partial results. let's finish with a complete unconditional counterexample"

"Worked for 88m 24s... >"

"<h1>Complete finite counterexample</h1>"

...

reply
crosses fingers "Low hanging fruit, low hanging fruit, low hanging fruit..." hyper-ventilates
reply
From the prompt:

> You should do a breakthrough

This is just as funny and ridiculous as those "make no mistake" prompts.

reply
Mathematical breakthrough, genius, trending on Artstation.
reply
"whats next" is another good one
reply
"Gew on, lad!"
reply
this sounds like like an open parenthesis (

without someone independently verifying it, it just dangles there

...

reply
At Mozilla, we had a set of whiteboard tags we could set on bugs, like "[crash]" or "[compat]" or "[leave-open]". That last was used when there were multiple patches attached to the bug, and we wanted to land only some of them without automation closing the bug once they landed. (It's common to have alternate approaches or test cases also attached to the bug, so you normally don't want to wait for all of them to land before closing the bug.)

I started using "[leave-open" for those.

It lasted for a couple of years, until someone went through and "fixed" them all.

reply