ChatGPT Space for Codex users: setup, sharing and context
This research library uses AI-assisted source research and drafting. Linked sources support product claims; analysis and proposed exercises are our interpretation. Unless an article documents a test and its results, do not read it as a hands-on review or an independently verified benchmark.
ChatGPT Space is the new home for pages, files and shared work in ChatGPT, and it replaces what used to be called Library. OpenAI announced it at DevDay on 29 September 2026 as a place where teammates, ChatGPT, Codex and your dot build on the same knowledge, per the ChatGPT Space launch page. It is available now on Pro, Business and Enterprise on desktop and web.
For a Codex team, the useful question is simple: which context belongs in the repository, and which belongs in a space? This guide covers setup, access and one working split.
ChatGPT Space vs Library: what changed?
The workspace admin docs describe it as "ChatGPT Space (formerly Library)". Some admin settings still use the old name, such as the "Share Library files and folders" permission.
| Area | What ChatGPT Space gives you |
|---|---|
| Name | Space, formerly Library |
| Content | Pages, spaces, sites, images and uploaded files |
| Grouping | Spaces around a topic or team, plus child pages |
| Editing | Real-time co-editing, comments and revisions by ChatGPT |
| Agents | Tag ChatGPT, Codex or your dot on a page |
| Sharing | View, Comment or Edit, for people or Teams |
| Admin naming | Some settings and Compliance API docs still say Library |
The product page also lists team spaces and a to-do list that pulls from Slack, email and calendar. Collaborative slides and spreadsheets are announced as coming soon.
Who can use ChatGPT Space today?
Space is part of Pro, Business and Enterprise. On desktop and web you can create and edit. On mobile you can find, read and share, and OpenAI says mobile creation and editing is coming soon.
The Meetings help article says Business admins must enable Space and Meetings before members can use them together. Enterprise admins manage sharing at the workspace and role level.
How do you set up a space for one repository?
Start with one repository and one team. A space per repo keeps inherited access easy to reason about.
- In Space, open All and select New, then Space. Name it after the repository or service.
- Invite the people who work on it, or invite a Team, before you create pages.
- Select New page and create an overview page. Add links to the repo, the issue board and the design files.
- Create child pages for architecture decisions, open questions and release notes.
- Open the sharing controls, check each person's access level, and confirm that one collaborator can open the page as expected.
The getting started guide suggests asking ChatGPT to turn rough notes into a clear draft that keeps facts and source links. That is a good first test. Paste the notes from your last planning meeting and ask for a draft with open questions listed at the end.
Where does Codex fit next to Space?
Codex already reads repository context. Run /init in the Codex CLI and it creates an AGENTS.md file with instructions for Codex. That file is reviewed in pull requests and versioned with the code, so it stays the right home for build commands, test rules and folder boundaries.
A space holds the context that does not live in code. That includes product decisions, the reasons behind an architecture choice, and questions waiting on another team. Scheduled tasks that a Codex chat creates can use connected tools, and Team Tasks can read shared instructions from a team's designated space.
A practical split looks like this:
AGENTS.md: commands, conventions, what Codex may and may not touch.- Space overview page: goals, owners, links to the repo and board.
- Decision pages: one page per decision, with date, status and source link.
- Open questions page: items waiting on people, with an owner each.
The launch page says you can tag Codex on a page. The help docs published today show @ChatGPT and @dot mentions, and they do not yet say what a Codex mention does from a page. Test it on a throwaway page before you build a workflow around it.
What should you check before sharing a page?
Three rules from the collaboration docs matter most for engineering teams.
First, sharing a page grants access to its child pages. A space shares all its pages. If you put a sensitive incident note under a widely shared overview page, it inherits that audience.
Second, removing someone's direct invite does not remove access they inherit from a parent page or space. Fix access at the parent.
Third, linked files keep their own permissions, but copied or summarized content does not. If ChatGPT summarizes a private Google Drive file onto a page, everyone with page access can read that summary. Sharing a page does not share your private chats or saved memory.
The agents docs also note that collaborators may use different agents, connected tools or instructions on the same page. Agree who changes which section. For small fixes, select the text, use Ask for change, and review the proposed wording before you accept it.
A first week with Space and Codex
Pick one active feature. Put its decisions and open questions in a space, keep its commands in AGENTS.md, and let people and agents work from both. At the end of the week, check two things. Did anyone ask a question the space already answered? Did an agent edit contradict a recorded decision?
If you want your team to practise this split on your own codebase, our Codex training covers repository context, review and shared team rules.
Next step: create one space for your busiest repository today and move its three most-asked questions onto an overview page.