# Companion Window Should Stay Available for ChatGPT (Not Only Codex)

**URL:** <https://community.openai.com/t/companion-window-should-stay-available-for-chatgpt-not-only-codex/1386295>\
**Category:** Feature requests\
**Tags:** codex, macos\
**Created:** [July 10, 2026, 12:25pm UTC](https://community.openai.com/t/companion-window-should-stay-available-for-chatgpt-not-only-codex/1386295 "2026-07-10T12:25:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mert\_Can\_Donmez](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/mert_can_donmez/32/511523_2.png) [@Mert\_Can\_Donmez](https://community.openai.com/u/Mert_Can_Donmez)\
**Post date:** [July 10, 2026, 12:25pm UTC](https://community.openai.com/t/companion-window-should-stay-available-for-chatgpt-not-only-codex/1386295/1 "2026-07-10T12:25:09Z")

</div>

The recent macOS app update changed the Companion Window so it now opens Codex instead of a regular ChatGPT conversation. This significantly impacts workflows for users who rely on both experiences.

Previously, I used the Companion Window (Option + Space) as a lightweight way to quickly ask ChatGPT questions while working in Codex. It was one of the best productivity features in the macOS app because it allowed me to keep my coding session uninterrupted while still having instant access to a general AI assistant.

Now, pressing Option + Space opens Codex instead. Since I’m often already using Codex in another window, this creates unnecessary friction. I don’t need a second Codex window—I need quick access to a normal ChatGPT conversation for brainstorming, explanations, documentation, research, or unrelated questions.

Please consider one of the following solutions:

- Restore the Companion Window as a ChatGPT conversation.

- Allow users to choose what opens with Option + Space (ChatGPT or Codex).

- Provide separate shortcuts for ChatGPT Companion and Codex.

- Allow both Companion windows to coexist.

The previous behavior made multitasking between coding and general AI assistance seamless. The current implementation removes that flexibility and makes the shortcut much less useful for developers who actively use both ChatGPT and Codex.

Please bring back the option to open a ChatGPT Companion Window.

---

<div class="post-metadata">

**Author:** ![Sara5](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/sara5/32/511875_2.png) [@Sara5](https://community.openai.com/u/Sara5)\
**Post date:** [July 10, 2026, 2:31pm UTC](https://community.openai.com/t/companion-window-should-stay-available-for-chatgpt-not-only-codex/1386295/2 "2026-07-10T14:31:23Z")

</div>

+1 I agree with U！Eu gosto disso muito. Espero isso pode volta!!

---

<div class="post-metadata">

**Author:** ![OpenAI\_Support](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/openai_support/32/561845_2.png) [@OpenAI\_Support](https://community.openai.com/u/OpenAI_Support)\
**Post date:** [July 10, 2026, 4:56pm UTC](https://community.openai.com/t/companion-window-should-stay-available-for-chatgpt-not-only-codex/1386295/3 "2026-07-10T16:56:13Z")

</div>

Hey [**Mert\_Can\_Donmez**](https://community.openai.com/u/mert_can_donmez) and [**Sara5**](https://community.openai.com/u/sara5), welcome to the forum!

That's indeed frustrating. I'll pass this feedback along to the product team so they can review the request and decide whether reverting to the previous ChatGPT shortcut makes sense.

Avinash

---

<div class="post-metadata">

**Author:** ![avinash.api](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/avinash.api/32/741581_2.png) [@avinash.api](https://community.openai.com/u/avinash.api)\
**Post date:** [July 10, 2026, 4:56pm UTC](https://community.openai.com/t/companion-window-should-stay-available-for-chatgpt-not-only-codex/1386295/4 "2026-07-10T16:56:22Z")

</div>