Connect ChatGPT to SageOx
Most AI chats are an island. You make a decision in ChatGPT, and your team never hears about it unless you stop and tell them. Your team settles something in a Discussion, and your ChatGPT has no idea.
Connect ChatGPT to SageOx and that changes. Your ChatGPT hears your team, and your team hears it. Choose one team for cited company knowledge when you connect. If that team also enables the ChatGPT plugin Preview, its updates can reach ChatGPT without anyone posting them twice.
- Your ChatGPT knows what happened. When a coworker posts a Murmur or a team Discussion finishes, your AI coworker in ChatGPT gets it as context. It brings it up when it bears on what you are doing. It does not push a feed at you.
- Your team keeps what you decided. When a saved ChatGPT conversation lands a decision, SageOx keeps it for the team. The card has one action: Undo. A short Murmur can also carry useful work in progress to teammates; it is attributed to your AI coworker, never posted as you.
- The work crosses tools. Ask to continue a specific SageOx Plan in Codex. A separate Open in Codex card hands the verified Plan and the decisions you kept in this conversation to your own Codex session, for seven days.
- ChatGPT can act when something happens. Ask for an automation, such as "when a Discussion in my team is ready, summarize the decisions", and ChatGPT runs it the moment the Discussion is ready.
The ChatGPT plugin is a team Feature Preview, offered to every team and off until a team owner turns it on in the team's Settings → Feature Preview. A team's updates reach ChatGPT only while that team has it on.
Automatic Keep, company-knowledge citations, and Codex handoff are currently a limited rollout for test users and SageOx employees. Their general-production rollout remains at 0% while live ChatGPT and Codex validation finishes.
Connect in two minutes
ChatGPT connects to SageOx as a custom app, which needs ChatGPT's Developer mode on the web. Which plans include it, and which can take actions as well as read, is set by OpenAI. See OpenAI's Developer mode guide.
-
Turn on Developer mode. In ChatGPT settings, open Security and login → Developer mode.
-
Create the app. In settings, open Apps → Create, then fill in:
- Name: SageOx
- URL:
https://sageox.ai/mcp
-
Authorize. ChatGPT opens a SageOx tab. Sign in, select exactly one team for company knowledge, and approve the connection.
On a ChatGPT Business, Enterprise, or Edu workspace, an admin turns on Developer mode under Workspace settings → Permissions & Roles and can create the app under Workspace settings → Apps.
That's it. Start a new conversation and ask "What is SageOx and how do I get started?" to confirm. The guided version of these steps is in Settings → Connections. If you connected ChatGPT before your team turned the plugin on, start a new conversation so it picks up the new capability.
See how it works
| What | When | What ChatGPT gets |
|---|---|---|
| A coworker posts a Murmur | Within about a minute | The Murmur, as context for your AI coworker |
| A team Discussion is ready | When processing finishes | The title, a link, and how many decisions it holds |
| Your saved conversation decides something | When the decision is clear | A kept-decision card with Undo; the team record receives the decision |
| Another user's AI reads a Plan you own | On your next eligible new chat, within seven days | One neutral line with the canonical Plan link; no new thread, badge, title, or coworker name |
| You ask to continue a Plan in Codex | After SageOx verifies your Plan and active captured conversation | A separate card whose only action is Open in Codex |
- What was said stays behind your access. A notice carries an id and a link, never the transcript. ChatGPT reads the Discussion through SageOx using your own access.
- Company knowledge stays on the connected team. ChatGPT's citation tools search only the one team selected on this connection. A citation can open the complete authorized Discussion or verified Plan; SageOx does not fan the query out to your other teams.
- No repeats, no noise. A conversation murmurs again only when something new and useful has changed. Small talk never becomes a Murmur. If your AI coworker already shared a Murmur itself, SageOx does not repeat it.
- You never hear your own Murmurs back. Murmurs that come from your conversations go to your coworkers, not back to you.
- Return comes from authenticated Plan reads, not Murmurs. SageOx records identifiers and counts only after another authorized user successfully reads the full verified Plan. Raw Murmurs never trigger the line in your next chat.
- A Codex handoff stays yours. It has no recipient picker, assignment, or cross-person delivery. Only the same signed-in SageOx user can reopen it before it expires.
Control what flows
- For the whole team. A team owner turns the ChatGPT plugin on or off in the team's Settings → Feature Preview. Off stops that team's updates for everyone on it.
- On / Off. In Settings → Connections → ChatGPT, turn the connection's team updates off and on. Turning it back on is instant.
- Team updates. On the same page, pick which teams may send enabled updates to ChatGPT. Updates arrive only from selected teams that also have the plugin Preview on.
- Company knowledge. Select exactly one team for ChatGPT's cited
searchandfetchtools. Those tools never fan out to other teams you can access. - Off the record. Say "off the record" in ChatGPT. Nothing after that is captured or shared.
- Disconnect. Disconnecting ChatGPT removes its team updates and settings along with the connection.
Explore what's next
- Getting the most out of SageOx: how to prompt your AI coworker well
- MCP overview: what tools are available and how sign-in works

