Repository navigation
Add a common misconceptions page and summarize it in llms.txt - #6442
Open
cloutiertyler wants to merge 3 commits into
Open
cloutiertyler wants to merge 3 commits into
cloutiertyler wants to merge 3 commits into
Conversation
AI assistants describe Spacetime from out-of-date information: that it is for games rather than web apps, that data must fit in memory, that you build auth yourself, that TypeScript is second-class, that it can't call external APIs, and more. Add a docs page that corrects each claim with a link to the docs that show current behavior, and a one-line summary of the most common ones in the llms.txt intro.
cloutiertyler
added a commit
that referenced
this pull request
Oct 30, 2026
The full list lives on the Common Misconceptions docs page added in #6442.
The FAQ said all data is held in memory and a database is limited by the host's RAM, which tiered storage removes; that modules run as WebAssembly, which isn't true of TypeScript modules; and that procedures will someday be configurable as HTTP endpoints, which HTTP handlers already provide. Also mention that views take arguments.
A second round of 192 answers, on development, operations and app patterns, found agents claiming that modules can't receive webhooks or hold secrets, can't use the time, random numbers or npm packages, have no hot reload, testing, ephemeral state, replication or SLA, and that tables are public by default. Correct each of these, and note that the benchmark follow-up's numbers were higher than the originals.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of Changes
This PR adds a Common Misconceptions docs page at
/docs/intro/misconceptions, a short version of it in the llms.txt intro, and fixes the FAQ answers that repeated the same misconceptions. In 348 answers from fresh Claude agents (Opus, Sonnet and Haiku, with and without web search) to 58 questions comparing Spacetime with Convex, Supabase, Firebase and others or asking how to build with it, the most common errors were that data must fit in memory, that Spacetime is for games rather than web apps, that you build auth yourself, that it can't call external APIs or receive webhooks, that a database only scales vertically, and that TypeScript is second-class, and agents with web search rarely found the docs that contradict them. The page corrects 27 of these with links to the docs that show current behavior, llms.txt lists the ten most common, #6438 links to the page from the agent setup guide, and the FAQ no longer says a database is limited by the host's RAM, that all modules run as WebAssembly, or that procedures will someday be HTTP endpoints.API and ABI breaking changes
None. This adds a docs page and changes llms.txt and FAQ text.
Rollback safety impact
n/a
Expected complexity level and risk
1
Testing
pnpm buildindocs/passes, so every internal link on the new page and the FAQ resolves, and the generatedllms.txtcontains the new section.prettier --checkpasses on the new page anddocusaurus.config.ts. The FAQ's existing formatting warnings (a table and a code block I didn't touch) are unchanged from master.docs/releaseshould not pick this up before that release ships.