Customizing for your use case

Configure how Supermemory processes and retrieves content for your specific use case.

Organizational Context

Tell Supermemory what your organization does and what content matters during ingestion. This steers what gets extracted into memories across every namespace. In v3/v4 this field was called filterPrompt.

// Example: Brand guidelines assistant
await supermemory.organization.update({
  organizationalContext: `You are ingesting content for Brand.ai's brand guidelines system.

    Index:
    - Official brand values and mission statements
    - Approved tone of voice guidelines
    - Logo usage and visual identity docs
    - Approved messaging and taglines

    Skip:
    - Draft documents and work-in-progress
    - Outdated brand materials (pre-2024)
    - Internal discussions about brand changes
    - Competitor analysis docs`,
});

Personal assistant

organizationalContext: `Personal AI assistant. Prioritize recent content, action items,
and personal context. Exclude spam and duplicates.`

Customer support

organizationalContext: `Customer support agent. Prioritize verified solutions, official docs,
and resolved tickets. Exclude internal discussions and PII.`

Legal assistant

organizationalContext: `Legal research assistant. Prioritize precedents, current regulations,
and approved contract language. Exclude privileged communications.`

Finance agent

organizationalContext: `Financial analysis assistant. Prioritize latest reports, verified data,
and regulatory filings. Exclude speculative data and MNPI.`

Healthcare

organizationalContext: `Healthcare information assistant. Prioritize evidence-based guidelines
and FDA-approved info. Exclude PHI and outdated recommendations.`

Developer docs

organizationalContext: `Developer documentation assistant. Prioritize current APIs, working
examples, and best practices. Exclude deprecated APIs and test fixtures.`

The value replaces the existing context in full. Send null to clear it. The legacy shouldLLMFilter, categories, includeItems, and excludeItems settings are not part of the v5 organization resource.

Supporting Context

Guide memory extraction for a specific namespace. Organizational context is org-wide; supporting context is per namespace. In v3/v4 this field was called entityContext.

await supermemory.add("session_abc123", {
  content: "User asked about logo variations for dark backgrounds...",
  supportingContext: `Design exploration conversation between john@acme.com and Brand.ai assistant.
    Focus on John's design preferences and brand requirements.`,
});

Update supporting context only

Set the supporting context for a namespace without uploading content.

await supermemory.namespaces.update("session_abc123", {
  supportingContext: `Design exploration conversation between john@acme.com and Brand.ai assistant.
    Focus on John's design preferences and brand requirements.`,
});

Supporting context persists on the namespace and combines with the org-level organizational context.

The Chunk size and Connector branding sections below use the legacy settings resource. Their client.settings.update(...) examples require a legacy SDK that exposes settings; SDK 5.x users should call PATCH /v3/settings directly with an org admin or owner credential. These options are not fields on the v5 organization resource.

Chunk size

Control how documents are split into searchable pieces. Smaller chunks = more precise retrieval but less context per result.

await client.settings.update({
  chunkSize: 512  // -1 for default
});

Use Case	Chunk Size	Why
Citations & references	`256-512`	Precise source attribution
Q&A / Support	`512-1024`	Balanced context
Long-form analysis	`1024-2048`	More context per chunk
Default	`-1`	Supermemory’s optimized default

Smaller chunks generate more memories per document. Larger chunks provide more context but may reduce precision.

Connector branding

Show “Log in to YourApp” instead of “Log in to Supermemory” when users connect external services. See Connectors Overview for the full list of supported integrations.

Google Drive

Create OAuth credentials in Google Cloud Console
Redirect URI: https://api.supermemory.ai/v3/connections/auth/callback/google-drive

await client.settings.update({
  googleDriveCustomKeyEnabled: true,
  googleDriveClientId: "your-client-id.apps.googleusercontent.com",
  googleDriveClientSecret: "your-client-secret"
});

Notion

Create integration at Notion Developers
Redirect URI: https://api.supermemory.ai/v3/connections/auth/callback/notion

await client.settings.update({
  notionCustomKeyEnabled: true,
  notionClientId: "your-notion-client-id",
  notionClientSecret: "your-notion-client-secret"
});

OneDrive

Register app in Azure Portal
Redirect URI: https://api.supermemory.ai/v3/connections/auth/callback/onedrive

await client.settings.update({
  onedriveCustomKeyEnabled: true,
  onedriveClientId: "your-azure-app-id",
  onedriveClientSecret: "your-azure-client-secret"
});

Client secrets are write-only. GET /v3/settings and the PATCH /v3/settings response return each connector’s client ID and *CustomKeyEnabled flag, but never its client secret.

API reference

// Read organization settings
const { organizationalContext, namespaceCount } = await supermemory.organization.get();

// Update organization context
await supermemory.organization.update({ organizationalContext: "..." });

// Read and update one namespace
const ns = await supermemory.namespaces.get("session_abc123");
await supermemory.namespaces.update("session_abc123", {
  supportingContext: "...",
});

Organization settings are organization-wide and require an organization administrator. Changes apply to new content only—existing memories aren’t reprocessed.

Getting started

Concepts

Using supermemory

Deployment

Other resources

Migration guides

Organizational Context

Supporting Context

Chunk size

Connector branding

API reference

Next steps

Add memories

Connectors

​Organizational Context

​Supporting Context

​Chunk size

​Connector branding

​API reference

​Next steps

Add memories

Connectors

Organizational Context

Supporting Context

Chunk size

Connector branding

API reference

Next steps