For a quick overview of major changes, use What's new. For versioned changes and fixes, use the changelog. For the instructions and conditions that apply now, open the linked feature guide. Those three pages answer different questions.
Match the entry to the app you are using
The official changelog includes ChatGPT and Codex updates. Its navigation offers categories including General, ChatGPT desktop app, Codex Mobile, and Codex CLI, plus month links. Do not assume an entry mentioning a model or a familiar feature applies to every product in that list.
Write down your own surface first: ChatGPT in a web browser, the desktop app, or a particular mobile app. Include the installed version when you are checking a versioned app change. Then compare the entry's heading, date, platform, and qualifications with that record.
This source route was checked on October 23, 2026. The official pages continue to change; use their current entries rather than treating an old screenshot or this article's example as the latest release list.
Read the condition after the feature name
One real example appears in OpenAI's October 12–16, 2026 overview. It describes opening Your dot through iOS widgets and Shortcuts. The entry says the features are rolling out with ChatGPT for iOS 1.2026.279 and require dot access. It links to the setup instructions and access conditions.
That does not establish that a particular reader has dot access, that an Android app has the same widget, or that updating an iPhone app alone will enable it. The platform, version, rollout, and access conditions all matter. This is an example of reading an announcement, not a recommendation to enable that feature.
Use a small comparison note when something appears to disagree:
| Check | What to record |
|---|---|
| Official entry | Its URL, date, and exact feature heading |
| Applies to | Named product, platform, version, and stated conditions |
| Your setup | Actual app or browser, version if relevant, and workspace |
| Observed difference | The specific missing control or different behavior |
| Unresolved condition | A requirement you have not established for this account |
Do not fill an unresolved condition with “must be a bug.” It may be a bug, but the note has not established that yet.
Use the current guide for the next action
A changelog explains a change at a point in time. A feature guide explains how to use the feature and may contain newer qualifications. Follow the entry's documentation link and check that it describes your surface. If the feature has moved or been renamed, retain the old dated entry as the history and use the current guide for instructions.
If you reached developer request parameters while looking for a setting in ChatGPT, use the product-versus-API documentation guide. An API changelog is relevant when you are integrating the API; it does not supply the missing steps for a consumer app setting.
Avoid changing unrelated account settings to make a tutorial match. First identify which documented condition is unconfirmed and whether the guide supplies a way to check it. If it does not, keep that question open.
Save an actionable update note
For a team, “ChatGPT has a new feature” gives colleagues too little to act on. A useful note can be this short:
Update checked: [DATE AND OFFICIAL ENTRY URL]
Relevant change: [ONE SENTENCE]
Applies to: [PRODUCT / SURFACE / STATED CONDITIONS]
Our observed setup: [ACTUAL DETAILS]
Action needed: [SPECIFIC DOCUMENTED STEP, OR NONE]
Still unconfirmed: [ACCOUNT CONDITION OR OBSERVED DIFFERENCE]
Current instructions: [OFFICIAL FEATURE-GUIDE URL]
Complete it from the source and your own observation. Do not announce that everyone has received a rollout because one colleague can see it. Keep the entry and the observed setup together so the next person can check the same conditions before changing how the team works.