ChatGPT workflow feedback: Canvas, Projects, Library, and app consistency

Hi everyone,

I want to share product feedback about the current ChatGPT workflow around Canvas, Writing Blocks, Projects, and long-form document work.

First, I want to say that I like ChatGPT overall. The current Thinking model is very strong, and the large context window is extremely useful for serious work. Being able to work with long context and receive long, coherent answers in a single message is one of the most valuable parts of the product. I also like the Projects system, especially the distinction between Standard projects and Project-only projects. That distinction makes it possible to use projects either as folders for organization or as more isolated workspaces with their own context.

However, the loss of persistent Canvas documents is a major regression for long-term workflows.

Writing Blocks are useful for short outputs, quick drafts, and small edits, but they do not replace the old Canvas workflow. Canvas was valuable because it behaved like a persistent document attached to a chat. It was not just an editable block. It was a fixed workspace that stayed with the conversation and could be reopened without scrolling back through a long chat.

The most important Canvas advantages were:

  • Persistent documents attached to a chat
  • Manual editing directly inside the document
  • Version navigation between older and newer document states
  • A cleaner chat, because the assistant did not need to regenerate full document versions repeatedly
  • Better support for long-term work such as prompt management, project planning, writing, coding notes, and structured documentation

The current Writing Block workflow feels weaker for these use cases. In my UI, I can open Writing Blocks in fullscreen, but I cannot rename them or save them as clean persistent documents. They are still tied to individual assistant messages. I also cannot directly export them as .md, .docx, or .pdf. This makes them useful as temporary blocks, but not as a full replacement for Canvas.

This especially affects users who use ChatGPT as a serious productivity tool. For example, I used Canvas-like workflows for prompt management, project notes, structured planning documents, and long-term text work. Without persistent documents, I now have to consider awkward alternatives such as managing Markdown files externally or using Codex to edit files directly. That may technically work, but it adds unnecessary complexity and moves document management out of ChatGPT.

There are also related workflow issues:

  • Feedback is often tied to a specific assistant message, even when the issue is really about the product or interface.
  • Desktop and mobile behavior is inconsistent in some areas, such as how chats inside projects are displayed.
  • Connector/app naming feels inconsistent across platforms.
  • The Library is useful, but it can become messy when many screenshots or automatically named uploads accumulate.
  • Fullscreen Writing Blocks are promising, but without naming, persistence, version history, and export options, they still do not replace Canvas.

I think ChatGPT needs either restored Canvas support in current models or an equivalent persistent document workspace with:

  • Named documents
  • Version history
  • Manual editing
  • Export options such as .md, .docx, and .pdf
  • Easy reopening from the chat or Library
  • Stable behavior across desktop, web, and mobile

Writing Blocks are a useful feature, but they solve a different problem. They are good for short editable outputs. Canvas solved the problem of long-term document work inside ChatGPT.

Is anyone else using ChatGPT for prompt management, project planning, documentation, or long-form writing and missing the old persistent Canvas workflow?

Thanks for sharing this, @lazyfresho.

I can see why this feels like a regression for long-term workflows. Writing Blocks are useful for quick edits, but they don't fully replace what Canvas provided: persistent, editable documents with version history and easy access from a chat.

The feedback around document naming, persistence, exports, cross-platform consistency, and project workflows is valuable. I'll make sure this is forwarded to the team.

-Mark G.