pkg(tools): Expose raw search results in MemoryPromptData for prompt templates

[MaheshtheDev]

Expose raw search results in MemoryPromptData so prompt templates can traverse, filter, and selectively include results based on metadata (e.g. score, source).

Usage example

const promptTemplate = (data: MemoryPromptData) => {
  const relevant = data.searchResults.filter(
    (r) => (r.metadata?.score as number) > 0.7
  )
  return `${data.userMemories}\n${relevant.map(r => r.memory).join('\n')}`
}

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
🕒 Queued	supermemory-mcp	bafe6ff	Mar 18 2026, 05:51 PM

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	supermemory-app	a00a751	Mar 19 2026, 12:42 AM

[MaheshtheDev]

• pkg(tools): Expose raw search results in MemoryPromptData for prompt templates #787 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add the label Main to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[claude]

Claude finished @MaheshtheDev's task in 1m 41s —— View job

---

Code Review Complete

• Get PR diff and understand changes
• Review code for bugs and security issues
• Check surrounding code context
• Submit review

Overview: Adds a searchResults field to MemoryPromptData exposing raw API search results with metadata for custom filtering in prompt templates.

Issues found: None — this looks good to ship.

The implementation is clean:

• Type Array<{ memory: string; metadata?: Record<string, unknown> }> correctly matches ProfileStructure.searchResults.results
• Null safety handled properly with memoriesResponse.searchResults?.results ?? []
• Clear distinction between generalSearchMemories (deduplicated, pre-formatted string) and searchResults (raw data with metadata) gives users flexibility
• Documentation accurately reflects the new capability
• Version bump to 1.4.01 is appropriate for this additive change

Score: 10/10

[claude]

Overview: Adds a searchResults field to MemoryPromptData exposing raw API search results with metadata for custom filtering in prompt templates.

Issues found: None — this looks good to ship.

The implementation is clean:

• Type Array<{ memory: string; metadata?: Record<string, unknown> }> correctly matches ProfileStructure.searchResults.results
• Null safety handled properly with memoriesResponse.searchResults?.results ?? []
• Clear distinction between generalSearchMemories (deduplicated, pre-formatted string) and searchResults (raw data with metadata) gives users flexibility
• Documentation accurately reflects the new capability
• Version bump to 1.4.01 is appropriate for this additive change
• Type cleanup in memory-prompt.ts using MemoryPromptData instead of inline type is a nice improvement

Score: 10/10

[graphite-app]

Merge activity

• Mar 19, 12:38 AM UTC: Dhravya added this pull request to the Graphite merge queue.
• Mar 19, 12:40 AM UTC: Merged by the Graphite merge queue.

[sentry]

Bug: The documentation example for filtering search results uses r.metadata?.score, but the API returns the score in the top-level similarity field, causing the filter to fail.
_{Severity: MEDIUM}

Suggested Fix

Update the documentation example in apps/docs/ai-sdk/user-profiles.mdx to filter by r.similarity instead of r.metadata?.score. The corrected code should be const relevant = data.searchResults.filter((r) => r.similarity > 0.7).

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: apps/docs/ai-sdk/user-profiles.mdx#L198

Potential issue: The documentation example for filtering memory search results
incorrectly references `r.metadata?.score`. The actual API response places the
similarity score in a top-level `similarity` field. As a result, any user code following
this example will have the filter condition `(r.metadata?.score as number) > 0.7`
evaluate to `false`, because `r.metadata?.score` is `undefined`. This will cause all
search results to be filtered out, leading to an empty `relevant` array and preventing
the intended user profile information from being included in the prompt.

_{Did we get this right? 👍 / 👎 to inform future reviews.}