Context or Trigger Field for Wiki Folders and Files
planned
I
Ignacio Montenegro
Current behavior:
The AI usually needs the user to explicitly say something like "Search Membase" to retrieve wiki content. Alternatively, the AI may pick up on memories automatically, but there is no reliable way to define when a specific wiki folder should be checked.
User problem:
Users cannot set persistent retrieval instructions such as: "Whenever I ask about university classes, check the syllabus folder." As a result, they have to repeat the same instruction across conversations.
Desired behavior:
Add a "when to use this" or trigger/context field at the folder or file level, similar to the trigger/description field used by skills. This would allow users to define contextual usage instructions once.
Examples:
- Wiki folder: "University syllabi" | Trigger: "Use whenever the user asks about courses, exams, assignments, readings, or university deadlines."
- Wiki folder: "Startup docs" | Trigger: "Use whenever the user asks about company strategy, product decisions, investor updates, or roadmap planning."
Why it matters:
This would make wikis feel more autonomous, persistent, and context-aware. Users could set retrieval behavior once and rely on the AI to use the right knowledge source at the right time, without repeating instructions every conversation.
Joshua Park
marked this post as
planned
Joshua Park
Merged in a post:
Smart Router for Automatically Saving Information to the Right Place
I
Ignacio Montenegro
User problem:
Users currently need to manually tell the agent exactly where to save information (e.g., which wiki folder). This interrupts the flow of work.
Desired behavior:
Users should be able to define routing rules in natural language so Membase can route saved information automatically.
Possible approaches:
Option 1: Global routing rules
Users create rules such as:
- "Anything related to this project goes to the project wiki folder."
- "Ideas should go to the ideas folder."
If no rule matches, the agent decides using its best judgment.
Option 2: Per-wiki context descriptions (recommended starting point)
Each wiki folder has a description explaining what should be saved there and why. The model reads these descriptions and routes content accordingly. Simpler, more natural, and builds on existing folder structure.
Feedback loop:
If an agent saves something in the wrong place, the user should be able to correct it. That correction should improve future routing behavior.
Why it matters:
A native router would make Membase feel more intelligent and harder to replace. It would also create a better enterprise story where configurable routing rules are easier to trust than an opaque "agent decides" model.