What happened
OpenAI's announcement says people can now use their ChatGPT Business plan in supported third-party tools. It names Notion, v0, Amp, Kilo Code, Warp, Hermes from Nous Research, OpenClaw and OpenCode, followed by “and more.” The announcement directs users to connect through Sign in with ChatGPT to get started. It does not describe a new model or a new feature within any of the named tools; the stated change is a way to use a ChatGPT Business plan with them.
The named services span different kinds of work. Notion is a workspace, v0 is a development tool, and Amp, Kilo Code, Warp and OpenCode are associated with software development workflows. Hermes and OpenClaw are also included in the announced set. The list matters because it makes the integration concrete: this is not only a general claim about third-party compatibility, but an announcement naming products where the sign-in route is intended to work. OpenAI's wording also leaves room for additional supported tools beyond those named.
The sign-in instruction is the only setup detail in the announcement: connect using Sign in with ChatGPT. It does not explain whether a user must be an administrator of a Business workspace, how workspace membership is checked, what data is shared during sign-in, or what permissions a connected tool receives. Nor does it explain whether the plan pays for usage in a third-party product, whether that product requires its own subscription, or whether the same arrangement applies to every named service. The announcement gives no pricing, quota, version, rollout schedule, or regional availability details.
That makes the practical announcement narrower than “ChatGPT Business features are available everywhere.” It establishes that a Business plan can be used to sign in to the named services, and tells users how to begin. The scope of what that authentication enables after entry remains specific to each integration and is not detailed in OpenAI's statement. Teams will need to check the flow inside the service they plan to use rather than assume that one sign-in grants identical capabilities across the list.
What the archive adds
New Runtime's earlier coverage noted that OpenAI supports embedded MCP Apps interfaces in ChatGPT, a separate example of tools and interfaces meeting inside an AI product. That is related context, not the same integration: this announcement is about signing in to third-party tools with a ChatGPT Business plan. This is a new event. The earlier note is dated 2026-02-06.
Trend signal
This supports the direction described in Agent-ready software exposes capabilities: external tools become more usable when products expose a clear way to connect. The announcement establishes a sign-in path, but says nothing about the capabilities or permissions exposed after sign-in, so it is only a limited signal for that pattern.
Why now
OpenAI's announcement presents the sign-in route as available now and directs users to connect with Sign in with ChatGPT. It does not explain why the change is being made at this time or describe a broader rollout sequence.
Why it matters
A familiar account-based entry point can reduce friction for teams trying a supported tool, particularly when they already use ChatGPT Business. Naming products such as Notion, v0, OpenClaw and OpenCode also gives practitioners specific integrations to check rather than leaving them to infer compatibility from a broad platform claim.
But authentication is not the same as a shared workspace, shared entitlement, or controlled delegation model. A team should not assume that a Business plan covers third-party usage costs, that all workspace members can connect, or that the connected tool inherits the organization's access policies. Those details affect both procurement and security review. The useful near-term move is to test the sign-in flow in the exact product and account configuration the team intends to use, then confirm what plan, permissions, and data handling apply there.
Limits and uncertainty
OpenAI's announcement does not specify which Business-plan capabilities are available in each third-party tool, whether use is included in the plan price, or whether a separate subscription or usage charge applies. It also does not describe workspace-admin controls, account eligibility, the data exchanged during sign-in, or any per-tool permission model. These details could differ by integration. The announcement names several products and says “and more,” but does not provide a complete directory or state availability by region. The mechanics and terms should therefore be verified with the relevant tool before a team relies on the connection.
Skill to build now
Pick one supported tool your team already uses and test Sign in with ChatGPT using a non-sensitive account or workspace. Record whether the Business identity is accepted, what permissions the flow requests, and which capabilities are actually available after login. Confirm any separate subscription or usage charges with the tool provider before rolling it out to teammates.
Reader takeaway
ChatGPT Business can now be used as the sign-in route for a set of named third-party tools. Treat that as an access change, not proof that the plan pays for all tool usage or that every integration shares the same permissions and features. Verify the details in the specific product before adopting it across a team.