zlacker

[return to "Cloudlflare builds OAuth with Claude and publishes all the prompts"]
1. infini+X7[view] [source] 2025-06-02 15:11:10
>>gregor+(OP)
From this commit: https://github.com/cloudflare/workers-oauth-provider/commit/...

===

"Fix Claude's bug manually. Claude had a bug in the previous commit. I prompted it multiple times to fix the bug but it kept doing the wrong thing.

So this change is manually written by a human.

I also extended the README to discuss the OAuth 2.1 spec problem."

===

This is super relatable to my experience trying to use these AI tools. They can get halfway there and then struggle immensely.

◧◩
2. diggan+D9[view] [source] 2025-06-02 15:20:31
>>infini+X7
> They can get halfway there and then struggle immensely.

Restart the conversation from scratch. As soon as you get something incorrect, begin from the beginning.

It seems to me like any mistake in a messages chain/conversation instantly poisons the output afterwards, even if you try to "correct" it.

So if something was wrong at one point, you need to go back to the initial message, and adjust it to clarify the prompt enough so it doesn't make that same mistake again, and regenerate the conversation from there on.

◧◩◪
3. int_19+bx[view] [source] 2025-06-02 17:39:28
>>diggan+D9
Chatbot UIs really need better support for conversation branching all around. It's very handy to be able to just right-click on any random message in the conversation in LM Studio and say, "branch from here".
◧◩◪◨
4. carlos+SB[view] [source] 2025-06-02 18:13:21
>>int_19+bx
AI Studio has this, I usually ask it to plan and I do some rounds of refining until the plan covers all my requirements, then I branch this conversation, a branch for each feature, none of the branches get polluted this way.
[go to top]