Answer with citations
Ask a real question. Memindex picks the right sources, reads the evidence, and writes an answer with numbered citations. If it doesn’t know, it says so — it never guesses.
How to use Memindex.
Memindex is your company’s shared memory. It reads Slack, Gmail, and GitHub on its own — nobody files anything — and everything it learns becomes searchable here, with a link back to the original.
Two ways to ask
Raw search
Skip the summary and see the matching memories directly. Faster, and better when you just need to find a thread, file, or email again.
Questions that work well
- “What did we decide about the Knight Phase 0 audit?”
- “Where is the Stripe webhook handler in octave?”
- “Why was manifest.webmanifest getting blocked in siteops?”
- “What are this week’s priorities from the team email?”
- “How did SimpliLeads hold up under load testing?”
Use real names — clients, repos, people. Memindex indexes decisions, resolutions, and who said what, so “what did we decide about X” beats “tell me about X”.
What it knows
SlackLive — new threads appear ~2 minutes after the conversation settles.
Every thread in channels the bot has been invited to.
GmailChecked every 5 minutes.
Substantive email threads (newsletters and automated mail are filtered out).
CodeSynced on demand — only changed files re-index.
Source code from every repo across zthebaron and DigitalBoutique-ai.
Issues/PRsSynced with the code.
GitHub issues and pull requests, including comment discussions.
To teach it a new Slack channel, invite @dbaibrain to the channel. Check status to see freshness per source.
Using it from Claude
Memindex is also an MCP server, so Claude can consult it mid-task. In Claude Code, ask Tim to register dbai-knowledge for you, then just mention it: “check dbai-knowledge for what we decided about…”. Claude gets the same cited answers you see here.