RememberStackremember.dev/docs

What is not built yet

This page lists what you might expect and will not find. Everything here is absent from the current release; nothing here has a date.

Ingest

  • Audio and video. RememberStack does not ingest audio or video yet; no converter turns speech or video into text.
  • URLs. You cannot ingest a web page by its address; fetch the page yourself and upload the file.
  • Connectors and watched folders. Nothing pulls documents from another system or a folder automatically; the remember connectors commands and SDK connector methods call routes that no deployment serves, and the connectors-watched-directory install extra installs nothing.

Documents

  • Erasing a document. Deleting a document removes it from the memory but keeps its claims and stored original as history; the HTTP API, the SDK, the CLI and the MCP tools cannot erase a document's bytes.
  • Deleting one version. You can delete a whole document, not a single version of it.
  • Waiting for readiness from the CLI. No remember command waits for a document to be processed; use the SDK's wait_for_readiness or the MCP pipeline_readiness tool.

Knowledge

  • Compiled pages. RememberStack does not write summary pages that combine what it knows about a topic; the envelope's pages field and the compiled grain exist but stay empty, and the k install extra installs nothing.
  • Opening a source from an agent. No MCP tool returns a whole original source file; agents read passages through search and adjacent_chunks (a self-hosted engine can publish its sources as files, see Filesystem views).

Clients

  • Async Python client. The remember package is synchronous only.
  • Other languages. There is no TypeScript, JavaScript, Go or other client library; use the HTTP API.

Running the engine