top | item 47096602

(no title)

btrettel | 9 days ago

I'm reminded of something I read recently about disclosure of AI use in scientific papers [1]:

> Authors should be asked to indicate categories of AI use (e.g., literature discovery, data analysis, code generation, language editing), not narrate workflows or share prompts. This standardization reduces ambiguity, minimizes burden, and creates consistent signals for editors without inviting overinterpretation. Crucially, such declarations should be routine and neutral, not framed as exceptional or suspicious.

I think that sharing at least some of the prompts is a reasonable thing to do/require. I log every prompt to a LLM that I make. Still, I think this is a discussion worth having.

[1] https://scholarlykitchen.sspnet.org/2026/02/03/why-authors-a...

discuss

order

selridge|9 days ago

This is totally infeasible.

If I have a vibe coded project with 175k lines of python, there would be genuinely thousands and thousands of prompts to hundreds of agents, some fed into one another.

Whats the worth of digging through that? What do you learn? How would you know that I shared all of them?

selridge|9 days ago

> I log every prompt to a LLM that I make.

How many do you have in the log total?

btrettel|9 days ago

I have a daily journal where I put every online post I make. I include anything I send to a LLM on my own time in there. (I have a separate work log on their computer, though I don't log my work prompts.) Likely I miss a few posts/prompts, but this should have the vast majority.

A few caveats: I'm not a heavy LLM user (this is probably what you're getting at) and the following is a low estimate. Often, I'll save the URL only for the first prompt and just put all subsequent prompts under that one URL.

Anyhow, running a simple grep command suggests that I have at least 82 prompts saved.

In my view, it would be better to organize saved prompts by project. This system was not set up with prompt disclosure in mind, so getting prompts for any particular project would be annoying. The point is more to keep track of what I'm thinking of at a point in time.

Right now, I don't think there are tools to properly "share the prompts" at the scale you mentioned in your other comment, but I think we will have those tools in the future. This is a real and tractable problem.

> Whats the worth of digging through that? What do you learn? How would you know that I shared all of them?

The same questions could be asked for the source code of any large scale project. The answers to the first two are going to depend on the project. I've learned quite a bit from looking at source code, personally, and I'm sure I could learn a lot from looking at prompts. As for the third question, there's no guarantee.