This is...concerning. I never use Claude with my closed-source projects, because I don't trust that they won't send the code to use for training. So I copy snippets, ask general questions, etc. Just now, I started a new prompt and got this. I didn't mention keyboards at all.
@danielsaidi likely a coincidence. Toolbars and keyboards are like bread and butter. Here's my bing search result for "SwiftUI toolbar" and the AI response immediately goes for a keyboard example.

@alexozun @danielsaidi I think it’s this too. They aren’t bright and just parrot information which does work okay a lot of times but other times they just go wrong.

I’ve just fixed a bug I didn’t catch the other day. It added a db query and used the library’s wherePK() function. Well if the primary key is id and version then you’ll never get the lastest version with that. It did this after fully explaining what makes up the primary key of the model.

@alexozun I asked and it said that it was due to my personal history of working on KeyboardKit haha.
@danielsaidi @alexozun It’s referenced my book to me before without me telling it about the book. I think it knows your name and pieces the rest together.
@RobW @alexozun I mean, as long as the memory is private and not used to train its models it’s fine, but it would be quite disastrous if a single Claude Code instance run in a closed source project is enough for it to share the code with its models.
@danielsaidi You're absolutely right! (Sorry I couldn't help myself).
I copied your prompt to Claude and it suggested ToolbarItemWidth, but when I tried adding "I'm Daniel Saidi" to the prompt, it suggested KeyboardToolbarItemWidth and later explained "Your name — Daniel Saidi is the creator of KeyboardKit! It came up from my training data".
What's interesting, Codex completely ignored this context, and when I pressed it to take my name into account it suggested SaidiToolbarItemWidth 😄
@alexozun Loooool that’s a pretty great experiment! 🥂 I mean public world knowledge is expected, I was just concerned.