We will update this story as more independent testing is published. If you have used the feature and want to share what you found, write to the editorial team.
The timing is not an accident. Competitors have shipped similar updates in recent months, and every lab wants to be the default choice when a company signs a yearly contract.
How we reported this
Independent researchers were quick to test the claims. Early results broadly match what the company said, with the usual caveat: benchmarks measure narrow skills, and real work is messier than a test set.
- Available first to paid plans
- Independent tests are still limited
- No change to default privacy settings
- API access at a separate price
What changes for you
Privacy groups asked how the new data will be stored and for how long. The company says customer data is not used for training by default on business plans. Consumer plans have a setting that you should check.
The question is not whether it works in a demo. It is whether it works on Tuesday afternoon with real data.
A technology analyst
If you use these tools at work, ask your administrator whether the new feature is turned on, and what the company policy says about using it with customer data.
The details
For most readers, the change will be gradual. Paid users get access first, then the feature moves to free plans over the following weeks. Businesses usually wait for admin controls before they switch anything on.
Not everyone is convinced. Some analysts say the update is mostly about catching up with rivals rather than moving the field forward. Others point to small but useful changes that the headlines missed.
At a glance
| Question | Short answer |
|---|---|
| Who is affected? | Most everyday users, gradually |
| Does it cost more? | Not for now |
| What should I do? | Try it on a low-stakes task first |
What happened
Prices did not change, but limits did. Heavy users may hit the new caps sooner, especially when they upload large files or run long tasks in the background.
The practical advice is the same as always: try it on a low-stakes task first, check the output against a source you trust, and keep a human in charge of anything that matters.
