This morning I opened Atlas like I do every day, coffee in hand, and installed the latest update without thinking much about it. Then I noticed something important was missing: slash commands.
If you updated Atlas and suddenly could not find your shortcuts, custom GPTs, or saved command-style workflows inside the Ask sidebar, you are not alone. This is a bigger deal than it may look at first, especially if you were using Atlas as a real workflow browser and not just a place to chat.
Quick Answer
Atlas appears to have removed slash commands from the Ask experience. Before this update, typing a slash could bring up options tied to GPTs or shortcut-style instructions that could work with the page you were currently viewing.
That matters because those commands were one of the most useful power-user features in Atlas. Without them, Atlas feels further behind Comet, which still has a working slash menu with saved instructions and shortcuts.
What Changed In Atlas
Inside Atlas, the Ask button still opens the ChatGPT sidebar, and you can still type normal requests. The problem is that the slash command behavior is gone from the place where I expected it.
Previously, typing slash would bring up extra options. For people already using the OpenAI ecosystem, that meant quick access to custom GPTs and prebuilt workflows without leaving the page.
That was useful because the assistant could work in the context of the page you were on. If I was on a webpage and wanted a specific kind of summary, post draft, title idea, or instruction set, I could call that workflow quickly instead of rebuilding the prompt every time.
- Ask still works in Atlas.
- The old slash command menu is missing.
- Custom GPTs are still available elsewhere in the sidebar.
- The fast page-aware shortcut workflow is what feels broken or removed.
Why Slash Commands Mattered
Yes, you can still type something like “summarize this page.” But that misses the point. Slash commands were not just about saving a few keystrokes. They were about turning repeatable instructions into quick actions.
In Comet, these are called shortcuts. They are basically saved instructions that you can call whenever you need them. Atlas had an advantage because it could tie into GPTs many of us had already built inside OpenAI.
For me, that meant workflows for things like social posts, video summaries, title ideas, and other repeat tasks. A basic GPT like my Brew Buddy example does not really show the power of this because it does not need the current webpage. But a GPT or shortcut that reads the current page or video context is where this becomes useful.
Removing that without a clear replacement makes Atlas feel less capable for real day-to-day work.
Comet Still Has The Shortcut Edge
When I opened Comet to compare, the difference was obvious. Comet still has the slash menu. I can type slash and see saved shortcuts like job search, rule book, pin comment, ideas, and other workflows I have set up.
Those shortcuts can be edited directly. You can open one, hit the pencil, and see the saved instructions behind it. It is simple, but that is exactly why it works.
This is the gap that keeps getting wider. Atlas has the OpenAI ecosystem behind it, and I still prefer OpenAI for writing in many cases. But Comet is currently doing the browser workflow side better.
- Comet still supports slash shortcuts.
- Shortcuts are editable saved instructions.
- The workflow feels faster for repeated browser tasks.
- Atlas losing this makes Comet more appealing for power users.
Cloud Agents Versus Local Agents
Another big difference is how the two browsers handle agent work. Atlas runs agent tasks in the cloud. It spins up private tabs in the cloud and works through the page there, even if it feels like the action is happening locally.
Comet, from what I have learned using it, handles more of that browser interaction locally. It still uses the internet when needed, but the agent-style browser work is not hitting the same limits in the same way.
That matters because Atlas has a token limit for agent work. I mentioned 20 chats or tokens a month in the video because that is the practical limit I have been running into. When Atlas has to run these tasks in the cloud, you burn through that allowance quickly.
I have had months where I got through about a week, and another where I ran through the available agent usage in a day while trying to complete something. If agent work is a core part of your browser setup, Atlas may not be enough right now.
Where Atlas Still Makes Sense
I am not saying Atlas is useless. I still like OpenAI better for writing. It feels like it understands my style and context better, which makes it hard for me to walk away from my OpenAI subscription completely.
Atlas also still gives you access to ChatGPT and your GPTs through the sidebar. The issue is workflow speed and page-aware automation. If you are mainly asking questions or writing, Atlas can still make sense.
But if you depend on browser agents, repeatable shortcuts, or quick slash-triggered workflows, this update makes Atlas harder to recommend over Comet.
What To Do If Your Shortcuts Disappeared
If you updated Atlas and started clicking around trying to find your slash commands, the practical answer is simple: they appear to be gone from the Ask slash workflow for now.
I do not know if this was removed for security reasons, because OpenAI is rebuilding the feature, or because of some other limitation. There may be a good reason behind it. But from a user workflow standpoint, removing it without a replacement is a step backward.
For now, the workaround is to access your GPTs manually through the sidebar or use Comet for the shortcut-style workflows Atlas no longer handles well.
- Use the Atlas sidebar if you need to open a custom GPT manually.
- Use Comet if you rely on slash shortcuts and saved browser instructions.
- Watch your Atlas agent usage closely because it can run out quickly.
- Do not assume the feature moved somewhere obvious; the old slash behavior appears to be removed.
Key Takeaways
- Atlas removed or disabled the slash command workflow that previously surfaced GPTs and shortcut-style actions.
- This matters most for people using Atlas for repeatable browser workflows, not casual ChatGPT questions.
- Comet still supports slash shortcuts and editable saved instructions, which gives it a clear advantage for power users.
- Atlas agent work runs through the cloud, which makes the monthly usage limit feel restrictive for heavier workflows.
- OpenAI still feels strong for writing, but Atlas is harder to rely on for local browser-agent style work right now.
Watch the Video
The video above for the full walkthrough, including the Atlas sidebar test, the Comet shortcut comparison, and my real-time reaction to what changed after the update.
