docs: fix drift in Cursor IDE

[jack-arturo]

Automated docs-accuracy audit of docs/platforms/cursor. Last reviewed 2026-07-10 (0 issues). The generated rule template templates/cursor/automem.mdc.template has since moved to the two-phase-recall / three-trigger policy, and this page still described the older three-phase model.

Claim	Current state	Fix	Evidence
"Three-Phase Memory Pattern — the rule file prescribes a three-phase memory workflow"	Template prescribes a two-phase session-start recall plus storage on three mid-conversation triggers	Heading and intro corrected; Phase 1 now states the standardized recall shapes (preferences limit 20 / sort: "updated_desc"; task context last 90 days, limit 30)	automem.mdc.template#L29
"Phase 3: Conversation End — Summary … Summarize when: multiple files were modified …"	Storage discipline: "Never store … session summaries, progress reports, confirmations, speculative context"	Section replaced with an explicit no-end-of-conversation-summary note	automem.mdc.template#L82
Storage triggers table: Pattern 0.7, Preference 0.6–0.8, Insight 0.8	Template: Pattern 0.8, Preference 0.9 (correction), Insight 0.75 (bug fix)	Values corrected to 0.8 / 0.9 / 0.75	#L98, #L100, #L127
Tagging Conventions, project block: cursor platform tag + YYYY-MM current month	Template: "no lang/ prefixes, platform tags, or date-stamped tags"; store comment // bare strings; NO platform tag, NO [YYYY-MM]	Replaced with category / bare project slug / language, plus the slug-collision caveat	#L21, #L88
Tagging Conventions, personal block: YYYY-MM current month	Same ban applies to cross-project memories	YYYY-MM entry dropped; t_valid/t_invalid noted for time-bound facts	#L21

Verified against: mcp-automem@2816beb7bb81d87bb8d592e8712fd8b4a7cc4f95
Verified against: automem@8ff266e62e65cb2e81719a765b05f64a2361a127

Draft because several fixes rewrite explanatory prose rather than only values or paths.

Checked and found accurate, left unchanged: the CLI flag table (--name, --dir, --dry-run, --yes/-y, --quiet all parse — src/cli/cursor.ts + src/cli/host-toolkit.ts), the .bak backup behavior, the alwaysApply: true frontmatter, the mcp_<server>_<tool> prefix table, and the 11 authorable / 3 system relation split (automem/config.py defines exactly 14 relationship types).

Questions

• "Auto-summarized by backend (requires OPENAI_API_KEY)" in Content Size Governance. AutoMem's summarizer runs through the classification LLM path, which also accepts OPENAI_BASE_URL-compatible providers, so naming OPENAI_API_KEY as the requirement may be an intentional simplification. Left unchanged.

Unverified

• The one-click deeplink URL scheme cursor://anysphere.cursor-deeplink/mcp/install?... — an Anysphere/Cursor URL scheme, not defined in any AutoMem repo. Left alone.
• "Cursor Settings > General > Rules for AI" menu path — Cursor UI, not verifiable from source.

Follow-ups

None — all proven discrepancies fit inside the 5-fix cap.

---

Generated by Claude Code

[cloudflare-workers-and-pages]

Deploying automem-website with    Cloudflare Pages

Latest commit:	4cef3d4
Status:	✅  Deploy successful!
Preview URL:	https://27346b78.automem-website.pages.dev
Branch Preview URL:	https://docs-audit-platforms-cursor.automem-website.pages.dev

View logs