From 434c86e2c32b3c29755dc781f30bac36463a9815 Mon Sep 17 00:00:00 2001 From: Prasanna721 <106952318+Prasanna721@users.noreply.github.com> Date: Tue, 4 Aug 2026 04:55:50 +0000 Subject: [PATCH] fix docs image pipeline (#1411) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Keep docs asset URLs repo-root-relative and pass images as literal MDX children so Mintlify can compile them through OptimizedImage under the /docs mount. Mintlify's official guidance says: “Image paths are root-relative from your docs repository.” It also says relative paths such as `./screenshot.png` are unsupported. See [Image embeds](https://www.mintlify.com/docs/create/image-embeds). The existing `/images/...` paths were correct. The failure came from passing them through custom-component string props, which kept Mintlify from seeing those images during its MDX transform. - fix hero, building-block, and Slack avatar images - preserve Slack avatar clipping - normalize Hermes and Company Brain icon sizing Tested with Mintlify validation, broken-link checks, and browser checks across every changed route. --- apps/docs/company-brain/automations.mdx | 6 +- apps/docs/company-brain/overview.mdx | 15 +++-- .../use-cases/acting-in-tools.mdx | 12 ++-- .../docs/company-brain/use-cases/greeting.mdx | 11 ++-- .../company-brain/use-cases/incidents.mdx | 6 +- .../use-cases/knowledge-recall.mdx | 6 +- .../use-cases/long-horizon-research.mdx | 6 +- .../use-cases/meeting-recall.mdx | 6 +- .../use-cases/meeting-scheduling.mdx | 3 +- .../use-cases/sandbox-debugging.mdx | 6 +- .../use-cases/support-escalation.mdx | 30 +++++++-- apps/docs/company-brain/use-cases/support.mdx | 3 +- apps/docs/index.mdx | 44 ++++++++----- apps/docs/overview/what-is-supermemory.mdx | 63 ++++++++++++------- apps/docs/snippets/slack-message.mdx | 39 +++++------- 15 files changed, 163 insertions(+), 93 deletions(-) diff --git a/apps/docs/company-brain/automations.mdx b/apps/docs/company-brain/automations.mdx index 7279bac0..da253659 100644 --- a/apps/docs/company-brain/automations.mdx +++ b/apps/docs/company-brain/automations.mdx @@ -14,10 +14,12 @@ Company Brain doesn't only answer when you @mention it. It can run recurring wor An automation is a prompt that runs on a schedule and posts the result somewhere. You write it once, in plain language: - + + supermemory every Monday at 9am, post a digest of what shipped last week and what's still open, to product. - + + Got it — scheduled. First digest posts Monday, 9:00 AM, to product. diff --git a/apps/docs/company-brain/overview.mdx b/apps/docs/company-brain/overview.mdx index c0f0629b..d709e0e7 100644 --- a/apps/docs/company-brain/overview.mdx +++ b/apps/docs/company-brain/overview.mdx @@ -25,10 +25,12 @@ It'll answer a question, actually go do the work, or just jump into a conversati ### Ask it anything - + + supermemory what did we decide about pricing for the company brain - + + You and mahesh decided yesterday that it stays at **$400/mo**, usage based only. we landed on that in a product huddle @@ -36,10 +38,12 @@ It'll answer a question, actually go do the work, or just jump into a conversati ### Put it to work - + + supermemory is the Stripe webhook timeout from Sentry already tracked anywhere? - + + nope, nothing yet — just opened **ENG-847** for it, added the sentry issue to it, and put it on Sam since they were the last one in `webhooks/stripe.ts` and their beautiful code broke it ☠️. here you go, should probably fix it asap. @@ -50,7 +54,8 @@ It'll answer a question, actually go do the work, or just jump into a conversati is prod down? a couple of customers are pinging me - + + not fully down — `api/search` is just elevated, 42 errors in the last 15 min (SM-2041), and Kush is on it. probably that deploy from this morning. Only one user has complained on support and i already replied to them saying it's being investigated. diff --git a/apps/docs/company-brain/use-cases/acting-in-tools.mdx b/apps/docs/company-brain/use-cases/acting-in-tools.mdx index 029d282b..71d8d8f1 100644 --- a/apps/docs/company-brain/use-cases/acting-in-tools.mdx +++ b/apps/docs/company-brain/use-cases/acting-in-tools.mdx @@ -16,10 +16,12 @@ You don't just want to *know* something — you want Company Brain to do the nex ### Read from a tool - + + supermemory what are my open PRs in the web repo? - + + You have **3 open PRs** on `supermemory/web`: - `#1199` staff custom MCP connection cards — review requested - `#1197` company brain onboarding research UI — changes requested @@ -30,10 +32,12 @@ You don't just want to *know* something — you want Company Brain to do the nex ### Write to a tool - + + supermemory create a Linear issue: fix the onboarding redirect - + + Created **ENG-842** — *Fix the onboarding redirect* in Engineering, assigned to you. Open in Linear diff --git a/apps/docs/company-brain/use-cases/greeting.mdx b/apps/docs/company-brain/use-cases/greeting.mdx index 9d78e943..1a0b8af9 100644 --- a/apps/docs/company-brain/use-cases/greeting.mdx +++ b/apps/docs/company-brain/use-cases/greeting.mdx @@ -5,7 +5,7 @@ description: "Connect card, welcome DM, and first answer — activation on day o icon: "user-plus" --- -import { SlackThread, SlackMessage, BOT_AVATAR } from "/snippets/slack-message.mdx"; +import { SlackThread, SlackMessage } from "/snippets/slack-message.mdx"; ## The scenario @@ -15,8 +15,10 @@ A new hire joins the Slack workspace. They shouldn't need a web signup form or a They get a connect card, tap **Connect me**, and receive a welcome DM: - - + + + + Welcome to **Acme**. Here's what I know, what I can access, and what I keep private. Try one of these: @@ -27,7 +29,8 @@ They get a connect card, tap **Connect me**, and receive a welcome DM: What does Acme do? - + + Acme builds memory infrastructure for AI apps — shared context for teams and agents. *(from the company profile your admin seeded at setup)* diff --git a/apps/docs/company-brain/use-cases/incidents.mdx b/apps/docs/company-brain/use-cases/incidents.mdx index 15aaac6f..dcd4b392 100644 --- a/apps/docs/company-brain/use-cases/incidents.mdx +++ b/apps/docs/company-brain/use-cases/incidents.mdx @@ -17,7 +17,8 @@ Someone drops a vague "is prod down?" in `#eng`. Company Brain correlates it wit is prod down? a couple of customers are pinging me - + + Not a full outage — **`api/search` is elevated** (42 errors in the last 15m, mostly `timeout on vectorize`). Sentry issue SM-2041. Deploy from this morning is the likely culprit; rollback candidate is `af61880`. @@ -25,7 +26,8 @@ Someone drops a vague "is prod down?" in `#eng`. Company Brain correlates it wit Or, without anyone asking, a scheduled automation posts every morning: - + + **Daily error digest** — 3 issues new since yesterday, 1 still spiking (`api/search` timeout). Full list in Sentry. diff --git a/apps/docs/company-brain/use-cases/knowledge-recall.mdx b/apps/docs/company-brain/use-cases/knowledge-recall.mdx index d0cfc0ff..68aa29f2 100644 --- a/apps/docs/company-brain/use-cases/knowledge-recall.mdx +++ b/apps/docs/company-brain/use-cases/knowledge-recall.mdx @@ -14,10 +14,12 @@ The Q2 roadmap lives in Notion. Nobody wants to dig for the link mid-conversatio ## What happens - + + supermemory what's in our Q2 roadmap? - + + Three themes for Q2: 1. **Company Brain GA** — Slack bot, connectors, automations 2. **Memory Router v2** — lower latency, better multi-tenant isolation diff --git a/apps/docs/company-brain/use-cases/long-horizon-research.mdx b/apps/docs/company-brain/use-cases/long-horizon-research.mdx index c7c9c669..a7f56d40 100644 --- a/apps/docs/company-brain/use-cases/long-horizon-research.mdx +++ b/apps/docs/company-brain/use-cases/long-horizon-research.mdx @@ -14,10 +14,12 @@ Some questions aren't a quick lookup. They need pulling information from a lot o ## What it will look like - + + supermemory prepare a brief on how we've handled enterprise SSO requests over the last two quarters — who asked, what we promised, what's still open, and what engineering thinks the real effort is - + + **Enterprise SSO — two-quarter brief** - **Demand:** 6 serious asks (Acme, Globex, Initech, …). Three converted to paid pilots. diff --git a/apps/docs/company-brain/use-cases/meeting-recall.mdx b/apps/docs/company-brain/use-cases/meeting-recall.mdx index 2cf4c415..0192c24c 100644 --- a/apps/docs/company-brain/use-cases/meeting-recall.mdx +++ b/apps/docs/company-brain/use-cases/meeting-recall.mdx @@ -14,10 +14,12 @@ Someone missed the Acme call — or was there and forgot the outcome. They ask i ## What happens - + + supermemory what did we decide in the meeting with Acme? - + + Acme is moving to annual billing at the current rate, with a 90-day pilot on the enterprise SSO add-on. Follow-up owned by **Priya**, due Friday. *(from Granola notes, Acme QBR — Jun 11)* diff --git a/apps/docs/company-brain/use-cases/meeting-scheduling.mdx b/apps/docs/company-brain/use-cases/meeting-scheduling.mdx index 5274e027..87bad5f6 100644 --- a/apps/docs/company-brain/use-cases/meeting-scheduling.mdx +++ b/apps/docs/company-brain/use-cases/meeting-scheduling.mdx @@ -21,7 +21,8 @@ A teammate needs help and doesn't want to play calendar ping-pong. They ask in S Dhravya are you free this afternoon? need some help with dev setup - + + Dhravya is free at **2:00 PM**. Sending an invite to block **20 mins** on both your calendars. diff --git a/apps/docs/company-brain/use-cases/sandbox-debugging.mdx b/apps/docs/company-brain/use-cases/sandbox-debugging.mdx index a3d70fb0..c28e4a8b 100644 --- a/apps/docs/company-brain/use-cases/sandbox-debugging.mdx +++ b/apps/docs/company-brain/use-cases/sandbox-debugging.mdx @@ -14,10 +14,12 @@ A test is failing and the stack trace alone isn't enough. You want Company Brain ## What happens - + + supermemory the `permissions.lease` unit test is failing on main — can you reproduce and tell me why? - + + Reproduced in a sandbox against `main`. **Failure:** `permissions.lease` expects temporary access to expire in 15 minutes, but the fixture still asserts 30. diff --git a/apps/docs/company-brain/use-cases/support-escalation.mdx b/apps/docs/company-brain/use-cases/support-escalation.mdx index 4f4e825b..60c2837f 100644 --- a/apps/docs/company-brain/use-cases/support-escalation.mdx +++ b/apps/docs/company-brain/use-cases/support-escalation.mdx @@ -14,7 +14,13 @@ 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**. @@ -22,7 +28,8 @@ A customer files a ticket through Plain. It lands in `#support`, gets triaged wi hi team, just tried the `rewriteQuery` param on the v3 search endpoint and it doesn't seem to actually do anything — tried a few different values, results look identical either way. can someone take a look - + + Confirmed, this is a real one — a couple of people have also flagged it on GitHub over the last week.

@@ -34,12 +41,24 @@ 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.

@@ -56,7 +75,8 @@ A customer files a ticket through Plain. It lands in `#support`, gets triaged wi Open in Web Open in Desktop - + + Dhravya I'll let you review that and let the customer know we have a fix ready.
Please do it ASAP — it's an enterprise customer! diff --git a/apps/docs/company-brain/use-cases/support.mdx b/apps/docs/company-brain/use-cases/support.mdx index 72a2851f..8d2a2791 100644 --- a/apps/docs/company-brain/use-cases/support.mdx +++ b/apps/docs/company-brain/use-cases/support.mdx @@ -17,7 +17,8 @@ A customer question lands in `#support`. Nobody has to @mention the bot — it a customer on the Pro plan is asking if they can export their full memory graph as CSV — do we support that? - + + Yes — **Settings → Export → Full graph (CSV)**. Available on Pro and above. Same answer went out on ticket PLN-1842 last week if you want the exact wording. diff --git a/apps/docs/index.mdx b/apps/docs/index.mdx index bdc43c1b..8b85ca51 100644 --- a/apps/docs/index.mdx +++ b/apps/docs/index.mdx @@ -4,18 +4,14 @@ description: "Context infrastructure for AI agents" mode: "custom" --- -export const HeroCard = ({ imageUrl, title, description, href }) => { +export const HeroCard = ({ title, description, href, children }) => { return (
- {title} + {children}

@@ -62,29 +58,49 @@ export const HeroCard = ({ imageUrl, title, description, href }) => {
+ > + Developer platform + + > + Company brain + + > + Plugins and MCP + + > + Self-hosting +

diff --git a/apps/docs/overview/what-is-supermemory.mdx b/apps/docs/overview/what-is-supermemory.mdx index b394dcf5..273d2119 100644 --- a/apps/docs/overview/what-is-supermemory.mdx +++ b/apps/docs/overview/what-is-supermemory.mdx @@ -6,17 +6,13 @@ icon: "book-open" mode: "wide" --- -export const BuildingBlock = ({ icon, title, href }) => { +export const BuildingBlock = ({ title, href, children }) => { return ( - + {children} {title} @@ -30,50 +26,69 @@ It provides all the building blocks — Memory, Retrieval, Profiles, Connectors,
+ > + + + > + + + > + + + > + + + > + + + > + + + > + + + > + + + > + +
With supermemory, developers can provide perfect recall about their users to build AI agents that are more intelligent, more personalized, and more consistent. diff --git a/apps/docs/snippets/slack-message.mdx b/apps/docs/snippets/slack-message.mdx index b21910f4..28b3735e 100644 --- a/apps/docs/snippets/slack-message.mdx +++ b/apps/docs/snippets/slack-message.mdx @@ -1,10 +1,3 @@ -export const DHRAVYA = { - name: "Dhravya Shah", - avatar: "/images/company-brain/dhravya-slack-icon.jpg", -}; - -export const BOT_AVATAR = "/images/company-brain/supermemory-slack-icon.png"; - export const Mention = ({ children, self = false }) => ( { + const childItems = Array.isArray(children) ? children : [children]; + const dmAvatar = hasAvatar ? childItems[0] : null; + const threadMessages = hasAvatar ? childItems.slice(1) : children; const composerLabel = type === "dm" ? `Message ${dmWith?.name || "someone"}` @@ -91,11 +88,9 @@ export const SlackThread = ({ ) : type === "dm" ? (
- {dmWith?.name + + {dmAvatar} +
@@ -149,7 +144,7 @@ export const SlackThread = ({ className="overflow-y-auto bg-white dark:bg-[#1A1D21]" style={maxHeight ? { maxHeight } : undefined} > - {children} + {threadMessages}
{maxHeight ? (
{ const SELF_NAME = "Dhravya Shah"; - const SELF_AVATAR = "/images/company-brain/dhravya-slack-icon.jpg"; - const BOT_AVATAR = "/images/company-brain/supermemory-slack-icon.png"; + const childItems = Array.isArray(children) ? children : [children]; + const resolvedAvatar = hasAvatar ? childItems[0] : null; + const messageBody = hasAvatar ? childItems.slice(1) : children; const resolvedName = bot ? "supermemory" : self ? SELF_NAME : name || SELF_NAME; - const resolvedAvatar = bot ? BOT_AVATAR : self ? SELF_AVATAR : avatar; const resolvedBadges = badges || (bot ? ["AGENT"] : null); return ( @@ -248,11 +243,9 @@ export const SlackMessage = ({ ))}
{resolvedAvatar ? ( - {resolvedName} + + {resolvedAvatar} + ) : (
- {children} + {messageBody}
{reactions ? (