Changelog: Memory

What we've shipped in Gurusup Brain, newest first.

  1. Memory

    Your first memory starts from the most useful content

    The first build used to wait until everything you imported had been read. With a large Slack history or a big Notion workspace, that meant waiting a long time before you could ask anything.

    Now Gurusup Brain starts with a first batch and brings in the rest on later passes. It reads uploaded files first, then Notion, HubSpot, webhooks and Slack, in that order.

    You can start asking much sooner, and the memory keeps filling in behind you. With very large imports, the first answers may not cover everything yet, and Ingest shows what is still being learned. As later passes finish, the same question gets a more complete answer without you doing anything.

  2. Memory

    See what Brain is doing while it learns

    Empty screens used to leave new admins guessing. Now Ingest, Conflicts, Skills, Synapses, Queries and Sources show a preview of what they will hold until the memory is built, and a notice across the app says when it hasn't been built yet.

    • Each ingest shows one clear state (Queued, Learning, Learned, Paused or Failed) and a three-step progress bar. A failed ingest is no longer marked as learned.
  3. Memory

    Fixes that keep your memory up to date

    Three fixes so what you connect and edit actually lands in your memory, without slowing the app down.

    Fixes

    • Editing a wiki page no longer stalls its sync.
    • Organizing a source's content no longer fails on large results, so the whole source reaches your memory.
    • Many searches at once no longer slow down navigating the app.