Build notes, practical systems, and a closer look at what changed. Written to help you make a decision, try something useful, or avoid learning the annoying part twice.
A ChatGPT Site can host a supported plugin, but the useful question is what its tools should be allowed to do. Here is a practical contract-and-test process before you share.
A Team Bot crosses several access boundaries. Map each one, test shared chats separately, and keep credentials and high-impact actions narrowly scoped.
A shared AI coworker is only useful when the team has a clear job, shared reference material, a checkable result, and someone who will keep the context current.
A screenshot request is incomplete until its destination is explicit. Give agents an approved private path, restrict public actions, and test the fallback before an agent reaches for a personal repository.
A repository search is not a complete audit. Start with the people who could publish, inventory public surfaces using metadata, and route suspected screenshots through a controlled response process.
ChatGPT Images 2.5 may make reference-led editing more reliable. A repeatable source, edit, inspect and approve loop still matters more than trusting a promising output.