Direct Answer
The important ChatGPT change is not one new toggle. Voice, plugins, connected apps, browser automation, and custom MCP tools are becoming parts of the same work surface. You can speak a request, let ChatGPT retrieve authorized context, create a document or spreadsheet, and continue a supported browser task. The useful setup is selective: enable the smallest set of tools required for one workflow, keep consequential approvals visible, and verify the output before it leaves ChatGPT.
Watch Rob's Walkthrough
Video and interface walkthrough credit: Rob The AI Guy. Feature availability and safety details below are checked against OpenAI's current documentation.
What Changed, and What Is Account-Specific
Rob's video shows an account where Voice can work inside ChatGPT Work, plugins are organized by use case, custom plugins and MCP apps can be added, and the Codex Chrome extension can use page context, memory, skills, and open tabs. He also demonstrates desktop-only settings for browsing, computer history, reasoning controls, background status indicators, and visual customization.
Not every control is universal. OpenAI says availability can depend on the plan, workspace, role, region, interface, app version, and rollout. A toggle visible in the video is evidence that Rob had it on his account, not that every personal or managed account has the same menu.
| Capability | Official status | Practical boundary |
|---|---|---|
| Live Voice | Official on supported web, mobile, desktop, and workspace experiences | Plan limits and workspace settings apply. Live does not support video or screen sharing. |
| Connected apps in Voice | Official for apps and plugins available to the account | Existing source permissions remain in force. Approvals happen on screen. |
| ChatGPT Library search in Live | Not currently supported directly | Attach a supported file manually or use an authorized connected source. |
| Custom MCP apps | Full MCP is beta for Business, Enterprise, and Edu; Pro supports narrower developer access | Admin, role, surface, and read/write restrictions differ by plan. |
| Cloud browser | Available in Work on eligible paid plans and supported regions | It uses a separate remote session and does not inherit the browser state on your device. |
| Built-in desktop browser | Available in the macOS and Windows desktop app | It has its own browser profile and may be restricted by workspace policy. |
| Chrome extension workflow | Best when an existing Chrome profile or signed-in tab is required | Check the active account and grant only the page or task access required. |
1. Choose the Right Voice Mode
OpenAI currently documents three Voice options. Live is the natural full-duplex mode and can use web search, memory, supported widgets, plugins, and connected apps. Advanced is the previous real-time mode and remains useful for eligible mobile video or screen-sharing workflows. Standard transcribes speech before producing each response.
Rob recommends Live for most users, which is sensible when the goal is a fluid conversation with connected tools. The right choice still depends on the job. Use Standard when you want a clearer turn-by-turn transcript. Use Advanced when mobile video or screen sharing is essential. Use Live when interruption, ongoing text, web information, and connected apps matter.
Voice can create documents, presentations, and spreadsheets in Work, but it does not erase the approval model. When an app action needs confirmation, Voice sends you to an on-screen control. A spoken “yes” is not enough.
2. Connect Apps Deliberately
Connected apps link ChatGPT to external services such as email, calendars, cloud files, or Slack. An app can search authorized information, retrieve documents, show an interactive experience, or perform supported actions. It cannot exceed the access already granted by the provider account or workspace administrator.
The safe sequence is simple:
- Connect the intended account, not whichever account happens to be active.
- Review the requested services and permissions before authorizing.
- Begin with search or read actions.
- Select or mention the app only on messages that need fresh external data.
- Keep approval prompts for sending, editing, deleting, sharing, purchasing, or changing account state.
- Disconnect the app when the workflow no longer needs it.
One correction matters: the transcript suggests enabling Library search for Voice. OpenAI's current Voice guide says Live cannot directly find or add files from the ChatGPT Library. That does not prevent manual attachments or authorized searches through a connected app.
3. Treat Plugins as Workflow Packages
A plugin and an app are related but different. An app provides a connection to an external service. A plugin can package reusable instructions, skills, connected apps, and configuration into a workflow. Installing a plugin does not silently grant the underlying app access to data.
Rob demonstrates selecting a vidIQ plugin inside a conversation. That is the useful pattern: invoke a specialized capability when the current message needs it. Avoid installing every “new and noteworthy” item. Review the publisher, included skills, required apps, data destination, write actions, privacy policy, and removal path first. An OpenAI Verified badge is a useful signal, but OpenAI explicitly says it does not replace your own security or vendor review.
4. Use Developer Mode for Controlled MCP Testing
Developer mode lets eligible users connect custom MCP-powered apps. Full MCP support, including write and modify actions, is still described as beta for Business, Enterprise, and Edu. Business admins and owners control deployment; Enterprise and Edu can add role-based access. Pro users can build apps and use narrower read/fetch MCP access, but do not receive the same full MCP capability.
Do not treat a remote MCP endpoint like a harmless prompt file. It exposes tools that can read data or take actions. Test it as software:
- Verify the operator, endpoint, authentication method, and requested scopes.
- Inspect every discovered tool and its input schema.
- Test read-only actions with non-sensitive data.
- Confirm that write actions pause for review where expected.
- Test expired authentication, repeated requests, malformed inputs, and unavailable services.
- Publish to a workspace only after an admin reviews the actions and access groups.
5. Choose the Correct Browser Surface
The video moves between the Codex Chrome extension, ChatGPT's desktop app, and a browser-based experience. Those surfaces do not share one universal browser state.
| Browser surface | Use it when | What it does not inherit |
|---|---|---|
| Cloud browser | A Work task should continue remotely after you leave or close the computer. | Your device's open tabs, saved passwords, cookies, extensions, and existing sign-ins. |
| Built-in desktop browser | You want to watch the page, annotate it, sign in directly, test localhost, or keep the task inside ChatGPT. | Your Chrome profile. It maintains a separate browser state. |
| Codex Chrome extension | The task needs your existing Chrome tabs, profile, signed-in session, cookies, or installed extensions. | Access is still scoped by the extension, active account, site, workspace, and approval settings. |
| Connected app or plugin | A structured integration can retrieve or update the required data directly. | It cannot access information outside the connected provider account's permissions. |
Prefer a structured app over visual browser control when both can complete the job. It is easier to constrain “read this calendar” than “click around my account until you find something.” Use browser automation for the remaining gap, and keep the task bounded to a named site and result.
6. Use Safer Settings Defaults
Rob shows personalized tips, suggested prompts, reasoning controls, dictation, browser permissions, and a setting that can provide broad internet and file access. Some are convenience preferences. Others materially change what the system can reach.
| Setting type | Good default | Why |
|---|---|---|
| Appearance, contrast, text size | Choose for comfort and accessibility. | These change the interface, not the permission boundary. |
| Suggested prompts and personalized tips | Optional. | Useful for discovery, but not required for better model quality. |
| Reasoning effort | Match it to task complexity. | More effort can cost more time or usage without improving a simple task. |
| Connected-app permissions | Always ask or allow read actions first. | Write access creates external side effects. |
| Browser website access | Approve the named host for the current task. | A page can contain malicious or misleading instructions. |
| Computer and filesystem access | One project, app, or folder. | Unrestricted access increases the impact of a mistake. |
| Memory and activity history | Enable only when persistent personalization is useful. | Review retention, training, and workspace policy separately. |
The external prompt-history tool promoted from 05:13 to 06:33 is Rob's separate product, not a native ChatGPT feature. It may be useful, but evaluate it as a third-party service: check what prompt content it stores, how long it retains history, whether it receives confidential material, and how to delete or export data.
A Practical First Workflow
Rob demonstrates turning an article into a YouTube title, description, tags, and script using the Chrome extension, page context, memory, and a channel-specific skill. The repeatable version is broader than content creation:
- Define one output. For example, a reviewable video brief from one approved source page.
- Name the source. Attach the tab or select the connected app explicitly.
- Apply one method. Use a reviewed skill or instructions that define structure and tone.
- Set prohibitions. Do not publish, message, download, purchase, or change accounts.
- Request evidence. Require links, quotations kept short, assumptions, and unresolved questions.
- Review the result. Check facts, voice, rights, and whether the output actually matches the requested format.
Read only the page I attached. Create a [deliverable] for [audience] using my approved [skill or style guide]. Separate facts from recommendations, cite the source for every factual claim, and flag anything the page does not establish. Do not browse other sites, publish, message anyone, download files, or change an account. End with a five-point review checklist.
Video Chapters
| Time | Section | Practical takeaway |
|---|---|---|
| 00:00 | ChatGPT Voice upgrades | Voice becomes an entry point to Work, apps, and deliverables. |
| 01:11 | Advanced settings | Check account capabilities, but do not assume every toggle is required. |
| 02:19 | Plugins and models | Route tasks deliberately and install only reviewed workflow packages. |
| 03:49 | Workflow settings | Developer mode and permissions change the risk boundary. |
| 05:06 | Prompt optimization | The featured shortcut tool is a third-party product, not ChatGPT itself. |
| 06:34 | Chrome extension workflow | Use page context, skills, and memory to create a reviewable deliverable. |
| 08:55 | Desktop app features | The desktop app exposes different browser, computer, and customization controls. |
| 10:53 | Final customization | Pin useful surfaces; appearance settings are preference, not capability. |
Sources and Further Reading
- Rob The AI Guy: ChatGPT's New Changes Are MIND BLOWING! (primary video and supplied transcript)
- OpenAI Help Center: ChatGPT Voice
- OpenAI Help Center: Connected Apps in ChatGPT
- OpenAI Help Center: Plugins in ChatGPT and Codex
- OpenAI Help Center: Developer Mode and MCP Apps
- OpenAI Help Center: Cloud Browser
- OpenAI Help Center: Built-in Desktop Browser
- OpenAI Help Center: Managing App Permissions
- OpenAI Help Center: Visual Experience Settings
YouTube lists the primary video's publication date as 27 September 2026. This article was reviewed on 28 September 2026. Product names, menus, limits, plan access, beta features, and workspace controls can change. The video documents the creator's account; OpenAI's current help pages are the source of truth for availability and permissions.