diff --git a/apps/docs/company-brain/use-cases/support-escalation.mdx b/apps/docs/company-brain/use-cases/support-escalation.mdx index de08f485..4f4e825b 100644 --- a/apps/docs/company-brain/use-cases/support-escalation.mdx +++ b/apps/docs/company-brain/use-cases/support-escalation.mdx @@ -14,7 +14,7 @@ A customer files a ticket through Plain. It lands in `#support`, gets triaged wi ## What happens - + New conversation: rewriteQuery param not working
**Jordan Alvarez** (acme-corp.io) sent a **new message**. @@ -34,12 +34,12 @@ A customer files a ticket through Plain. It lands in `#support`, gets triaged wi
- + Agent thread started
Reproducing against the v3 search test suite now. - + Fixed — `rewriteQuery` was getting skipped by the new cost short-circuit whenever a query was already cached. Pushed on #2312.

diff --git a/apps/docs/connectors/overview.mdx b/apps/docs/connectors/overview.mdx index 7e8a9b70..5b40ef2b 100644 --- a/apps/docs/connectors/overview.mdx +++ b/apps/docs/connectors/overview.mdx @@ -10,7 +10,7 @@ Connect external platforms to automatically sync documents into supermemory. Sup ## Supported Connectors - + **Google Docs, Slides, Sheets** Real-time sync via webhooks. Supports shared drives, nested folders, and collaborative documents. @@ -22,26 +22,26 @@ Connect external platforms to automatically sync documents into supermemory. Sup Real-time sync via Pub/Sub webhooks. Syncs threads with full conversation history and metadata. - + **Pages, Databases, Blocks** Instant sync of workspace content. Handles rich formatting, embeds, and database properties. - + **Word, Excel, PowerPoint** Scheduled sync every 4 hours. Supports personal and business accounts with file versioning. - + **GitHub Repositories** Real-time incremental sync via webhooks. Supports documentation files in repositories. - + **Meeting notes and transcripts** Syncs AI meeting notes, summaries, attendees, and transcripts from your Granola workspace. diff --git a/apps/docs/docs.json b/apps/docs/docs.json index e72c74df..63c0af6b 100644 --- a/apps/docs/docs.json +++ b/apps/docs/docs.json @@ -30,7 +30,7 @@ "footer": { "socials": { "github": "https://github.com/supermemoryai", - "linkedin": "https://linkedin.com/company/supermemoryai", + "linkedin": "https://linkedin.com/company/supermemory", "x": "https://x.com/supermemory" } }, diff --git a/apps/docs/images/cartesia.svg b/apps/docs/images/cartesia.svg new file mode 100644 index 00000000..7f83ca30 --- /dev/null +++ b/apps/docs/images/cartesia.svg @@ -0,0 +1,4 @@ + + + + diff --git a/apps/docs/index.mdx b/apps/docs/index.mdx index 647f13e4..bdc43c1b 100644 --- a/apps/docs/index.mdx +++ b/apps/docs/index.mdx @@ -40,19 +40,19 @@ export const HeroCard = ({ imageUrl, title, description, href }) => {

Architecture Quickstart Set up your company brain @@ -62,25 +62,25 @@ export const HeroCard = ({ imageUrl, title, description, href }) => {
Claude Code + Supermemory @@ -141,7 +141,7 @@ Per-repo overrides in `.claude/.supermemory-claude/config.json`. Run `/supermemo ## Next Steps - + Source code, issues, and detailed README. diff --git a/apps/docs/integrations/codex.mdx b/apps/docs/integrations/codex.mdx index 6d610fa6..00896015 100644 --- a/apps/docs/integrations/codex.mdx +++ b/apps/docs/integrations/codex.mdx @@ -166,7 +166,7 @@ tail -f ~/.codex-supermemory.log ## Next Steps - + Source code, issues, and detailed README. diff --git a/apps/docs/integrations/hermes.mdx b/apps/docs/integrations/hermes.mdx index 1b0f10f8..d45811cb 100644 --- a/apps/docs/integrations/hermes.mdx +++ b/apps/docs/integrations/hermes.mdx @@ -141,7 +141,7 @@ If you run your own supermemory API, set **`base_url`** (and any other host-spec ## Next Steps - + Full config table, env vars, and multi-container details. diff --git a/apps/docs/integrations/n8n.mdx b/apps/docs/integrations/n8n.mdx index 9fbf88e3..7376a5af 100644 --- a/apps/docs/integrations/n8n.mdx +++ b/apps/docs/integrations/n8n.mdx @@ -12,7 +12,7 @@ Connect Supermemory to your n8n workflows to build intelligent automation workfl ### Prerequisites - n8n instance (self-hosted or cloud) -- Supermemory API key ([get one here](https://console.supermemory.com/settings)) +- Supermemory API key ([get one here](https://console.supermemory.ai/settings)) - Basic understanding of n8n workflows ### Setting Up the HTTP Request Node @@ -90,4 +90,4 @@ If you want to process attachments: 3. Check the execution to ensure the email was captured 4. Verify in Supermemory that the email appears in search results -Refer to the API Reference tab to learn more about other supermemory API endpoints. \ No newline at end of file +Refer to the API Reference tab to learn more about other supermemory API endpoints. diff --git a/apps/docs/integrations/openclaw.mdx b/apps/docs/integrations/openclaw.mdx index 3c23c1c5..5704d3d4 100644 --- a/apps/docs/integrations/openclaw.mdx +++ b/apps/docs/integrations/openclaw.mdx @@ -286,7 +286,7 @@ openclaw supermemory wipe # Delete all memories (requires confirma ## Next Steps - + Source code, issues, and detailed README. diff --git a/apps/docs/integrations/opencode.mdx b/apps/docs/integrations/opencode.mdx index 90a896b1..3cce46d7 100644 --- a/apps/docs/integrations/opencode.mdx +++ b/apps/docs/integrations/opencode.mdx @@ -148,7 +148,7 @@ tail -f ~/.opencode-supermemory.log ## Next Steps - + Source code, issues, and detailed README. diff --git a/apps/docs/integrations/pipecat.mdx b/apps/docs/integrations/pipecat.mdx index c05af722..1637ce44 100644 --- a/apps/docs/integrations/pipecat.mdx +++ b/apps/docs/integrations/pipecat.mdx @@ -236,7 +236,7 @@ For a complete example using Gemini Live speech-to-speech with Supermemory, chec Full working example with Gemini Live, including frontend and backend code. diff --git a/apps/docs/overview/comparison.mdx b/apps/docs/overview/comparison.mdx index 342f11f0..669887d2 100644 --- a/apps/docs/overview/comparison.mdx +++ b/apps/docs/overview/comparison.mdx @@ -53,7 +53,7 @@ This page is intentionally **not** a vendor scorecard. We know things change and If you are migrating from a specific tool, use the [migration guides](/migration/from-mem0), that is where we name names and map APIs. -## vs Rolling your own (vector DB + embeddings + glue) +

vs Rolling your own (vector DB + embeddings + glue)

**What this path is:** Pinecone/Weaviate/pgvector + an embedding model + chunking scripts + a prompt that says “here is relevant context.” and running it through a text model, extracting facts. @@ -74,7 +74,7 @@ If you are migrating from a specific tool, use the [migration guides](/migration **Supermemory instead:** one engine that derives **memories** using our custom model, a **temporal vector-graph engine**, and **profiles**, with hybrid retrieval and isolation primitives built in. You keep the option to [self-host](/self-hosting/overview) when you want the stack on your metal. -## vs “Memory layers” that are thin wrappers +

vs “Memory layers” that are thin wrappers

**What this path is:** an API that stores chat turns or summaries in a vector store, sometimes with a light extract-facts prompt. Marketed as memory; architected as RAG with better branding. @@ -93,7 +93,7 @@ If you are migrating from a specific tool, use the [migration guides](/migration **Supermemory instead:** memory is a first-class data model (documents → derived memories → graph → profiles), not a convenience wrapper. Same store from API, MCP, plugins, and Company Brain, all primitives built in for you to compose for your use case. See [How it works](/concepts/how-it-works) and [Graph memory](/concepts/graph-memory). -## vs Pure RAG / document search products +

vs Pure RAG / document search products

**What this path is:** excellent document ingestion and semantic search over a corpus, wikis, PDFs, tickets. No (or weak) per-user long-horizon memory. @@ -113,7 +113,7 @@ If you are migrating from a specific tool, use the [migration guides](/migration **Supermemory instead:** **both** layers in one engine, SuperRAG for corpus grounding, memory + profiles for people and entities. They share container tags so isolation stays coherent. Deep dive: [Memory vs RAG](/concepts/memory-vs-rag). -## vs Building a full context engine in-house +

vs Building a full context engine in-house

**What this path is:** custom extraction models, graph store, profile assembly, hybrid search, connector fleet, multi-tenant keys, compliance pack. @@ -134,7 +134,7 @@ If you are migrating from a specific tool, use the [migration guides](/migration **Supermemory instead:** that platform as a product, managed cloud or self-hosted binary, so your team ships agents and apps, not a second infrastructure company. Benchmarks and research: [supermemory.ai/research](https://supermemory.ai/research). -## Decision cheat sheet +

Decision cheat sheet

| If your job is… | Prefer | |---|---| @@ -144,7 +144,7 @@ self-hosted binary, so your team ships agents and apps, not a second infrastruct | Full control, data never leaves your network | Supermemory [self-host](/self-hosting/overview) / Enterprise | | Maximum control of every model weight and storage engine | Build in-house (or fork open pieces and accept the ops) | -## Prove it yourself +

Prove it yourself

We would rather you verify than trust a comparison page: @@ -152,7 +152,7 @@ We would rather you verify than trust a comparison page: 2. Reproduce long-horizon results with [MemoryBench](https://supermemory.ai/research) / the MemoryBench docs when you care about evals 3. If you already store memories elsewhere, use a [migration guide](/migration/from-mem0) -## Supermemory is never overkill +

Supermemory is never overkill

In most cases, supermemory will be the _lighter_ choice (not heavier), and it is cheaper too! Because supermemory involves all the blocks while being fully composable, but we also build the infrastructure ourselves (a post-trained model, etc.), it's perfect for everything from internal tools, side projects, and hobby projects to production-grade infrastructure that millions of people rely on. diff --git a/apps/docs/overview/what-is-supermemory.mdx b/apps/docs/overview/what-is-supermemory.mdx index ed5a0b9f..b394dcf5 100644 --- a/apps/docs/overview/what-is-supermemory.mdx +++ b/apps/docs/overview/what-is-supermemory.mdx @@ -30,47 +30,47 @@ It provides all the building blocks — Memory, Retrieval, Profiles, Connectors,
diff --git a/apps/docs/snippets/slack-message.mdx b/apps/docs/snippets/slack-message.mdx index 3af4efb9..b21910f4 100644 --- a/apps/docs/snippets/slack-message.mdx +++ b/apps/docs/snippets/slack-message.mdx @@ -1,9 +1,9 @@ export const DHRAVYA = { name: "Dhravya Shah", - avatar: "/docs/images/company-brain/dhravya-slack-icon.jpg", + avatar: "/images/company-brain/dhravya-slack-icon.jpg", }; -export const BOT_AVATAR = "/docs/images/company-brain/supermemory-slack-icon.png"; +export const BOT_AVATAR = "/images/company-brain/supermemory-slack-icon.png"; export const Mention = ({ children, self = false }) => (
{dmWith?.name @@ -221,8 +221,8 @@ export const SlackMessage = ({ children, }) => { const SELF_NAME = "Dhravya Shah"; - const SELF_AVATAR = "/docs/images/company-brain/dhravya-slack-icon.jpg"; - const BOT_AVATAR = "/docs/images/company-brain/supermemory-slack-icon.png"; + const SELF_AVATAR = "/images/company-brain/dhravya-slack-icon.jpg"; + const BOT_AVATAR = "/images/company-brain/supermemory-slack-icon.png"; const resolvedName = bot ? "supermemory" : self ? SELF_NAME : name || SELF_NAME; const resolvedAvatar = bot ? BOT_AVATAR : self ? SELF_AVATAR : avatar; diff --git a/apps/docs/supermemory-mcp/mcp.mdx b/apps/docs/supermemory-mcp/mcp.mdx index d1bf071b..867e8109 100644 --- a/apps/docs/supermemory-mcp/mcp.mdx +++ b/apps/docs/supermemory-mcp/mcp.mdx @@ -145,7 +145,7 @@ In Cursor and Claude Code you can often invoke this with **`/context`**, which g Client configs, OAuth, and project scoping. - + Open-source implementation.