### Changes

- Memory: add a core OpenAI-compatible embedding provider for local and hosted OpenAI-style endpoints, with config, doctor, and docs support. (#85269) Thanks @dutifulbob.

- Plugin SDK: mark memory-specific embedding provider registration as deprecated compatibility and surface non-bundled usage in plugin compatibility diagnostics. (#85072) Thanks @mbelinky.

### Fixes

engine.

Memory search can consume generic `embeddingProviders`. The older

`memoryEmbeddingProviders` contract remains for compatibility while existing

memory-specific providers migrate, but new reusable embedding providers should

use `embeddingProviders`.

`memoryEmbeddingProviders` contract is deprecated compatibility while existing

memory-specific providers migrate; new reusable embedding providers should use

`embeddingProviders`.

## Review checklist

`api.runtime.config.loadConfig()` / `api.runtime.config.writeConfigFile(...)`

- legacy memory-plugin split registration while memory plugins move to

`registerMemoryCapability`

- legacy memory-specific embedding provider registration while embedding

providers move to `api.registerEmbeddingProvider(...)` and

`contracts.embeddingProviders`

- legacy channel SDK helpers for native message schemas, mention gating,

inbound envelope formatting, and approval capability nesting

- legacy channel route key and comparable-target helper aliases while plugins

| `speechProviders` | `string[]` | Speech provider ids this plugin owns. |

| `realtimeTranscriptionProviders` | `string[]` | Realtime-transcription provider ids this plugin owns. |

| `realtimeVoiceProviders` | `string[]` | Realtime-voice provider ids this plugin owns. |

| `memoryEmbeddingProviders` | `string[]` | Legacy memory embedding provider ids this plugin owns. |

| `memoryEmbeddingProviders` | `string[]` | Deprecated memory-specific embedding provider ids this plugin owns. |

| `mediaUnderstandingProviders` | `string[]` | Media-understanding provider ids this plugin owns. |

| `transcriptSourceProviders` | `string[]` | Transcript source provider ids this plugin owns. |

| `imageGenerationProviders` | `string[]` | Image-generation provider ids this plugin owns. |

General embedding providers should declare `contracts.embeddingProviders` for

each adapter registered with `api.registerEmbeddingProvider(...)`. Use the

general contract for reusable vector generation, including providers consumed by

memory search. `contracts.memoryEmbeddingProviders` is the older

memory-specific compatibility contract and remains while existing providers

migrate to the generic embedding provider seam.

memory search. `contracts.memoryEmbeddingProviders` is deprecated

memory-specific compatibility and remains only while existing providers migrate

to the generic embedding provider seam.

`contracts.gatewayMethodDispatch` currently accepts

`"authenticated-request"`. It is an API hygiene gate for native plugin HTTP

**New**: one call on the memory-state API -

`registerMemoryCapability(pluginId, { promptBuilder, flushPlanResolver, runtime })`.

Same slots, single registration call. Additive memory helpers

(`registerMemoryPromptSupplement`, `registerMemoryCorpusSupplement`,

`registerMemoryEmbeddingProvider`) are not affected.

Same slots, single registration call. Additive prompt and corpus helpers

(`registerMemoryPromptSupplement`, `registerMemoryCorpusSupplement`) are

not affected.

</Accordion>

<Accordion title="Memory embedding provider API">

**Old**: `api.registerMemoryEmbeddingProvider(...)` plus

`contracts.memoryEmbeddingProviders`.

**New**: `api.registerEmbeddingProvider(...)` plus

`contracts.embeddingProviders`.

The generic embedding provider contract is reusable outside memory and is

the supported path for new providers. The memory-specific registration API

remains wired as deprecated compatibility while existing providers migrate.

Plugin inspection reports non-bundled usage as compatibility debt.

</Accordion>

is the generic embedding surface for reusable vector generation. Memory search

can consume this generic provider surface. The older

`api.registerMemoryEmbeddingProvider(...)` and

`contracts.memoryEmbeddingProviders` seam remains as compatibility while

`contracts.memoryEmbeddingProviders` seam is deprecated compatibility while

existing memory-specific providers migrate.

### Tools and commands

| `api.registerMemoryFlushPlan(resolver)` | Memory flush plan resolver |

| `api.registerMemoryRuntime(runtime)` | Memory runtime adapter |

### Memory embedding adapters

### Deprecated memory embedding adapters

| Method | What it registers |

| ---------------------------------------------- | ---------------------------------------------- |

- `MemoryFlushPlan.model` can pin the flush turn to an exact `provider/model`

reference, such as `ollama/qwen3:8b`, without inheriting the active fallback

chain.

- `registerMemoryEmbeddingProvider` lets the active memory plugin register one

or more embedding adapter ids (for example `openai`, `gemini`, or a custom

plugin-defined id).

- User config such as `agents.defaults.memorySearch.provider` and

`agents.defaults.memorySearch.fallback` resolves against those registered

adapter ids.

- `registerMemoryEmbeddingProvider` is deprecated. New embedding providers

should use `api.registerEmbeddingProvider(...)` and

`contracts.embeddingProviders`.

- Existing memory-specific providers continue to work during the migration

window, but plugin inspection reports this as compatibility debt for

non-bundled plugins.

### Events and lifecycle

```

Declare the same id in `contracts.embeddingProviders`. This is the

general embedding contract for reusable vector generation. Use

`registerMemoryEmbeddingProvider(...)` only for memory-engine-specific

adapters.

general embedding contract for reusable vector generation, including

memory search. `registerMemoryEmbeddingProvider(...)` is deprecated

compatibility for existing memory-specific adapters.

</Tab>

<Tab title="Image and video generation">

Video capabilities use a **mode-aware** shape: `generate`,

| `plugin-sdk/memory-core` | Bundled memory-core helper surface for manager/config/file/CLI helpers |

| `plugin-sdk/memory-core-engine-runtime` | Memory index/search runtime facade |

| `plugin-sdk/memory-core-host-engine-foundation` | Memory host foundation engine exports |

| `plugin-sdk/memory-core-host-engine-embeddings` | Memory host embedding contracts, registry access, local provider, and generic batch/remote helpers |

| `plugin-sdk/memory-core-host-engine-embeddings` | Memory host embedding contracts, registry access, local provider, and generic batch/remote helpers. `registerMemoryEmbeddingProvider` on this surface is deprecated; use the generic embedding provider API for new providers. |

| `plugin-sdk/memory-core-host-engine-qmd` | Memory host QMD engine exports |

| `plugin-sdk/memory-core-host-engine-storage` | Memory host storage engine exports |

| `plugin-sdk/memory-core-host-multimodal` | Memory host multimodal helpers |

listRegisteredMemoryEmbeddingProviderAdapters,

listRegisteredMemoryEmbeddingProviders,

} from "../plugins/memory-embedding-provider-runtime.js";

export {

clearMemoryEmbeddingProviders,

registerMemoryEmbeddingProvider,

} from "../plugins/memory-embedding-providers.js";

export { clearMemoryEmbeddingProviders } from "../plugins/memory-embedding-providers.js";

/**

* @deprecated New embedding providers should use `api.registerEmbeddingProvider(...)`

* and `contracts.embeddingProviders`. This memory-specific registrar remains

* available only for compatibility while existing providers migrate.

*/

export { registerMemoryEmbeddingProvider } from "../plugins/memory-embedding-providers.js";

export type {

MemoryEmbeddingBatchChunk,

MemoryEmbeddingBatchOptions,

file: "src/plugins/hook-types.ts",

marker: "@deprecated Use gateway_stop",

},

{

code: "deprecated-memory-embedding-provider-api",

file: "src/plugins/types.ts",

marker: "registerMemoryEmbeddingProvider",

},

{

code: "channel-route-key-aliases",

file: "src/plugin-sdk/channel-route.ts",