Skip to content

docs(sdk): update SDK docs to describe v2 MemoryClient surface#6

Merged
ethanj merged 4 commits intomainfrom
docs/sdk-v2-surface-update
Apr 21, 2026
Merged

docs(sdk): update SDK docs to describe v2 MemoryClient surface#6
ethanj merged 4 commits intomainfrom
docs/sdk-v2-surface-update

Conversation

@ethanj
Copy link
Copy Markdown
Contributor

@ethanj ethanj commented Apr 21, 2026

Summary

  • Rewrite the SDK section to describe the current v2 surface — MemoryClient, the providers config, the ./browser subpath — instead of the pre-split AtomicMemorySDK / ContextManager shape.
  • Drop pages that describe features no longer in the OSS core SDK: concepts/consent-and-gating and cookbook/knowledge-base (both belong to the proprietary webapp wrapper).
  • Treat browser-helpers as "Browser entry" and point it at @atomicmemory/atomicmemory-sdk/browser.
  • Forward-only style throughout: these pages describe what the SDK is, not a migration from any prior shape.

Pages changed

  • sdk/overview.md, sdk/quickstart.md
  • sdk/concepts/architecture.md, provider-model.md, scopes-and-identity.md, storage-adapters.md, embeddings.md
  • sdk/guides/atomicmemory-backend.md, mem0-backend.md, custom-provider.md, browser-helpers.md, nodejs-server.md, browser-primitives.md, swapping-backends.md
  • sdk/api/overview.md, memory-provider.md
  • sidebars.ts (drops the two removed pages)

Test plan

  • pnpm build succeeds — no broken internal links
  • Spot-check rendered pages in dev server

ethanj added 4 commits April 21, 2026 02:40
Rewrite the SDK section to describe the current public surface —
MemoryClient, the providers config, and the slim ./browser entry —
instead of the pre-split AtomicMemorySDK/ContextManager shape.

- Overview, quickstart, architecture, provider-model, and all guides
  now use MemoryClient; userAccounts / platform / targetDomain
  examples are gone.
- Scopes-and-identity drops UserAccountsManager and describes the
  Scope type the SDK actually accepts.
- browser-helpers is now "Browser entry", describing the
  @atomicmemory/atomicmemory-sdk/browser subpath.
- consent-and-gating and cookbook/knowledge-base are removed — those
  features live in the webapp wrapper, not the OSS core.
- Storage / embeddings / api pages touched up for the same rename.

Forward-only: these pages describe what the SDK is today, not a
migration path from any prior shape.
…, ingestModes spelling

- swapping-backends migration example now uses the real MemoryIngest
  shape (content/kind/metadata), not a non-existent memory field
- quickstart multi-provider example uses pathPrefix (the real field),
  not apiStyle (webapp-wrapper-era)
- ingestModes spelling: 'messages' plural matches types.ts
- MemoryProvider.close() clarified — providers can define it but
  MemoryClient does not drive teardown
…ethods + requiredScope/extension-key shapes

- custom-provider example now implements the template-method hooks
  (doIngest/doSearch/doGet/doDelete/doList) that BaseMemoryProvider
  actually requires, not direct overrides of the public methods
- requiredScope shape corrected everywhere: { default: Array<keyof
  Scope>, ingest?: ..., ... } not the old { user: bool, ... } form
- extension capability keys corrected to the real spellings: update,
  forget, profile, reflect, batch (previously updater/forgetter/
  profiler/reflector/batchOps — those are the TypeScript interface
  names, not the capability keys)
- scopes-and-identity + capabilities + memory-provider + both backend
  guides updated for consistency
…es call site

Last two stale sdk. references:
- errors.md handling example now uses memory.package(request) /
  memory.search(request) with the single-arg MemoryClient shape
- atomicmemory-backend.md cache tip now says memory.capabilities()
@ethanj ethanj merged commit 5d69bf6 into main Apr 21, 2026
@ethanj ethanj deleted the docs/sdk-v2-surface-update branch April 21, 2026 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant