正在加载视频...

视频加载失败

Finally! A RAG over code solution that actually works (open-source). Naive chunking used in RAG isn't suited for code. This is because codebases have long-range dependencies, cross-file references, etc., that independent text chunks just can't capture. Graph-Code is a graph-driven RAG system that solves this. It analyzes the Python...

121,874 次观看 • 1 年前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Claude Code + Google Stitch 2.0 is f*cking cracked 🤯 Google just dropped a free AI design agent that solves Claude Code's biggest weakness: frontend design. One screenshot of a high-converting landing page → a production-ready site for your brand in minutes. All inside Google Stitch + Claude Code. Perfect for DTC brands and agencies who are building advertorial pages and product launch pages for Meta but burning days on designer back-and-forth. If you're running Meta ads and need 5-10 different landing pages testing different hooks, angles, and offers — each one targeting a different audience and pain point — you know the bottleneck isn't the ads. It's the pages. Briefing designers, waiting for revisions, paying $2-5K per page. Stitch eliminates the design bottleneck: → Find a high-converting advertorial that's scaling on Meta → Screenshot it and drop it into Stitch (powered by Gemini 3.1) → Stitch redesigns it with your brand's colors, fonts, and imagery using Nano Banana 2 → Edit sections visually — headlines, CTAs, layouts — without touching code → Export the code and paste it into Claude Code → Claude builds the full production site and deploys to Vercel or Netlify in 60 seconds No designer. No $3K per landing page. No Claude Code frontend that looks like a template from 2019. What you get: → Designer-quality landing pages and advertorials built in minutes, not weeks → Visual editing so you actually see the design before you code it → Nano Banana 2 generating on-brand product imagery and hero shots → A repeatable system — new angle, new page, same pipeline Built 100% with Google Stitch 2.0 + Claude Code. I put together a full playbook showing the exact workflow: how to find winning pages, redesign them in Stitch, and deploy with Claude Code. Want it for free? > Like this post > Comment "STITCH" And I'll send it over (must be following so I can DM)

Mike Futia

125,653 次观看 • 4 个月前

HERMES AGENT HAS A SECOND BRAIN. 1,100+ KNOWLEDGE FILES. AUTO-LINKED. SELF-IMPROVING. GROWING EVERY NIGHT. THIS IS THE OBSIDIAN GRAPH BEHIND IT. every dot = one knowledge file (markdown) every line = one wiki-link between files every color = one category (skills, notes, decisions, sources, entities) HOW IT BUILDS ITSELF: Hermes ships with a bundled LLM Wiki skill. based on Andrej Karpathy's pattern. unlike RAG (rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. when you feed the agent a source: → it reads the content → writes a structured markdown page → auto-links to every related existing page → flags contradictions with previous entries → updates all affected pages one source in. multiple connections created. the graph grows denser with every entry. WHAT FEEDS THE WIKI: → articles and URLs you find interesting → meeting transcripts → PDF documents and research papers → conversation history from Hermes sessions → Claude Code and Codex session history → Slack logs, email threads, saved notes → YouTube transcripts → raw text dropped into a _raw/ folder the obsidian-wiki package supports multi-agent ingest from Hermes, Claude Code, Codex, OpenClaw, Pi, Windsurf, and ChatGPT exports. install: pip install obsidian-wiki obsidian-wiki setup --vault ~/wiki AUTOMATE THE GROWTH: set cron jobs to feed the wiki overnight: "every day at 9am, check for new meetings. ingest transcripts into the wiki." "every week, check arXiv for new papers in [niche]. summarize and file into the wiki." "every day, ingest today's Hermes sessions into the wiki under session-history." month 1: 50 entries. scattered. month 3: 300+ entries. cross-referenced. month 6: 1,000+ entries. the agent surfaces patterns you never searched for. WHY OBSIDIAN: the wiki is plain markdown files. no database. no lock-in. open it in Obsidian for graph view: → nodes show knowledge density → links show how ideas connect → clusters reveal your strongest domains → orphan nodes reveal gaps Hermes writes from a VPS. Obsidian reads on your laptop. obsidian-headless syncs without a GUI. agent writes from the server, you browse on your device. FOUR MEMORY LAYERS: Layer 1: memory.md + user.md (~2,200 + 1,375 chars. short-term.) Layer 2: SQLite with FTS5 (full session transcripts. searchable.) Layer 3: external providers (Mem0, SuperMemory, Honcho. optional.) Layer 4: Obsidian wiki via LLM Wiki skill (unlimited. compounding. the long-term brain.) layers 1-3 handle memory. layer 4 handles knowledge. the graph in this post is layer 4. SETUP: set in Desktop app, Dashboard, or config.yaml: WIKI_PATH=~/wiki OBSIDIAN_VAULT_PATH=~/wiki first run: Hermes asks for your domain. answer with your niche. the skill builds SCHEMA.md with tag taxonomy. after that: "index this into my wiki: [URL or text]" the wiki grows. the graph densifies. the agent gets smarter because the knowledge base got smarter. full 15 levels breakdown in the article 👇

YanXbt

34,368 次观看 • 26 天前