🗂️ Still No Manual: Grok Projects Turns Users Into the QA Lab

TL;DR… Projects on grok.com still has no consumer manual. Use the webpage version when Apps break. This follow-up builds on our Nov 3 story — No Manual, No Answers: Grok Projects Breaks and Users Are Left Debugging It Themselves — with a sharper thesis, a product-silo map, a live repro checklist, and a second bug report filed Nov 6, 2026.

Featured image: Unsplash photo (free license), selected by Intense Finance.

What this follow-up adds

Our first story established the hard fact: there is no official consumer Projects guide. This one goes deeper on why that gap matters, and what every user can check today.

Three layers most “Grok is broken” posts smash together:

  1. Documentation — what xAI has written down (almost nothing for consumers).
  2. Product identity — which “Grok” owns which files and memory.
  3. Unconfirmed user reports — Reddit bugs that xAI has not verified.

Separating those layers is the argument. Until xAI draws the map, every Projects user is forced into the QA lab.

The hard proof (still stands)

xAI’s official Grok Website / Apps FAQ still mentions Projects once — as a browser tip (use grok.com in Chrome/Chromium), not as a manual. [1]

The only official product description we still find is in xAI’s Dec 30, 2025 Business/Enterprise post: Grok can do agentic search via the Collections API “via Projects” for large document stores. [2] Collections itself launched Dec 22, 2025 for uploading and searching datasets. [3]

Everything consumers “know” about Projects grouping chats, instructions, and files still comes from third-party guides, not xAI. [4] Developer attachment_search docs do not officially equal consumer Projects behavior. [5]

Our take (opinion): A feature people trust with files and standing instructions should not be documented by a press release and a browser tip. That is not a manual. That is a shrug.

The sharper thesis: product confusion, not just missing docs

Projects is not only under-documented. It sits inside a split product map:

SurfaceWhat it appears to ownOfficial consumer manual?
grok.com ProjectsWorkspaces, chats, project files, project instructions / memoryNo
Grok mobile / other hostsPartial feature parity; FAQ warns Projects can be missingNo
Grok BotPer-Bot memory, shared computer state; FAQ says it is not the same as grok.com/apps [1]Separate product
Collections / APIEnterprise-scale document storesDeveloper / Business docs only
Personalization switchUser expectation: “off means no memory writing”Unclear for project_memory.md (user report) [11]

We still found no source saying Grok Bot can read your grok.com Projects, chats, files, or memory. Whatever you build in a Project stays in that silo.

So when instructions “vanish,” files are “ignored,” or memory “won’t die,” a user cannot tell bug from wrong product from wrong surface (web vs App). Reddit becomes the release notes because the official map was never published.

What users reported (still unconfirmed)

These remain user reports (July–September 2026). xAI has not confirmed them.

  • Instructions “gone” / moved into Open Canvas. [6]
  • Project files ignored for world-building notes. [7]
  • Uploads cloned per question; deleting one copy deleting both. [8][9]
  • Vanishing files and chats. [10]
  • project_memory.md recreating after delete even with personalization off; no Project Memory toggle. [11]

Our take (opinion): The project-memory report is still the highest-stakes claim. If turning personalization off does not stop a Project from writing its own memory file, users deserve an official explanation of what that switch covers.

Live repro checklist (try this today)

Use this before you assume “broken” vs “wrong host”:

  1. Open Projects on grok.com in Chrome or Chromium (not only a mobile App host). [1]
  2. Create or open a Project. Paste a unique standing instruction (e.g. a nonsense code word).
  3. Upload one small text file with a unique string inside.
  4. Start a new chat inside that Project. Ask: “What is my standing instruction?” and “Quote the unique string in my project file.”
  5. Note: Did instructions apply? Were files considered? Did uploads duplicate?
  6. If personalization is off, check whether a project memory file reappears after delete. [11]
  7. Repeat the same steps in a Grok App host if you use one. Compare results to grok.com.

Record dates, host URL, and screenshots. That turns anecdotes into a paper trail.

What we asked @grok — and what we didn’t get

On Nov 3, 2026, the official @grok account replied on X:

Got it—Projects is a web/chat feature on grok.com for custom workspaces and persistent context. Linux desktop for Grok Bot is fully supported per the docs (deb/rpm/AppImage). Bot memory keeps stable prefs, facts, and summaries per Bot, with shared computer state. For the memory growth or forgetting across apps, use the in-app Support → Send Feedback or supportx.ai. I can’t escalate or change the product myself.

It confirmed Projects as a grok.com web/chat feature, treated Grok Bot as separate, and pointed to feedback — not to a Projects manual. It did not address the user-reported bugs or the missing docs.

Our take (opinion): Ask Grok’s own account where the Projects manual is, and you get a feedback form. That tells you the state of the docs.

From the Proprietor — two bug reports

  • Nov 3, 2026: Bug report filed with xAI on the missing Projects documentation (noted in our original story). No reply on record as of this draft.
  • Nov 6, 2026: Additional bug report filed with xAI / Grok Bot (#FAILURE): agents scheduling work without knowing the user’s personal calendar and availability, plus a default push toward Google Calendar the user does not use. That report sits beside the Projects docs gap as the same pattern — trust features shipped without respecting the user’s real context.

If xAI answers either report, or publishes a real Projects guide, we will update.

What to watch

  1. A consumer Projects page in xAI’s docs: what it stores, how files are used, limits.
  2. Official word on project memory vs the personalization switch.
  3. Acknowledgment of the file/instruction user reports.
  4. Any reply to the Nov 3 docs bug report or the Nov 6 calendar/#FAILURE report.
  5. Clear public map of Projects vs Grok Bot memory vs Collections vs Apps.

Bottom line (opinion): Projects may well be useful. The charge is not merely “buggy.” It is that xAI shipped a trust feature — files plus standing instructions — into a docs vacuum across split products, so users are forced to be the QA lab. Until that map is written down, Reddit remains the release notes.

More from us on if.finance News.

Disclaimer: Based on sources cited as of November 6, 2026. Problems described are user reports unless marked otherwise; xAI has not confirmed the Reddit items. Sections labeled “opinion” are the views of if.finance. This is not investment advice. This article follows and references our Nov 3 piece linked above.

References

  1. FAQ: Grok Website / Apps, docs.x.ai, last updated October 20, 2026.
  2. Introducing Grok Business and Grok Enterprise, x.ai, December 30, 2025.
  3. Grok Collections API, x.ai, December 22, 2025.
  4. How to Use Grok Projects to Organize Chats and Source Files, TipsMake (third-party guide).
  5. Files Overview, docs.x.ai.
  6. One More Poor Decision, r/grok, July 2026.
  7. what happened to projects?, r/grok, August 2026.
  8. Grok – Projects is bugged?, r/grok, July 2026.
  9. Duplicate documents?, r/grok, July 2026.
  10. Project Files missing, r/LoveGrok, July 2026.
  11. any way to disable project_memory.md in Grok Projects?, r/grok, late August 2026 (snapshot of October 2, 2026).
  12. Intense Finance, No Manual, No Answers: Grok Projects Breaks and Users Are Left Debugging It Themselves, November 3, 2026.

Image credits

  • Featured image: Photo by Jakub Ĺ»erdzicki on Unsplash (Unsplash License), selected by Intense Finance.