ChatGPT Work Now Operates Logged-In Websites
💡See how ChatGPT Work handles logged-in sites without exposing user passwords.
⚡ 30-Second TL;DR
What Changed
Users must complete the website login themselves before delegating tasks to ChatGPT Work.
Why It Matters
This expands ChatGPT Work from public-web assistance into authenticated business workflows such as internal portals and SaaS tools. Organizations should still evaluate session isolation, permissions, auditability, and the risk of unintended actions before broad deployment.
What To Do Next
Pilot ChatGPT Work on a low-risk authenticated SaaS workflow, restricting permissions and logging every action before connecting it to production systems.
Key Points
- •Users must complete the website login themselves before delegating tasks to ChatGPT Work.
- •ChatGPT Work can maintain the authenticated session for subsequent website operations.
- •OpenAI says the AI never sees or accesses usernames and passwords.
🧠 Deep Insight
Background and context from public sources — not the original article. 6 sources cited.
🔑 Enhanced Key Takeaways
- •The feature utilizes a cloud-based browser for web and mobile interfaces, while the desktop application leverages an internal device-level browser to maintain session persistence.
- •This capability follows the August 9, 2026, sunsetting of the standalone 'Atlas' browser, with its automation features now integrated directly into the ChatGPT and Codex platforms.
- •The system mandates explicit user confirmation before the AI executes high-stakes actions, specifically including payment processing and final reservation submissions.
- •The functionality is restricted to paid tiers, specifically available to users on ChatGPT Plus, Pro, and Business subscription plans.
- •The architecture ensures that user credentials are neither transmitted to the model nor utilized for the purpose of training future iterations of the AI.
📊 Competitor Analysis▸ Show
| Feature | ChatGPT Work | Claude (Claude in Chrome) |
|---|---|---|
| Browser Interaction | Cloud-based (Web/Mobile) / Local (Desktop) | Real-time browser session control |
| Credential Handling | Zero-knowledge (No credential access) | Session-based interaction |
| Primary Focus | Multi-step enterprise/work automation | Direct browser-based task execution |
🛠️ Technical Deep Dive
- Employs a secure session-token management system that allows the AI to operate within an authenticated environment without direct access to the underlying authentication credentials.
- Integrates browser automation logic previously developed under the Atlas project into the core ChatGPT and Codex inference engines.
- Utilizes a hybrid deployment model where desktop clients use local browser instances for session persistence, while web/mobile clients rely on cloud-hosted browser environments.
- Implements a human-in-the-loop (HITL) verification layer that intercepts and pauses execution for user approval on sensitive operations like financial transactions.
🔮 Future ImplicationsAI analysis grounded in cited sources
⏳ Timeline
📎 Sources (6)
Factual claims are grounded in the sources below. Forward-looking analysis is AI-generated interpretation.
Weekly AI Recap
Read this week's curated digest of top AI events →
👉Related Updates
AI-curated news aggregator. All content rights belong to original publishers.
Original source: ITmedia AI+ (日本) ↗
This is a summary, not the original. Read the source, or get the weekly briefing.
Weekly AI briefing
One email a week. Unsubscribe anytime.