You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Read-only external transcript indexing boundary for ~/.herdr/
#6014
I maintain deja-vu, a local MIT-licensed CLI/MCP server that builds a read-only BM25 index (~/.cache/deja/index.db) across coding-agent transcripts stored on disk so users can search prior project context and past command fixes across tools.
We currently index Herdr's local session records read-only without patching Herdr or opening an unsolicited integration PR. Two short questions to make sure we stay aligned with Herdr's design:
Are there fields or locations under ~/.herdr/ you consider unstable or prefer external indexers not to depend on?
Is there a preferred way external tools should handle Herdr pane/worktree transitions (for example scoping recall by workspace path rather than assuming one long-lived session file)?
Happy to adjust our reader and Herdr guide to match what you consider the stable on-disk boundary.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi Herdr maintainers,
I maintain
deja-vu, a local MIT-licensed CLI/MCP server that builds a read-only BM25 index (~/.cache/deja/index.db) across coding-agent transcripts stored on disk so users can search prior project context and past command fixes across tools.We currently index Herdr's local session records read-only without patching Herdr or opening an unsolicited integration PR. Two short questions to make sure we stay aligned with Herdr's design:
~/.herdr/you consider unstable or prefer external indexers not to depend on?Happy to adjust our reader and Herdr guide to match what you consider the stable on-disk boundary.
All reactions