Skip to main content

Knowledge Base with Tag Filtering in Project Settings

Currently, when managing multiple projects, such as creating a series of e-books, it's common for several projects to reference the same underlying information (e.g., location rental prices, macroeconomic data). The current system requires users to upload the same documents repeatedly for each new project.

This feature request proposes making the existing centralized Knowledge Base accessible from the project settings interface.

By implementing this, users could link their projects to the relevant documents in the centralized Knowledge Base, using tags to filter for the correct files. This would eliminate the need to upload the same documents repeatedly for different projects that share common information, thereby streamlining the workflow, saving time, and ensuring data consistency.

2 comments

Log in to comment and vote

Comments2

  • Red Turtle

    •

    Mar 1

    We can already filter to view specific knowledge base tags when creating Agents. We need similar functionality offered at the folder level. As it stands, you can only query the entire knowledge base, which causes a higher chance of noise and higher token burn.

    It’s common practice for a folder/thread to need specific context from some KB tags, instead of your entire KB, which could be quite large. Ex, only look across my side-hustle docs, not my day-job docs.

    When building, the Mem team can use the same tag filter component from Agents, just expose it in the Project settings page.

  • Plum Pen

    •

    Nov 5, 2025

    Totally support this! I want to be able to use the same agent for multiple similar projects, but limit the scope of the agent at the project level instead of the agent level.