mcp-memory-bucket 0.9.0 → 0.10.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -118,6 +118,25 @@ server); `npm start` does **not** rebuild it, so run `npm run build`
118
118
  again after changing anything under `src/client/`. `npm run dev` rebuilds
119
119
  the client on change alongside the server, for active UI development.
120
120
 
121
+ The **🗂 Folder View** toggle switches the same UI into a directory-style
122
+ browsing mode, for exploring what's in the bucket by structure instead of
123
+ narrowing a flat list. A dropdown picks between three layouts — **Folder
124
+ tree** (the default: expand a folder to see its items), **Breadcrumb
125
+ drill-down** (folder cards you click into, one level deep), and **Tag →
126
+ Name** (flat and cross-folder: items group by tag regardless of which
127
+ folder they're in, so browsing by tag isn't scoped to one folder; an item
128
+ with multiple tags appears under every one of them, Gmail-label style, and
129
+ each leaf shows which folder it's actually in; untagged items land in an
130
+ "(untagged)" bucket). The last-picked mode and each mode's expand/collapse
131
+ state persist across reloads. Folder View keeps its own folder/tag
132
+ selection and its own open item, entirely independent of the flat Filters
133
+ view's `activeFolders`/`activeTags`/selection — switching between the two
134
+ never disturbs either one's state. The broader query scope (search text,
135
+ type filter, date range, deprecated/paused visibility) is shared between
136
+ both views. Clicking a folder or tag node opens a resizable middle pane
137
+ listing its contents; clicking an item there, or clicking a leaf item
138
+ directly in the tree, opens it in the detail pane on the right.
139
+
121
140
  ### Configuration
122
141
 
123
142
  By default the server uses the current working directory as the base for