正在加载视频...

视频加载失败

this is pure f*cking treasure 20 useful GitHub projects for a system that captures sources, connects ideas, remembers context, and helps agents act on it your second brain should get sharper after every session CAPTURE THE INPUT 01 Chubby Skills ▸ 02 OpenWiki ▸ 03 Agent Second Brain ▸...

133,321 次观看 • 2 天前 •via X (Twitter)

26 条评论

Gipp 🦅 的头像
Gipp 🦅1 天前

pure builder gold, saved

kozh ./ 的头像
kozh ./2 天前

A nice selection bro

Insomnia 的头像
Insomnia1 天前

I wanna to save all this paper

Diam 的头像
Diam1 天前

Writing the correction back is what stops this becoming a prettier bookmark folder.

Slonski 的头像
Slonski1 天前

a sharper brain after every session

0xbobaa 的头像
0xbobaa1 天前

I think this will be useful

Lummox 的头像
Lummox1 天前

Bookmarked it

烦70·BG小墨 的头像
烦70·BG小墨1 天前

大脑扩容神器 赶紧存起来研究

NO1ennn 的头像
NO1ennn1 天前

really second brain

monokern 的头像
monokern1 天前

good list

Gate高返85阿白 的头像
Gate高返85阿白1 天前

这脑子进化的速度太超前了

返85Gate| 的头像
返85Gate|1 天前

这波干货含金量太高了得赶紧存下来

spect 的头像
spect1 天前

oh myyyy. really treasure broo

ALEXYZ 的头像
ALEXYZ1 天前

sharper after every session is the goal

Marvin 的头像
Marvin1 天前

so basically, you can create a really smart data researcher from AI

凡70|BG 的头像
凡70|BG1 天前

这哪是资料库简直是外挂大脑

yata 的头像
yata1 天前

the most-starred repo here (openviking, 38.7k) is AGPL. "build a second brain for your business" needs a footnote.

marfin 的头像
marfin1 天前

thx for this list fam

Isoldegwow 的头像
Isoldegwow1 天前

20 repos to build a second brain, while my first one still can't remember where I saved this list 🧠

shikamaru 的头像
shikamaru1 天前

hindsight + memu + obsidian is a stack i need to explore!

EagleVision 的头像
EagleVision1 天前

like the idea that the system should improve itself and add new results to itself

Sofie a, 的头像
Sofie a,1 天前

This is so true

Iron Mind 的头像
Iron Mind1 天前

bookmarked that

Gregor 的头像
Gregor1 天前

'gets sharper after every session' assumes you stay consistent with the inputs. is it just me or do these stacks mostly degrade around week 3 when the curation cost catches up?

beamnxw ./ 的头像
beamnxw ./1 天前

my substack:

maguyva 的头像
maguyva1 天前

ngl half these agent memory stacks fall apart on retrieval, not capture. saving is the easy part

相关视频

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

Yarchi

58,591 次观看 • 3 个月前

One of the smartest things you can do with Fable 5 right now: Re-create your AI second brain to log all your business ideas, personal context, and important data. The first time I built an AI second brain was with Opus, but I recently re-created it with Fable 5, and it blew my mind. Here's exactly how to get started: Step 1. Set up your Obsidian vault Download Obsidian from Obsidian dot md if you haven't already. Then, go ahead and create a clean vault with your most important folders. For example: /ideas → business ideas, content angles, random thoughts /context → who you are, your business, your goals, your stack /data → important numbers, portfolios, metrics /log → daily entries, decisions, lessons learned This is your database. Everything Fable reads lives here. Step 2. Connect Fable 5 to your vault I like this Claude Code prompt: "/goal connect to my Obsidian vault at [path] and act as my second brain orchestrator. Read everything in /context before every session. Log anything new I tell you to /log with today's date." Fable now reads your vault before it answers anything - it knows your business, your goals, your history. Step 3. Build the self-update habit Every time you have an idea, a decision, or a lesson, tell Fable: "Log this to my second brain: [thought]" Step 4. Start querying it You can start sending prompts like: → "What are the most common themes across my last 30 ideas?" → "Based on my context, what should I be prioritising this week?" → "What decisions have I made about my content strategy so far?" Opus was good at this, but Fable is on another level. I feel the depth of reasoning it brings to your data is genuinely unlike anything I've used before. Some might argue it's a bit of overkill to use Fable for a simple second-brain setup, but if you have the means, it's 100% worth it. Build this once, and it'll compound forever.

Miles Deutscher

92,735 次观看 • 2 个月前

Andrej Karpathy said: "There's room for an incredible new product in the second brain space" This might be it. (bookmark it) Everyone is suddenly building a second brain. Karpathy's LLM wiki pattern went viral, and half of X is now hand-wiring Obsidian to Claude Code so an agent maintains their notes for them. The idea is beautiful: stop making your AI re-read raw notes on every question. Let it build a wiki that compounds. As Karpathy put it, "LLMs don't get bored, they don't forget to update a cross-reference (backlinks), and can touch 15 files in one pass." But if you start doing it manually, it becomes a project in itself. You wire up the vault, the agents, the schedules, the integrations, and then you babysit all of it. So I sat down with Arjun, who actually built the open source version of this, and we broke down what it looks like when the whole thing already works out of the box. It just crossed 15K stars on GitHub. Think Claude's desktop app, open source, with two things layered on top: → A work brain: background agents index your emails, meetings, and notes into a living knowledge graph that updates itself as you work. → Work surfaces: chat is not the best interface for real work, so you get an email client, a meeting note taker, a browser, and a code mode where you and the AI actually collaborate. The part that got me: a customer email comes in asking for a product change, a background agent triages it, spins up Claude Code in its own worktree, and the feature is written before you are back at your desk. Bring your existing Obsidian vault, connect Slack, X, and Fireflies, and let it run your day. Here's the full breakdown of what we covered in this session: Enjoy! 00:00 Intro 01:08 What is Roboat (an open source AI co-worker) 02:42 The second brain (a knowledge graph of your work) 04:01 Bringing your existing Obsidian vault in 04:46 Work surfaces 05:29 Meetings and automatic note taking 06:53 Connecting Slack, X and other sources 07:55 Background agents that run your day 09:24 Code mode (Claude Code and Codex) 10:18 Demo: from an email to written code 14:28 Guardrails: approvals and agent workspaces 17:15 Scheduling agents on a cron 18:52 The browser work surface (browser use) 20:42 Wrapping up: automating your whole day 22:44 Outro Checkout Rowboat's GitHub repo: (don't forget to star 🌟) My co-founder recently wrote a great article on the same idea, and I highly recommend reading it as well. The article is quoted below. Here's my session with Arjun:

Akshay 🚀

45,815 次观看 • 2 个月前

THIS GUY BUILT A BUSINESS SECOND BRAIN WITH CLAUDE CODE + OBSIDIAN IN 3 STEPS Most teams do not need another Notion workspace. They need a place where the company can remember how it works. The video shows a simple setup: 1. Create one empty folder called second brain. 2. Split it into 3 buckets: raw new knowledge wiki 3. Let Claude Code turn messy company material into connected notes. The useful part is the separation. Raw is where your existing stuff goes: SOPs, sales docs, process notes, client delivery checklists, old Loom summaries, onboarding docs. New knowledge is where fresh outside material lands: articles, clips, tactics, examples, market notes. Wiki is the cleaned version: concepts, roles, processes, SOPs, gaps, reusable decisions. That is where Claude Code becomes more useful than a normal chat window. Instead of asking it to remember random context forever, you give it a folder it can read, edit, and reorganize. Then Obsidian becomes the human interface. The Obsidian Web Clipper captures useful pages into the vault. Claude Code ingests them. The wiki gets updated. Then you can ask questions like: “Does my current workflow actually hold up?” That is the real point. Not “AI notes.” A business memory system that can compare what you do today against new information tomorrow. The caveat: this is not magic company intelligence. If your raw docs are vague, outdated, or full of tribal knowledge, Claude will organize weak inputs into cleaner weak outputs. You still need naming rules, review habits, and someone responsible for deleting junk. But the setup is refreshingly practical. Folder first. Clipper second. Claude Code as the maintainer. No giant knowledge base migration. No complex setup. Just a local vault that can slowly turn scattered business memory into something searchable, editable, and actually reusable.

kocer

16,698 次观看 • 3 个月前

I just built a self-improving second brain in Claude Code 🤯 A brain that runs your brand: every tool reads from it, it's wired to your live data, and it gets smarter every week. All running on the Claude Agent SDK. Perfect for DTC brands and agencies whose AI output sounds generic because every new chat starts from zero. If you're re-explaining your brand to AI every single time — re-pasting the voice guidelines, re-describing the customer you've described a hundred times, re-uploading the same positioning doc you uploaded yesterday, and still editing for an hour to strip out the generic phrasing... A brand second brain fixes the entire loop: → Build 3 foundation files once: brand DNA, voice, and customer → Every skill you create reads from them automatically → Wire in live data — your ad account, competitor ads, customer reviews → A weekly routine refreshes the brain with what's actually working → Every output comes back on-brand on the first pass No re-briefing AI on every chat. No hour of editing to undo generic phrasing. No brain that goes stale the week after you build it. What a second brain gives you: → The exact 3-file foundation that runs the whole system → The skill structure that makes every tool brand-aware by default → The live-data wiring that keeps it grounded in reality → The weekly self-improvement loop that keeps it sharp → The cold-start sequence to stand it all up from zero Built 100% in Claude Code. I put together the full playbook with the file structure, the wiring, and the exact setup. Want it for free? > Like this post > Comment "BRAIN" And I'll send it over (must be following so I can DM)

Mike Futia

18,118 次观看 • 3 个月前