Do you tell anyone which parts of your product were written by AI?
I work in AI text detection, so I spend most of my time on the content side of this question: whether a paragraph can be traced back to a model. Vibecoding asks the same thing one layer down, about code, and the answers people give are completely different.
Nobody labels a commit. There's no convention for it, nothing in a README, and the honest reason might be that a label wouldn't survive anyway. Once generated code has been reviewed, renamed and refactored into the rest of the codebase, whatever was distinctive about it is gone. One editing pass does the same thing to a watermark in text.
So does provenance matter for code, or only for content?
Where I've got to so far, and I'd change my mind easily on this:
For what I ship to users, the output is mine regardless of what typed it, so a label would be noise.
For anything someone else has to maintain, I'd want to be told, because generated code tends to fail in a different place: the structure is plausible and the edge cases are wrong.
For client work, it's their question to ask rather than mine to volunteer, though I'd answer it straight.
For open source, I honestly don't know. A contribution nobody has read is a different object from one somebody wrote.
Do you state it anywhere, in a commit message, a PR description or a README? And if you have, did it change how people responded to the work?
Replies