TL;DR: ChatGPT Space gives your AI work a place to live: editable Pages, files and shared work you can return to and develop with other people. You can bring ChatGPT or your Dot into a Page, add interactive elements, and use Sites for a hosted website or app. The opportunity is to turn useful conversations into work you keep improving. Below: how it works, five practical starting points, five ambitious builds, and the details that make the difference.

Your best ChatGPT answer shouldn't disappear into a conversation you never open again.

You work through an idea. Get a useful plan. Generate a draft.

Then next week arrives, and you're hunting through chats trying to remember which version mattered.

ChatGPT Space gives that work a home.

OpenAI included Space in its September 29 DevDay announcements, alongside Dots. My take: the interesting shift is that the work can become something you organize, collaborate on and keep developing.

What ChatGPT Space actually is

Space brings together Pages, saved files, images, spreadsheets, presentations and Sites. A Page is a document you can edit directly or work on with ChatGPT. Individual spaces group related Pages around a topic or team.

That could mean a product launch, a course you're studying, a trip, or your next creative project.

Two naming details help: your workspace is the personal or organization environment you're signed into; a space organizes related work within it. OpenAI's admin documentation also calls Space the successor to Library.

How Space relates to Dots and Sites

Here's a practical way to divide the jobs:

Tool	Its job	Example
Space	Keep the material and shared work together	A launch brief and its supporting research
Dot	Take on ongoing responsibilities	Research changes and follow up on assigned work
Site	Deliver a hosted web experience	A demo, calculator, dashboard or browser game

You can mention your Dot directly in a Page. Dots can continue work between conversations, including cloud work while your computer is off. Sites gives you a separate workflow for building and hosting web experiences.

For example, imagine launching a workshop:

• Space: Keep the audience research, curriculum and decisions together.
• Dot: Give it responsibility for researching unanswered questions.
• Site: Build the workshop's website from the approved brief.

That's a workflow you can set up. Saving a Page doesn't automatically create a Dot assignment, a running schedule or a published Site.

How to get started

You need an account with Space enabled.

1. Open Space in ChatGPT.
2. For a group of related Pages, use All → New → Space and name it.
3. Choose New page. Add notes, files or source links.
4. Open ChatGPT alongside the Page and explain the outcome you want.
5. Review and edit the result, then use the sharing controls if you want collaborators.

You can also ask ChatGPT to turn an existing conversation into a Page. Connected sources such as Google Drive require the appropriate app connection and file access. Getting started

Try this as your first request:

Turn these notes into a project brief with a clear goal, current decisions, next actions, source links and unresolved questions. Mark missing information instead of guessing.

Then ask for one focused improvement:

Rewrite the opening for someone seeing this project for the first time. Keep the facts and decisions intact.

Five useful ways to try it

These are starter recipes you can adapt.

1. Build a learning headquarters

Pick something you actually want to understand. Add a few good articles, your notes and a specific learning goal.

Create a learning plan from these sources. Explain the essential concepts, make a glossary and give me practice questions. Separate what the sources establish from your own explanation. Start with a short exercise that exposes what I don't understand.

The useful part: you have a place to capture corrections and build on them.

2. Create a content studio

Put your audience, source material, writing samples and ideas in one place.

Develop this idea into a Reddit post, a LinkedIn post and a 60-second video script. Give each format its own opening. Preserve the evidence and distinguish opinion from fact. Put unsupported claims in a questions list.

Then save the angle you chose and why. Your next draft has a better starting point.

3. Plan a trip people can actually agree on

Bring dates, budget, must-haves and saved options.

Compare these options against our priorities. Draft an itinerary with travel time, a daily budget and a rainy-day alternative. Flag prices or opening hours that need checking. Show which decisions we still need to make.

Share the planning Page with your travel companions and use comments to resolve the tradeoffs.

4. Build a launch room

Collect customer insights, product notes and positioning ideas.

Use these materials to draft the launch story, audience, key objections and a checklist. Separate confirmed commitments from proposals. Suggest owners only where the source material supports them.

Add research and creative work as related Pages as the project grows.

5. Keep a decision notebook

Use it for software selection, hiring priorities or a business idea.

Compare these options using my constraints. Recommend one, explain the tradeoffs, record the assumptions and identify what evidence would change the recommendation.

Future you gets to see the reasoning behind a choice.

Five wild things to build

These are ambitious project ideas using Space with available Dots, Sites and visualizations. They require setup and iteration.

1. A one-person launch studio

Give a single idea a full development environment: customer evidence, an offer, a demo, a launch narrative and a website.

Help me develop this idea into a small launch. Build Pages for customer evidence, the offer, experiments and launch copy. Give my Dot a scoped research assignment. Use Sites to build a demo website from the approved brief. Show me the work at each stage.

The ambition: make the leap from “interesting idea” to something another person can experience.

2. A personal research observatory

Choose a question you want to follow for months: an emerging technology, a scientific field or a changing market.

Create an evidence notebook for this question. Track each claim, its source, date, contradictions and open questions. Help me set up a weekly review that adds material changes and explains whether they affect our conclusions. Confirm the saved schedule and its time zone.

You're designing a record of how your understanding changes.

For fixed recurring work, Dots requires a saved schedule. Supported event monitoring also needs an explicit assignment; connecting a service alone doesn't start it. Tasks and memory

3. A business wind tunnel

Create a place to test an idea before committing real resources. Model pricing, customer demand, costs and different operating choices.

Build an interactive model from these assumptions. Let me adjust price, customer volume and costs. Show what breaks first under pessimistic scenarios. Label simulated results clearly and create a Page explaining the assumptions we should test with real customers.

Use a Page visualization for a compact experiment, or Sites for a fuller tool. The value is seeing which assumptions matter.

4. An entire fictional universe

Build the world bible, geography, factions, characters, timelines and visual style. Then make something playable.

Help me create an original fictional universe. Organize its canon into related Pages, generate character and location concepts, and flag continuity conflicts. Use Sites to prototype a branching browser adventure based on the approved canon.

A shared world you and collaborators can keep expanding could become a game, a story series or a creative playground.

5. A personal university built around your goals

Design a curriculum that ends with work you can show.

Use my goals and these sources to design a course with lessons, practice, assessments and a capstone project. Keep my feedback and revisions in Space. Prototype a learning portal in Sites and specify how progress should be saved.

Imagine a course on storytelling where each week improves your actual screenplay, or a marketing course built around your real launch.

Pro tips that make the work better

• Name the outcome. “Prepare a launch decision” gives better direction than “organize my stuff.”
• Start with a small source set. A few relevant documents beat a pile of unrelated uploads.
• Separate evidence, decisions and drafts. Make it easy to tell what is known, what is agreed and what is still being explored.
• Tell the agent where the answer belongs. Ask for a chat response, a Page edit or a separate deliverable.
• Protect settled details. Tell it to preserve approved names, dates, quotations and commitments.
• Ask for changes, not another full report. “What changed, why does it matter, and what should we reconsider?”
• Define success before delegating. Specify the output, sources, review points and when you need an update.
• Test the result. Click the calculator, open the source and inspect the saved output.

Things people can easily miss

Pages can do more than hold text. The slash menu includes image generation and interactive visualizations. Prompt blocks let readers reuse a request to start a chat. You can also reference existing files, Pages and chats.

You can bring the agent to a specific passage. Select text and use Ask for change, or address ChatGPT or dot inline or in a comment. Be explicit about the section and requested change.

“Keep Updated” isn't available at launch. Writing “update this every morning” in a Page doesn't establish a working schedule. Request recurring work in chat, inspect the saved task, and verify an actual run and resulting update.

Sharing can extend to nested work. Space access applies to its Pages; sharing a Page also includes its child Pages. Removing a direct invitation may leave access inherited from a parent. Choose view, comment or edit access from the options your account offers.

Private sources and shared summaries are different. A linked source keeps its own permissions. Information copied or summarized into the Page becomes visible to that Page's readers. Sharing a Page doesn't expose your entire private chat history or saved memory. Sharing details

A shared Page doesn't give everyone the same tools. Collaborators may have different agents, connections and instructions. Agree on who changes what.

A Site has its own publishing and access settings. You can save a Site version before deploying it. Decide its audience separately; a Page edit isn't automatic website publication.

A note on access

Check the features enabled in your account and workspace. Dots has a separate gradual rollout and eligibility rules; Sites has its own plan limits. Having Space doesn't establish access to every feature described here.

Try this today

Choose one project you've already been putting off.

Create one Page. Add three useful sources. Ask for one concrete result.

Then improve it once.

The result could be a better decision, a draft worth publishing or the first version of something people can use.

Save this for the prompts, or send it to the person you'd want to build with.