DEDUPEDCredentials. Calendar, email and chat access needs account credentials, so keep them out of the vault and out of any file the agent writes into it.
Who it is forA knowledge worker who wants the vault to know what is on their schedule and in their inbox, not only what they clipped.
The problemThe vault only holds what you saved by hand, so it misses the meetings and messages that shape the work you are doing.
The outcomeA vault that can read live calendar, email and chat sources through the setup described in the live-data guide.
What you need first
- Git, to clone the repo
- Obsidian, to open the vault as a folder
- Claude Code, the agent the README sets up the vault around
- A terminal, for the copy commands and for running claude
Steps
- Complete the vault setup from the first use case so
~/brainis running in Claude Code - Open the live-data setup guide at
docs/02-setup/live-data.mdin the repo - Connect the calendar, email and chat sources that guide describes, one at a time
- Run
cd ~/brain && claudeand confirm the agent can read one item from each source
Prompt for your agent
Using the live-data guide in the second-brain-os repo, connect the calendar, email and chat sources for the vault at ~/brain. Report which sources connected and list one item read from each. Verify that no credential is written into any markdown file in the vault.
Caveat. The README only links to a live-data guide for these sources, so the specific connection steps must be taken from that page rather than from this summary.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page