The questions nobody answers straight

Not by typing into a chat window. It reads what you write and writes back — it isn't connected to your files, your company's systems, or anything else unless you deliberately connect it, which takes several explicit steps. You can close the tab at any point and nothing has changed anywhere.

That changes once you do connect it to something, or let it run actions on your behalf. Those are different activities with real consequences, and they're covered separately under Connecting tools.

To the company running the tool, over the internet, where it's stored. Whether it's also used to improve their models depends on which product and which plan you're on — personal accounts and company accounts usually have different rules, and personal accounts often have a setting you can turn off.

Find that setting before you paste anything real. It's usually under Settings, labelled something like data controls or training. If you're on a work account, your IT department has likely already decided this for you, and the answer to "am I allowed" lives in your company's policy, not in the tool.

Yes. Regularly, and in a confident tone that reads exactly like the parts it got right. There's no signal in the writing that separates a correct answer from an invented one. This is the single most important thing to understand about the technology.

Which is why every guide here treats output as a draft to check, never as an answer to trust. Use it where you can verify the result — because you know the subject, or because you can test it. Avoid it where you can't.

Sometimes yes, sometimes no, and a lot of companies haven't decided. Check for a written policy first. If there isn't one, assume the strict version: no customer data, no employee data, no financial figures, no anything you'd be uncomfortable seeing forwarded outside the building.

The good news is that the restriction is usually about your company's data, not about your work. A great deal of what you do — thinking through a problem, drafting, structuring, checking your logic — never involves pasting real records at all.

No. Every guide on this site is written for someone who has never opened a terminal and doesn't plan to. Where a step genuinely requires a technical tool, it says so at the top, before you've spent any time on it.

Nobody honestly knows, and anyone who tells you they do is selling something. What's visible so far is narrower: it's fast at first drafts, summarising, restructuring, and boilerplate, and unreliable at anything requiring accountability or real judgment about your specific situation.

That's not a reassurance, it's just where things currently stand. The practical response is the same either way — knowing what it's actually good and bad at puts you in a better position than avoiding it or overtrusting it.

Because a lot of that certainty is performance. The tools are genuinely useful for some things and genuinely oversold for others, and the loudest voices rarely distinguish between the two. Feeling behind is mostly a marketing achievement.

You don't need to catch up on a field. You need one task done well. That's what everything here is organised around.