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 stores audio and video and describes each file with a card, but no converter turns speech or video into text.
  • Email attachments. An .eml file's attachments are listed by name and size; they are not read.
  • 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.
  • Document filters on facts and operations. Claim and chunk search take a documents filter; the assured operations (facts_context and the others), fact lookups and the SQL query functions do not yet, and there is no documents filter over MCP because MCP has no claim or chunk search tool.
  • Metadata from other formats. Word, PowerPoint, PDF and email files give their title, people and dates, and .xlsx workbooks their title, author and dates; HTML, EPUB and notebooks give only a title, and other formats give none.
  • 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