Live data from Hacker News

Cloudlflare builds OAuth with Claude and publishes all the prompts

github.com

21–30 of 552 posts

Re: Cloudlflare builds OAuth with Claude and publishes all the prompts

#21
I’ve been using Claude (via Cursor) on a greenfield project for the last couple months and my observation is:

1. I am much more productive/effective

2. It’s way more cognitively demanding than writing code the old-fashioned way

3. Even over this short timespan, the tools have improved significantly, amplifying both of the points above

Re: Cloudlflare builds OAuth with Claude and publishes all the prompts

#22
post #7

I guess for me the questions is, at what point do you feel it would be reasonable to this without the experts involved in your case? As an edit, after reading some of the prompts, what is the likelihood that a non-expert could even come up with those prompts? The really really interesting thing would be if an AI could actually generate the prompts.

Why do you need a non-expert? We built on layers of abstractions, AI will help you at whichever layer you're the "expert" at. Of course you'll need to understand low-level stuff to work on low-level code

i.e. I might not use AI to build an OAuth library, but I might use AI to build a web app (which I am an expert at) that may use an OAuth library Cloudfare developed (which theya are experts at). Trying to make "anyone" code "anything" doesn't seem like the point to me

Re: Cloudlflare builds OAuth with Claude and publishes all the prompts

#23
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.

Re: Cloudlflare builds OAuth with Claude and publishes all the prompts

#24
post #17
post #13

> In all seriousness, two months ago (January 2025), I (@kentonv) would have agreed. I'm confused by "I (@kentonv)" means here because kentonv is a different user.[0] Are you saying this is your alt? Or is this a typo/misunderstanding? Edit: Figured out that most of your post is quoting the README. Consider using > and * characters to clarify. [0] https://news.ycombinator.com/user?id=kentonv

He is quoting from the project readme. I wrote all this text.

Thanks for weighing in here

If I might make a suggestion, based on how fast things change, even within a model family, you may benefit from saying Claude what. I was especially cognizant of this given the recent v4 release which (of course) hailed as the second coming. Regardless, you may want to update your readme to say

It may also be wildly out of scope for including in a project's readme, but knowing which of the bazillions of coding tools you used would also help a tiny bit with this reproduction crises found in every single one of these style threads

Re: Cloudlflare builds OAuth with Claude and publishes all the prompts

#25
post #13

> In all seriousness, two months ago (January 2025), I (@kentonv) would have agreed. I'm confused by "I (@kentonv)" means here because kentonv is a different user.[0] Are you saying this is your alt? Or is this a typo/misunderstanding? Edit: Figured out that most of your post is quoting the README. Consider using > and * characters to clarify. [0] https://news.ycombinator.com/user?id=kentonv

[deleted]

Re: Cloudlflare builds OAuth with Claude and publishes all the prompts

#26

[flagged]

Until you make your own website, then you love them

I've made plenty of websites, still don't love them and still get served 5+ captchas sometimes, straight after each other. Perhaps I have to give them money, then I'll love them?

Re: Cloudlflare builds OAuth with Claude and publishes all the prompts

#28
post #24
post #17

Earlier quoted context omitted.

He is quoting from the project readme. I wrote all this text.

Thanks for weighing in here If I might make a suggestion, based on how fast things change, even within a model family, you may benefit from saying Claude what . I was especially cognizant of this given the recent v4 release which (of course) hailed as the second coming. Regardless, you may want to update your readme to say It may also be wildly out of scope for including in a project's readme, but knowing which of th…

> It may also be wildly out of scope for including in a project's readme

The entire point of the repository seems to be to invalidate/validate the thesis if LLMs are good enough to be pair programmers right now. Removing it from the README makes no sense in that context.

Post reply on HN