Skip to main content

​
Custom Memory Providers

Custom memory providers are not supported in BindAI V1. The V1 memory implementation described by this documentation uses project-local SQLite storage. This page explains the boundary of that implementation; it does not describe a custom-provider API.

​
V1 Memory Storage

The documented storage layout is:
The database filename shown here is an example of the project-local memory layout, not a guarantee that every project uses this exact filename.

​
Supported Scope

BindAI V1 documents a SQLite-based memory implementation for Agent conversation context. Do not assume that the current product provides an extension point for replacing the SQLite backend with a custom provider.

​
Unsupported Custom-Provider APIs

The following must not be treated as supported BindAI V1 APIs unless they are implemented and explicitly exposed by the current codebase:
  • Custom MemoryProvider implementations
  • A MemoryRecord management API
  • A MemoryRegistry for registering providers
  • Alternative database-backed memory providers
  • External memory-service providers
  • Custom vector-memory providers
  • Studio configuration for custom memory backends

​
Memory and Workflow Persistence

Agent memory and workflow persistence serve different purposes.
  • Agent memory concerns conversation context associated with an Agent.
  • Workflow persistence concerns workflow execution state.
Do not assume that configuring or replacing one persistence mechanism configures or replaces the other.

​
Summary

BindAI V1’s documented memory implementation uses project-local SQLite storage. Custom memory-provider APIs and alternative memory backends are not supported V1 features. This page intentionally excludes setup instructions, examples, and API contracts for functionality that is not part of the supported implementation.