AI Tools & Technology

ChatGPT Space Comes to Plus With Pages That Can Update Themselves

British newspaper cartoon showing a cheerful ChatGPT robot presenting self-updating pages on a large display to a curious man, with refresh symbols beside articles and charts.
ChatGPT's new Space feature promises pages that can keep themselves updated, offering a different way to organise and revisit information.

OpenAI is expanding ChatGPT Space to Plus subscribers, giving more people a place to create interactive pages and presentations inside ChatGPT. Some pages can update from connected apps rather than remaining static documents. The change is more than a new place to save files: it moves AI-assisted work towards material that can be viewed and edited over time, sometimes with other people.

The company’s 20 November release notes say Space is rolling out globally to eligible Plus users aged 18 and older, with access governed by subscription and account requirements. It replaces the older Library entry in the sidebar for those receiving the change. A gradual rollout means some subscribers may not see it immediately, and a feature described in one plan should not be assumed to be available to everyone.

What a ChatGPT Space page does differently

A traditional chatbot returns text that a person may copy into a document. Space is designed to keep the result as a page or presentation that can be revised, organised and, where supported, connected to information from apps. OpenAI gives examples including a project plan that reflects changes in a connected service and an interactive study guide. The value is continuity: useful work can remain available without beginning every revision from scratch.

The distinction also changes what people need to check. A static document may be wrong when first created, but it does not normally change by itself. A page linked to an external source can acquire new information after it has been reviewed. That may be helpful for a regularly updated plan, but it means readers should know whether they are looking at a fixed version or a live result.

A good use case has clear boundaries. For a personal task list, the risk of an imperfect update may be low. For a budget, legal schedule or client-facing report, a changed data source can affect important decisions. Automation should not erase the distinction between an updated draft and something a person has approved for use.

Sharing is more complicated than copying a link

OpenAI’s Space sharing and data guidance explains that access is permission-based and recipients need an eligible account. The announcement says public links are not available for these pages. That differs from publishing a conventional webpage that anyone can open without signing in.

The requirement may be useful for collaborative work where material should not be available to the public. It also means sharing a page does not automatically solve external publishing, distribution or accessibility needs. An organisation that wants customers to read a public report may still need an ordinary website or exported document.

Shared material can also contain information drawn from earlier conversations or connected sources. A person who can read a shared page may see material that the creator did not intend to expose. The correct question is not merely whether the page has a share button. It is what information it currently contains, what it might contain after an update and who is allowed to view it.

What app-linked updates change

A page that updates from another service can reduce repetitive copying. For example, a team planning an event might want a schedule that reflects a connected calendar or a task list that changes when work is completed. A page can be useful as a common view of information that otherwise lives in separate places.

However, access to a connected app should be treated as a permission decision. A presentation may need to show a few agreed milestones, not the contents of an entire private calendar. Teams should check which data are being used and whether the connection can be removed when it is no longer necessary.

LiveAIWire has previously examined AI agents completing longer work projects. Space is a different part of the workflow: it concerns the ongoing form in which work is kept and shared. An interactive page does not itself prove that the information within it has been checked.

Collaboration still needs ownership

When more than one person can edit a page, the team needs agreement about who is responsible for the result. A shared draft may be appropriate for brainstorming, while a policy or client document requires a clearer approval process. People should be able to recognise suggestions, corrections and final decisions.

If a page is updated automatically, the owner should also know when to review it. A stale connection may stop bringing in expected information, or an upstream service may change how a field is interpreted. An apparently current page can therefore still be incomplete. A visible update date is useful but not the same as verified accuracy.

Privacy considerations become more important when information flows between accounts. OpenAI’s guidance covers sharing controls and how data and personalisation features interact with shared content. Users should check the current settings and understand what the invited collaborators can see rather than relying on assumptions based on ordinary chat privacy.

LiveAIWire’s article on meeting-note sharing permissions raises a related concern. A convenient summary can expose sensitive details when the audience is wider than the people who supplied the original material. The same principle applies to interactive pages.

The opportunity for ordinary users

The strongest initial uses are projects in which the information changes gradually and can be checked easily. A study plan, holiday itinerary, club schedule or personal project can benefit from a page that remains editable. The goal should be to make information easier to maintain rather than to add a layer of automation that people struggle to understand.

Users should begin with information they are comfortable keeping in the workspace, examine a page before sharing it and test how linked updates behave. If a page is intended for someone else, check it while viewing with that person’s permissions where possible. Access and presentation can differ between the creator and an invited collaborator.

The rollout makes the idea of an AI-generated document less temporary. Instead of a response that disappears into chat history, a page can become an ongoing shared object. The important conditions are the same as for any useful collaborative tool: reliable information, clear ownership and permissions that match what people actually want to share.

About the Author

Stuart Kerr is Technology Correspondent at LiveAIWire, covering artificial intelligence, cybersecurity and the social impact of emerging technology. LiveAIWire is an independent, human-led technology publication using AI-assisted research, editorial production and original AI-assisted editorial illustrations under his direction.