Video wird geladen...

Video konnte nicht geladen werden

Beim Laden dieses Videos ist ein Problem aufgetreten. Dies könnte an einem vorübergehenden Netzwerkproblem liegen oder das Video ist möglicherweise nicht verfügbar.

THIS CREATOR MADE HIS HERMES AGENT 10X FASTER WITHOUT CHANGING THE MODEL, JUST BY ADDING ONE FILE TO HIS OBSIDIAN VAULT 00:02 the screen shows a massive second brain with hundreds of connected notes, but without a clear map an AI agent still treats every file like it could... be the answer Hermes used to open 7 different documents and spend nearly 2 minutes searching for the current brief, even though the correct file was already sitting inside the vault the fix was one index file inside each major folder, listing the important subfolders, canonical files, and the exact document the agent should open first after reorganizing the vault, the same search dropped from 2 minutes to around 10 seconds, while several tasks went from 5 or 6 opened files to just one the model never changed, the $30 agent stack never changed, only the structure around it did, because a powerful agent without a map is still just wandering through folders blindlyshow more

Gipp 🦅

7,606 subscribers

36,473 Aufrufe • vor 3 Monaten •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

YOUR HERMES AGENT IS FLYING BLIND WITHOUT A MAP THAT LOOKS LIKE THIS hundreds of nodes, every connection visible, spectral data mapped in real time so nothing gets lost your vault has the same complexity under the hood, your agent just can’t see it I learned this the hard way, one task took 2 minutes opening wrong files for a brief from 3 months ago one index file per major folder fixed it, dropped to 10 seconds build the map, the agent finds everything full breakdown in the article below ↓

YOUR HERMES AGENT IS FLYING BLIND WITHOUT A MAP THAT LOOKS LIKE THIS hundreds of nodes, every connection visible, spectral data mapped in real time so nothing gets lost your vault has the same complexity under the hood, your agent just can’t see it I learned this the hard way, one task took 2 minutes opening wrong files for a brief from 3 months ago one index file per major folder fixed it, dropped to 10 seconds build the map, the agent finds everything full breakdown in the article below ↓

leopardracer

248,763 Aufrufe • vor 3 Monaten

STOP TREATING YOUR OBSIDIAN VAULT AS AI MEMORY. WITHOUT ONE ROUTING FILE, CLAUDE IS BURNING TOKENS ON NOISE YOU FORGOT YOU SAVED. a folder full of markdown does not make Claude smart. what makes it smart is what your agent can find without rereading the whole vault. storage: write → tag → graph → agent scans everything the model touches the entire vault, hallucinates half of it, forgets by the next session. memory: write → index → route → agent opens two files the model reads the index first, follows one path, answers with a link back to the note. i have rebuilt my Obsidian vault three times this year. the first two collapsed inside a month because Claude kept guessing which folder to open. the third one holds because the first thing i ship now is the routing file. Markdown, links, and the graph view are not what changed. what changed was a one-line description per folder, written for the agent, kept current, loaded before any retrieval call. if your agent still starts every session by scanning your whole vault, you are running storage. write the routing file today.

STOP TREATING YOUR OBSIDIAN VAULT AS AI MEMORY. WITHOUT ONE ROUTING FILE, CLAUDE IS BURNING TOKENS ON NOISE YOU FORGOT YOU SAVED. a folder full of markdown does not make Claude smart. what makes it smart is what your agent can find without rereading the whole vault. storage: write → tag → graph → agent scans everything the model touches the entire vault, hallucinates half of it, forgets by the next session. memory: write → index → route → agent opens two files the model reads the index first, follows one path, answers with a link back to the note. i have rebuilt my Obsidian vault three times this year. the first two collapsed inside a month because Claude kept guessing which folder to open. the third one holds because the first thing i ship now is the routing file. Markdown, links, and the graph view are not what changed. what changed was a one-line description per folder, written for the agent, kept current, loaded before any retrieval call. if your agent still starts every session by scanning your whole vault, you are running storage. write the routing file today.

kocer

17,240 Aufrufe • vor 1 Monat

Your AI agent has your API keys. A poisoned document tells it to curl your secrets to an attacker's server. This is credential exfiltration, and it's the #1 risk in agentic AI right now. The fix is removing the secret from the agent entirely. Agent Vault sits between your agent and the APIs it calls. The agent gets dummy credentials, and Agent Vault swaps in the real ones at the network layer. The agent never sees your keys. We just dropped a full video + guide on connecting Hermes Agent to Agent Vault on a VPS!

Your AI agent has your API keys. A poisoned document tells it to curl your secrets to an attacker's server. This is credential exfiltration, and it's the #1 risk in agentic AI right now. The fix is removing the secret from the agent entirely. Agent Vault sits between your agent and the APIs it calls. The agent gets dummy credentials, and Agent Vault swaps in the real ones at the network layer. The agent never sees your keys. We just dropped a full video + guide on connecting Hermes Agent to Agent Vault on a VPS!

Infisical

86,438 Aufrufe • vor 4 Monaten

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

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,643 Aufrufe • vor 4 Monaten

Hermes is powerful. But Open WebUI makes it way easier to actually use. Here’s the setup: → Run Hermes locally → Add the API server → Set up the environment file → Install Open WebUI with Docker → Connect Hermes as the chat agent → Log in and start chatting through a clean UI Now you can use Hermes without living inside the terminal. You get a ChatGPT-style interface, file uploads, model switching, web search, image tools, previews, and cleaner conversation management. Save this video, you’ll make Hermes 10x easier to use. Want the SOP? DM me. 💬

Hermes is powerful. But Open WebUI makes it way easier to actually use. Here’s the setup: → Run Hermes locally → Add the API server → Set up the environment file → Install Open WebUI with Docker → Connect Hermes as the chat agent → Log in and start chatting through a clean UI Now you can use Hermes without living inside the terminal. You get a ChatGPT-style interface, file uploads, model switching, web search, image tools, previews, and cleaner conversation management. Save this video, you’ll make Hermes 10x easier to use. Want the SOP? DM me. 💬

Julian Goldie SEO

61,538 Aufrufe • vor 5 Monaten

THIS GUY TURNED ONE OBSIDIAN VAULT INTO A SHARED BRAIN FOR 5 CLAUDE AGENTS BUILT TO HANDLE 80% OF A SOLO DEVELOPER’S WORK. 00:03 he zooms out and hundreds of connected notes appear on screen. it is the perfect visual for Claude working from one shared project memory instead of starting from zero every session. most developers give Claude 1 file and 1 prompt. this setup gives it the architecture, coding rules, tests, client briefs, and previous decisions before it writes anything. obsidian becomes the memory layer, storing everything in markdown files Claude can read alongside the codebase. every agent works from the same context instead of repeating the same questions. then 5 specialists split the job. one researches, one plans, one codes, one reviews, and one deploys while the developer only controls the important decisions. one vault, 5 agents, 2 model tiers, and a $50 to $150 monthly stack can turn Claude from a chatbot into a small development team.

THIS GUY TURNED ONE OBSIDIAN VAULT INTO A SHARED BRAIN FOR 5 CLAUDE AGENTS BUILT TO HANDLE 80% OF A SOLO DEVELOPER’S WORK. 00:03 he zooms out and hundreds of connected notes appear on screen. it is the perfect visual for Claude working from one shared project memory instead of starting from zero every session. most developers give Claude 1 file and 1 prompt. this setup gives it the architecture, coding rules, tests, client briefs, and previous decisions before it writes anything. obsidian becomes the memory layer, storing everything in markdown files Claude can read alongside the codebase. every agent works from the same context instead of repeating the same questions. then 5 specialists split the job. one researches, one plans, one codes, one reviews, and one deploys while the developer only controls the important decisions. one vault, 5 agents, 2 model tiers, and a $50 to $150 monthly stack can turn Claude from a chatbot into a small development team.

Gipp 🦅

10,799 Aufrufe • vor 3 Monaten

HERMES AGENT + OBSIDIAN IS A COMBINATION NOBODY IS TALKING ABOUT. Hermes ships with a bundled Obsidian skill. read, search, and create notes in your vault out of the box. why this combination is powerful: Hermes built-in memory is capped. MEMORY.md: 2,200 chars (~800 tokens). USER.md: 1,375 chars (~500 tokens). Obsidian vault has no cap. your agent writes research, session summaries, project context, and learned patterns as linked markdown notes. unlimited depth. the agent creates indexed notes by design. timestamps, backlinks, tags. every note connects to the knowledge graph. three ways to integrate: 1. BUNDLED OBSIDIAN SKILL (simplest) ships with Hermes. reads, searches, creates notes in your vault directly. hermes skills list | grep obsidian 2. OBSIDIAN MCP SERVER (deepest) 30+ tools: full-text search, tag lookup, note management, vault analysis, link analysis, orphan detection. add it via: hermes mcp 3. TELEGRAM + CRON → VAULT (always-on) set a cron job that writes daily summaries, research findings, or task reports directly into your Obsidian vault. your agent feeds the vault while you sleep. you review in Obsidian when you're ready. the unlock: Hermes memory handles what the agent needs to know per session (capped, injected). Obsidian handles everything the agent has ever learned (uncapped, searchable). short-term in Hermes. long-term in Obsidian. both accessible. both persistent. keep the vault scope narrow at first. start with one /Hermes folder. expand once you trust the workflow. 8 Loops Indise Hermes Agent👇

HERMES AGENT + OBSIDIAN IS A COMBINATION NOBODY IS TALKING ABOUT. Hermes ships with a bundled Obsidian skill. read, search, and create notes in your vault out of the box. why this combination is powerful: Hermes built-in memory is capped. MEMORY.md: 2,200 chars (~800 tokens). USER.md: 1,375 chars (~500 tokens). Obsidian vault has no cap. your agent writes research, session summaries, project context, and learned patterns as linked markdown notes. unlimited depth. the agent creates indexed notes by design. timestamps, backlinks, tags. every note connects to the knowledge graph. three ways to integrate: 1. BUNDLED OBSIDIAN SKILL (simplest) ships with Hermes. reads, searches, creates notes in your vault directly. hermes skills list | grep obsidian 2. OBSIDIAN MCP SERVER (deepest) 30+ tools: full-text search, tag lookup, note management, vault analysis, link analysis, orphan detection. add it via: hermes mcp 3. TELEGRAM + CRON → VAULT (always-on) set a cron job that writes daily summaries, research findings, or task reports directly into your Obsidian vault. your agent feeds the vault while you sleep. you review in Obsidian when you're ready. the unlock: Hermes memory handles what the agent needs to know per session (capped, injected). Obsidian handles everything the agent has ever learned (uncapped, searchable). short-term in Hermes. long-term in Obsidian. both accessible. both persistent. keep the vault scope narrow at first. start with one /Hermes folder. expand once you trust the workflow. 8 Loops Indise Hermes Agent👇

YanXbt

20,617 Aufrufe • vor 4 Monaten

A GUY MAKING $100K/MONTH WITH AI JUST SHOWED HIS ENTIRE SETUP. IT'S ONE FOLDER OF NOTES AND NOTHING ELSE no framework. no $500 course. he opens his screen and it's just obsidian - a plain notes app - wired into claude here's what he did: -> he pulled claude's memory files out of their default folder and dumped them into one vault -> had claude rename and merge them: 107 messy files collapsed into 17 clean ones -> every folder gets one master note that links to all the others that last part is the whole trick the agent reads the master note, follows the links and by the time it's done it has read every file in the folder. one instruction, full context here's the part most people miss: everyone's trying to make the AI smarter. he made the AI's memory smaller fewer files, better organized, all linked. the agent isn't scanning hundreds of notes anymore - it walks a path you built that's why his agent actually finishes jobs instead of forgetting what it was doing halfway through then he goes one step further: at the end of every session, the agent writes its own daily note. what it did, when, indexed at the top so it can find it again in seconds so he never re-explains anything. the agent looks up what it already did now he types "create a campaign for this offer" and walks away. it reads the product notes, reads the process notes, and comes back with the campaign done you don't need any of the complicated agent tools people are selling you. you need structure and instructions save this. the people winning with AI aren't using better models. they're just the only ones who bothered to organize what it remembers

A GUY MAKING $100K/MONTH WITH AI JUST SHOWED HIS ENTIRE SETUP. IT'S ONE FOLDER OF NOTES AND NOTHING ELSE no framework. no $500 course. he opens his screen and it's just obsidian - a plain notes app - wired into claude here's what he did: -> he pulled claude's memory files out of their default folder and dumped them into one vault -> had claude rename and merge them: 107 messy files collapsed into 17 clean ones -> every folder gets one master note that links to all the others that last part is the whole trick the agent reads the master note, follows the links and by the time it's done it has read every file in the folder. one instruction, full context here's the part most people miss: everyone's trying to make the AI smarter. he made the AI's memory smaller fewer files, better organized, all linked. the agent isn't scanning hundreds of notes anymore - it walks a path you built that's why his agent actually finishes jobs instead of forgetting what it was doing halfway through then he goes one step further: at the end of every session, the agent writes its own daily note. what it did, when, indexed at the top so it can find it again in seconds so he never re-explains anything. the agent looks up what it already did now he types "create a campaign for this offer" and walks away. it reads the product notes, reads the process notes, and comes back with the campaign done you don't need any of the complicated agent tools people are selling you. you need structure and instructions save this. the people winning with AI aren't using better models. they're just the only ones who bothered to organize what it remembers

Paone

23,833 Aufrufe • vor 2 Monaten

The "Karpathy Method" Obsidian + Claude Code is quietly replacing $15/month note apps for 1000s of builders. The setup costs $0. Takes 10 minutes. And it's stupidly simple. Karpathy stores his entire brain in plain markdown files. No Notion. No database. A folder. People mocked it for years. Then Claude Code shipped an agent that lives in the terminal and reads files natively. Obsidian IS files. Notion hides your notes behind an API. Obsidian hands them to the agent raw. The "boomer stack" turned out to be the only one AI can walk through end to end. The method, 4 steps: Open your vault folder in terminal. Type claude. The agent now sees 100% of your notes. Drop a CLAUDE.md at the root. 40 lines: how you tag, how you link, what a good note looks like. Your brain's operating manual. Run 1 nightly job. Claude reads the day's dump links, highlights, half-thoughts and files it into atomic notes with backlinks. Once a week, ask 1 question: "what connects that I haven't connected?" Old notes collide into ideas you'd never find alone. A builder running this loop hit 4,120 notes in 5 months. Found 2 essay ideas in the collisions. Sold both for $3,400. Hardware: a $599 Mac Mini. Software: a folder. The industry spent 10 years building smarter note apps. Karpathy bet on the file. The file won.

The "Karpathy Method" Obsidian + Claude Code is quietly replacing $15/month note apps for 1000s of builders. The setup costs $0. Takes 10 minutes. And it's stupidly simple. Karpathy stores his entire brain in plain markdown files. No Notion. No database. A folder. People mocked it for years. Then Claude Code shipped an agent that lives in the terminal and reads files natively. Obsidian IS files. Notion hides your notes behind an API. Obsidian hands them to the agent raw. The "boomer stack" turned out to be the only one AI can walk through end to end. The method, 4 steps: Open your vault folder in terminal. Type claude. The agent now sees 100% of your notes. Drop a CLAUDE.md at the root. 40 lines: how you tag, how you link, what a good note looks like. Your brain's operating manual. Run 1 nightly job. Claude reads the day's dump links, highlights, half-thoughts and files it into atomic notes with backlinks. Once a week, ask 1 question: "what connects that I haven't connected?" Old notes collide into ideas you'd never find alone. A builder running this loop hit 4,120 notes in 5 months. Found 2 essay ideas in the collisions. Sold both for $3,400. Hardware: a $599 Mac Mini. Software: a folder. The industry spent 10 years building smarter note apps. Karpathy bet on the file. The file won.

Selina

36,122 Aufrufe • vor 2 Monaten

THIS GUY BUILT AN AUTONOMOUS AI AGENT OUT OF CLAUDE CODE + OBSIDIAN and this is way more interesting than another “use AI to take notes” demo the trick is simple: Obsidian is not the writing app here. it becomes the agent’s memory, task board, and context folder. Claude Code is not just answering prompts. it reads the vault, edits files, follows instructions, and keeps moving through the work like a junior operator with a filesystem. the reusable setup looks like this: 1. create an Obsidian vault for one project 2. keep goals, rules, tasks, decisions, and references as markdown files 3. point Claude Code at the folder 4. give it a clear operating loop: read context → choose next task → execute → write back what changed 5. use the notes as persistent memory instead of re-explaining the project every chat that’s the part people miss. the “agent” is not magic. it’s the boring combination of: - local files - explicit rules - task state - write access - a model that can run through the repo/vault Obsidian makes the memory human-readable. Claude Code makes the memory executable. that combo is why the video worked: it turns a notes app into an operating surface for actual work. best use cases: - content systems - research vaults - coding projects - client ops docs - personal knowledge bases that need actions, not just storage the caveat: if your vault is messy, your agent becomes messy too. folders, naming, “done” criteria, and forbidden actions matter more than the prompt. but once the structure is clean, this is one of the easiest ways to build an agent that remembers what happened yesterday without paying for a full custom app.

THIS GUY BUILT AN AUTONOMOUS AI AGENT OUT OF CLAUDE CODE + OBSIDIAN and this is way more interesting than another “use AI to take notes” demo the trick is simple: Obsidian is not the writing app here. it becomes the agent’s memory, task board, and context folder. Claude Code is not just answering prompts. it reads the vault, edits files, follows instructions, and keeps moving through the work like a junior operator with a filesystem. the reusable setup looks like this: 1. create an Obsidian vault for one project 2. keep goals, rules, tasks, decisions, and references as markdown files 3. point Claude Code at the folder 4. give it a clear operating loop: read context → choose next task → execute → write back what changed 5. use the notes as persistent memory instead of re-explaining the project every chat that’s the part people miss. the “agent” is not magic. it’s the boring combination of: - local files - explicit rules - task state - write access - a model that can run through the repo/vault Obsidian makes the memory human-readable. Claude Code makes the memory executable. that combo is why the video worked: it turns a notes app into an operating surface for actual work. best use cases: - content systems - research vaults - coding projects - client ops docs - personal knowledge bases that need actions, not just storage the caveat: if your vault is messy, your agent becomes messy too. folders, naming, “done” criteria, and forbidden actions matter more than the prompt. but once the structure is clean, this is one of the easiest ways to build an agent that remembers what happened yesterday without paying for a full custom app.

kocer

30,403 Aufrufe • vor 3 Monaten

Obsidian CEO actually released the skill that lets your AI agent run your entire vault for you. It's called obsidian-skills. Install it into Claude Code, Codex, or OpenCode, and your agent can read, create, search, and organize notes directly, plus handle Markdown, Bases, and Canvas files without you touching a thing. This is the missing piece for an AI second brain. Your notes live in Obsidian, and now the agent actually knows how to work them. Want the full picture? We broke down how to build a complete AI second brain from scratch in the article below.

Obsidian CEO actually released the skill that lets your AI agent run your entire vault for you. It's called obsidian-skills. Install it into Claude Code, Codex, or OpenCode, and your agent can read, create, search, and organize notes directly, plus handle Markdown, Bases, and Canvas files without you touching a thing. This is the missing piece for an AI second brain. Your notes live in Obsidian, and now the agent actually knows how to work them. Want the full picture? We broke down how to build a complete AI second brain from scratch in the article below.

Simplifying AI

68,025 Aufrufe • vor 2 Monaten

Opus 5.5 makes this AI stack look f…cking illegal 10 GitHub repos for building everything around the model 01 zen-mcp-server ▸ → your agent debates Gemini, GPT and local models mid-task 02 claude-context ▸ → semantic code search so the agent stops grepping blind 03 wshobson/agents ▸ → a roster of subagents, each with one narrow job 04 mcp-agent ▸ → workflow patterns built around MCP tools, not around chat 05 Backlog.md ▸ → tasks live in git, so the agent and you read the same board 06 Claude Code Development Kit ▸ → hooks, subagents and MCP wired for context at scale 07 agent-rules ▸ → shared guardrails the agent inherits in every repo 08 Agent Skills ▸ → one file that teaches the agent a job, portable across tools 09 agent-scan ▸ → scans your agents, MCP servers and skills for what leaks 10 awesome-claude-code-toolkit ▸ → the map: agents, skills, commands, hooks, MCP configs the architecture: rules → context → subagents → tools → state → review → scan I'd split the stack like this: context: claude-context → Development Kit work: wshobson/agents → mcp-agent → zen-mcp-server state: Backlog.md safety: agent-rules → Agent Skills → agent-scan everyone posts the SDK and the CLI the layer that decides whether your agent survives a week is this one the model is one folder in the stack ⭣

Opus 5.5 makes this AI stack look f…cking illegal 10 GitHub repos for building everything around the model 01 zen-mcp-server ▸ → your agent debates Gemini, GPT and local models mid-task 02 claude-context ▸ → semantic code search so the agent stops grepping blind 03 wshobson/agents ▸ → a roster of subagents, each with one narrow job 04 mcp-agent ▸ → workflow patterns built around MCP tools, not around chat 05 Backlog.md ▸ → tasks live in git, so the agent and you read the same board 06 Claude Code Development Kit ▸ → hooks, subagents and MCP wired for context at scale 07 agent-rules ▸ → shared guardrails the agent inherits in every repo 08 Agent Skills ▸ → one file that teaches the agent a job, portable across tools 09 agent-scan ▸ → scans your agents, MCP servers and skills for what leaks 10 awesome-claude-code-toolkit ▸ → the map: agents, skills, commands, hooks, MCP configs the architecture: rules → context → subagents → tools → state → review → scan I'd split the stack like this: context: claude-context → Development Kit work: wshobson/agents → mcp-agent → zen-mcp-server state: Backlog.md safety: agent-rules → Agent Skills → agent-scan everyone posts the SDK and the CLI the layer that decides whether your agent survives a week is this one the model is one folder in the stack ⭣

rody

18,089 Aufrufe • vor 10 Tagen

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.

DegenCalls

20,124 Aufrufe • vor 3 Monaten

KIMI K3 + OBSIDIAN + LOOP ENGINEERING = A VAULT THAT RUNS ITSELF the core idea: the vault is the loop's state, not the chat window everything Kimi K3 knows lives in a .md file the loop: > capture - a thought lands in 00-inbox > context - K3 pulls links, tags, and neighbouring notes > draft - edits happen inside a git worktree, never the live vault > review - a critic agent checks the diff before anything ships > commit - appended to the vault, nothing gets rewritten the key insight: frontmatter fields like supports, contradicts, and supersedes are graph edges, not metadata - the note format is the write API start with a plain loop, it runs about 2-4x the cost of one direct call > only move to a full graph once state has to outlive the session, several agents need to coordinate, or you have to explain what changed - that jump can run 10-50x one review assistant climbed from 55% to 72% to 84% just by moving through these shapes in order

KIMI K3 + OBSIDIAN + LOOP ENGINEERING = A VAULT THAT RUNS ITSELF the core idea: the vault is the loop's state, not the chat window everything Kimi K3 knows lives in a .md file the loop: > capture - a thought lands in 00-inbox > context - K3 pulls links, tags, and neighbouring notes > draft - edits happen inside a git worktree, never the live vault > review - a critic agent checks the diff before anything ships > commit - appended to the vault, nothing gets rewritten the key insight: frontmatter fields like supports, contradicts, and supersedes are graph edges, not metadata - the note format is the write API start with a plain loop, it runs about 2-4x the cost of one direct call > only move to a full graph once state has to outlive the session, several agents need to coordinate, or you have to explain what changed - that jump can run 10-50x one review assistant climbed from 55% to 72% to 84% just by moving through these shapes in order

Mr. Buzzoni

10,680 Aufrufe • vor 1 Monat

CLAUDE + OBSIDIAN + LOOP ENGINEERING = A VAULT THAT RUNS ITSELF the core idea: the vault is the loop's state, not the chat window everything Claude knows lives in a .md file the loop: > capture - a thought lands in 00-inbox > context - claude pulls links, tags, and neighbouring notes > draft - edits happen inside a git worktree, never the live vault > review - a critic agent checks the diff before anything ships > commit - appended to the vault, nothing gets rewritten the key insight: frontmatter fields like supports, contradicts, and supersedes are graph edges, not metadata - the note format is the write API start with a plain loop, it runs about 2-4x the cost of one direct call > only move to a full graph once state has to outlive the session, several agents need to coordinate, or you have to explain what changed - that jump can run 10-50x one review assistant climbed from 55% to 72% to 84% just by moving through these shapes in order

CLAUDE + OBSIDIAN + LOOP ENGINEERING = A VAULT THAT RUNS ITSELF the core idea: the vault is the loop's state, not the chat window everything Claude knows lives in a .md file the loop: > capture - a thought lands in 00-inbox > context - claude pulls links, tags, and neighbouring notes > draft - edits happen inside a git worktree, never the live vault > review - a critic agent checks the diff before anything ships > commit - appended to the vault, nothing gets rewritten the key insight: frontmatter fields like supports, contradicts, and supersedes are graph edges, not metadata - the note format is the write API start with a plain loop, it runs about 2-4x the cost of one direct call > only move to a full graph once state has to outlive the session, several agents need to coordinate, or you have to explain what changed - that jump can run 10-50x one review assistant climbed from 55% to 72% to 84% just by moving through these shapes in order

Mr. Buzzoni

137,015 Aufrufe • vor 2 Monaten

THIS GUY BUILT A REAL JARVIS THAT TURNS HIS IDEAS INTO FINISHED PROJECTS ON ITS OWN, AND HE JUST SHOWED HOW THE WHOLE THING WORKS The whole system runs on one clean split he calls a blood-brain barrier. The second brain, his Obsidian vault, is only for things that aren't real yet. Ideas. Each one sits in a project-shaped folder, waiting to be processed and turned into something real. Nothing executes there. The vault is the place where ideas get shaped, not built. Once an idea is signed off, it crosses over to the execution pipeline. That lives on his actual machine, or an always-on box, or a Raspberry Pi, depending on what the project needs. Inside that machine is a fully Claude-native file system. The key piece is one CLAUDE.md file sitting in the root of his documents folder, acting as the map to everything in there. So he just opens Claude and says "go to my projects folder," and it already knows the whole structure, because that root file explains it. Two zones, one rule: the brain holds what isn't real, the machine runs what is. That separation is what keeps the ideas from tangling with the work. Bookmark this

THIS GUY BUILT A REAL JARVIS THAT TURNS HIS IDEAS INTO FINISHED PROJECTS ON ITS OWN, AND HE JUST SHOWED HOW THE WHOLE THING WORKS The whole system runs on one clean split he calls a blood-brain barrier. The second brain, his Obsidian vault, is only for things that aren't real yet. Ideas. Each one sits in a project-shaped folder, waiting to be processed and turned into something real. Nothing executes there. The vault is the place where ideas get shaped, not built. Once an idea is signed off, it crosses over to the execution pipeline. That lives on his actual machine, or an always-on box, or a Raspberry Pi, depending on what the project needs. Inside that machine is a fully Claude-native file system. The key piece is one CLAUDE.md file sitting in the root of his documents folder, acting as the map to everything in there. So he just opens Claude and says "go to my projects folder," and it already knows the whole structure, because that root file explains it. Two zones, one rule: the brain holds what isn't real, the machine runs what is. That separation is what keeps the ideas from tangling with the work. Bookmark this

Yarchi

87,650 Aufrufe • vor 3 Monaten

the agent failed while I was asleep and somehow the work still got finished that was the test I actually wanted i gave GPT-6 Astra a workflow that normally needed me between every step inbound came in messy one agent had to sort it, another find the missing context, another build the deliverable, and the last one check everything before it reached me somewhere in the middle, agent 2 got stuck the source it needed wasn’t there normally that kills the entire chain instead, it wrote the missing piece into a blocker file and passed everything else forward the other agents kept working when I came back, most of the pack was finished and the one thing they couldn’t solve was sitting separately waiting for me that felt more important than a perfect demo because an agent completing 10/10 tasks is impressive an agent failing without taking the other 9 down with it is infrastructure

the agent failed while I was asleep and somehow the work still got finished that was the test I actually wanted i gave GPT-6 Astra a workflow that normally needed me between every step inbound came in messy one agent had to sort it, another find the missing context, another build the deliverable, and the last one check everything before it reached me somewhere in the middle, agent 2 got stuck the source it needed wasn’t there normally that kills the entire chain instead, it wrote the missing piece into a blocker file and passed everything else forward the other agents kept working when I came back, most of the pack was finished and the one thing they couldn’t solve was sitting separately waiting for me that felt more important than a perfect demo because an agent completing 10/10 tasks is impressive an agent failing without taking the other 9 down with it is infrastructure

Lummox

19,046 Aufrufe • vor 20 Tagen

I STOPPED REBUILDING MY AGENT EVERY TIME A NEW MODEL SHIPS I used to rewrite the prompts, rewire the tools, redo the whole thing, then hope the new model behaved -> now I change one line in a config file and run the same folder again here's what's actually inside the folder that survives the swap: • the contract > harness.yaml - the whole harness, model is one line of it > SKILL.md - the task spec, loaded first > CONSTRAINTS.md - last week's corrections, every run > SCHEMA.md - the shape every return must match > aliases.csv - one company, one node • the hooks, five reflexes > pre_tool - blocks writes outside the allowlist > post_tool - rejects a bad schema on the spot > pre_send - holds drafts in a queue for me > on_fail - attaches the reason to the retry > post_run - appends the record, diffs the graph • the checks, outside the agent > - catches anything mechanical > reviewer.md - a second agent that never saw the work • the runner > fires at 02:00, one agent per node > stops at 40 verified nodes, or 3 passes with nothing new > capped at 300 agents and 2 retries • the state > 10-returns/ - one return per agent, checked before the graph > 212 last night, 9 rejected and retried once > 20-graph/ - merged only after the check. +41 nodes, +96 edges > 40-runs/ - append only, one record per run > queue/ - what pre_send is holding. one draft tonight • the edges > tools.allow - browser, fs, shell, search. the rest asks first > swap test.md - change the model line, run it again, read the diff 7 engineerings. 5 hooks. 0 orchestrators nothing in there is clever. every file exists because the model keeps changing and the folder doesn't the model is one line. the harness is yours

I STOPPED REBUILDING MY AGENT EVERY TIME A NEW MODEL SHIPS I used to rewrite the prompts, rewire the tools, redo the whole thing, then hope the new model behaved -> now I change one line in a config file and run the same folder again here's what's actually inside the folder that survives the swap: • the contract > harness.yaml - the whole harness, model is one line of it > SKILL.md - the task spec, loaded first > CONSTRAINTS.md - last week's corrections, every run > SCHEMA.md - the shape every return must match > aliases.csv - one company, one node • the hooks, five reflexes > pre_tool - blocks writes outside the allowlist > post_tool - rejects a bad schema on the spot > pre_send - holds drafts in a queue for me > on_fail - attaches the reason to the retry > post_run - appends the record, diffs the graph • the checks, outside the agent > - catches anything mechanical > reviewer.md - a second agent that never saw the work • the runner > fires at 02:00, one agent per node > stops at 40 verified nodes, or 3 passes with nothing new > capped at 300 agents and 2 retries • the state > 10-returns/ - one return per agent, checked before the graph > 212 last night, 9 rejected and retried once > 20-graph/ - merged only after the check. +41 nodes, +96 edges > 40-runs/ - append only, one record per run > queue/ - what pre_send is holding. one draft tonight • the edges > tools.allow - browser, fs, shell, search. the rest asks first > swap test.md - change the model line, run it again, read the diff 7 engineerings. 5 hooks. 0 orchestrators nothing in there is clever. every file exists because the model keeps changing and the folder doesn't the model is one line. the harness is yours

Mr. Buzzoni

10,901 Aufrufe • vor 22 Tagen

Creator of agent loops: "Anthropic also using my agent systems formula and still the biggest mistake in agents: is skipping Graphs" his 3 rules for every agent: rule 1 → loop it, don't run once - think, act, observe, repeat - cut the context and it forgets why it started rule 2 → an agent is memory + tools + reasoning - drop one and it breaks rule 3 → stop fine-tuning the model - the real alpha is the infrastructure around it the formula behind every AI agent - explained by the one who wrote it one agent → a loop → a graph of loops → a system that never forgets watch & bookmark - then read how to wire it into a graph ↓

Creator of agent loops: "Anthropic also using my agent systems formula and still the biggest mistake in agents: is skipping Graphs" his 3 rules for every agent: rule 1 → loop it, don't run once - think, act, observe, repeat - cut the context and it forgets why it started rule 2 → an agent is memory + tools + reasoning - drop one and it breaks rule 3 → stop fine-tuning the model - the real alpha is the infrastructure around it the formula behind every AI agent - explained by the one who wrote it one agent → a loop → a graph of loops → a system that never forgets watch & bookmark - then read how to wire it into a graph ↓

codila

23,915 Aufrufe • vor 2 Monaten

Over 90,000 Skills sitting inside Hermes Desktop is kind of insane!!!🤯 Did you know Hermes Desktop has a built-in Skills Hub with more than 90,000 Skills you can browse and add to an agent? And you can do it right from Desktop. Go to: Capabilities → Skills From there, open the Skills Hub under your installed Skills. You can: • search the catalog • browse by category or source • open any Skill to read what it does • review platform support, author, version, requirements, and docs • click + Add to this Agent to install it directly to the agent/profile you have selected That means if you want Hermes to get better at a specific type of work, you do not have to go hunting through repos or memorize install commands first. Just open the Hub, look through the catalog, inspect the Skill, and add it with one click. A lot of users still have no idea this is sitting inside Hermes Desktop.

Hermes Release Watch

68,830 Aufrufe • vor 1 Monat