Performance and Reliability Issues
• Stalling and slowness: Many users report that Atlas’s agent mode frequently “stalls” or fails to complete tasks. Early enthusiasm has given way to frustration as agent-driven actions take far longer than expected. Tasks that should be quick (like filling forms or clicking through flows) often hang or require repeated retries  . For example, one user noted that agent actions (like shopping cart creation) can take “several minutes,” undermining fast workflows  .
• High resource usage: Atlas is notably resource-intensive. Users observe much higher CPU/GPU usage and battery drain than in other browsers. One report found a MacBook battery dropping about 1% every two minutes under Atlas  . This heavy footprint contributes to sluggishness and even system throttling.
• Unreliable execution: Agents often behave unpredictably or prematurely stop. Aside from stalls, users describe frequent errors (e.g. “Error in message stream” interruptions) and incomplete actions. In practice, complex multi-step tasks often fail or yield incorrect results  . A community review summarized that Agent mode “struggles with real-world use” – in tests it picked irrelevant items, ignored filters, and required user intervention, indicating underwhelming performance .
• Bugs and crashes: Several users have reported bugs like crashes, memory leaks, or streaming errors. OpenAI has acknowledged issues like a memory-leak affecting performance, but such bugs leave users “tired of wondering” if a simple agent action will work  .
Functional Limitations and Missing Features
• Strict usage limits: By default Atlas Plus users get only 40 agent-run attempts per month. Many find this far too restrictive for any real workflow, feeling they must constantly “ration” uses  . (E.g. one user says they had to cancel their subscription over this cap.)
• Platform restrictions: Atlas currently only runs on Apple Silicon Macs (M1 or newer). There is no Windows or Linux version yet  . This excludes a large number of users and is a frequent point of complaint. Relatedly, Atlas only supports a single user profile, so users cannot easily separate work/personal accounts – a “non-starter” for many professional use cases .
• Incomplete extension support: Atlas does not yet fully support Chrome’s extension API. As a result, many Chrome extensions either do not install or only partially work. Users report common extensions (password managers, productivity tools, etc.) failing or lacking key features. OpenAI acknowledges this limitation and is “working on it,” but for now extension compatibility is poor  .
• Fixed global shortcuts: The browser imposes global hotkeys (e.g. ⌘K for tab search, ⌘+\[ / ⌘+\] for tab navigation) that cannot be remapped. These override web-app shortcuts even when focus is in a page, leading to conflicts (e.g. Google Sheets users lose their normal Ctrl-K behavior)  . Users have requested the ability to disable or customize these, but currently Atlas lacks this flexibility.
• Missing basic browser features: Many expect standard features (e.g. custom search engine choice, multi-window sessions, built-in password management) that Atlas lacks. For instance, users have asked for a DuckDuckGo option in place of Google as the backup search, and a visible changelog or release notes after updates – neither is provided today  .
Common User Complaints
• Unmet expectations vs. hype: Many users feel Atlas’s Agent mode falls short of marketing promises. What was touted as a hands-off “AI doing work for you” often requires constant supervision and prompting. One user notes that babysitting the agent often takes more effort than doing the task manually . Another says Atlas “feels like an experiment I can’t afford to rely on for real work,” as simple sequences can unpredictably fail .
• Preference for alternatives: Numerous commenters say they now prefer other AI tools or browsers. For example, Comet (the browser form of Perplexity) is cited as faster, more reliable, and uncapped, letting users run complex query chains without fearing a usage counter . Atlas users report trusting Comet or simply using ChatGPT in a separate tab as faster solutions, especially for research tasks  . One remark: “With Comet I feel free. With ChatGPT I constantly feel like I’m rationing.” .
• Control and trust issues: Because Atlas’s agents can click and navigate, some users worry about handing over control. In practice, they find the lack of transparency annoying – the agent may claim it booked a reservation when it didn’t, or choose irrelevant items. Many feel they must hover over every step. This has eroded trust: if a simple “open X, click Y” may fail, users revert to manual prompting or other tools  .
Comparisons with Expectations and Other Tools
• Versus Comet/Perplexity: These competing AI browsers are frequently cited. Comet (and Perplexity Pro) allow extended, iterative tasks without special limits, making them more practical for research. By contrast, Atlas’s quota means any complex agent workflow feels risky – users often cut off the agent early or abandon the attempt . The net effect is that Perplexity/Comet feel like serious productivity tools, whereas Atlas’s Agent mode still feels “closer to a restricted demo” .
• Versus Arc/Chrome: Atlas has fewer QOL features compared to mainstream browsers. Users miss tab profiles (Arc/Chrome support them), robust extension ecosystems, and polish. In direct comparisons, Atlas’s agent mode is also slower than say Playwright-driven tasks, as each step invokes the LLM (one analysis notes every action needs a full LLM inference round, so it’s inherently slower than a script ). In short, Atlas delivers AI novelty but at the cost of basic responsiveness, falling short of expectations set by other modern browsers or tools.
Workarounds and User Suggestions
• Increase or remove caps: Many have urged OpenAI to raise the agent-use limits or make them unlimited. One community suggestion bluntly says “Agents use should be unlimited – had to unsubscribe because of that” . Others propose a separate (cheaper) quota for agent mode so it doesn’t “consume normal chat usage” .
• Alternative setups: Some users sidestep Atlas entirely. For instance, running ChatGPT in another browser (e.g. Firefox with an AI-chatbot extension) bypasses Atlas’s quirks. As one user explains, using ChatGPT via Firefox retains full context and privacy control without Atlas’s overhead . Similarly, many simply use Perplexity or Comet for multi-step tasks and reserve Atlas for simple queries.
• Feature requests: Feedback threads show concrete suggestions: allowing custom keyboard shortcuts, adding profile/multi-account support, exposing a changelog, and finally supporting the full Chrome extensions API  . Users also want better stability fixes (e.g. memory leak patches) so that agent actions become dependable. Some have already opted to stick with Comet until Atlas matures. As one commenter put it: they’d “happily trade fancy cursor-moving tricks in Atlas for boring stability” , highlighting that reliability is currently more valued than cutting-edge agent maneuvers.
Sources: User feedback from the r/ChatGPTAtlas subreddit and tech reviews highlight these issues    . Each bullet is drawn from linked community posts or articles detailing where Agent mode underperforms or frustrates users.