Hacker News

points by kevcampb 4 days ago | 0 comments

Last week Claude seemed to trigger /feedback automagically in a session, even though we've got that turned off in our org settings. Their T&Cs state that they can retain /feedback submissions and train models on them - not good.

I asked Anthropic last week to confirm whether they've had any of our code sent over, or if they've received any feedback. They've stopped responding to my support requests.

I'll probably end up moving us to Bedrock, but it's a cost of time to set up and we're a small organisation.

[–] l1n 4 days ago

I think this is the new Claude Code in-session suggestions for feedback - I think they generate in-session even though they're unsubmittable for the org. Kind of bad UX.

[–] nbulka 4 days ago

The absolute worst and the reason I switched from Anthropic to Codex. Codex caught wind of it of course and now they do use the unsuspecting message: We are reviewing this request (do you mean hoping to train on it? or reviewing?) and if you would like to use a different model, press the "any" key. I wonder if they collect the data they make a point to collect, that would make so much sense ... we need to speak out against these type of data collection patterns. Terrible UX and a dark pattern for them to use the same "accept" buttons of 1, 2, 3 etc. The irony is that THESE feedback messages are the sole thing driving me to consider running open source models locally.