Загрузка видео...

Не удалось загрузить видео

На главную

I truly don't understand why nobody is using this setup graphify, a tool that turns any folder into a knowledge graph your agent can query, just passed 126k stars on github and got into Y Combinator. people stopped asking ai questions. they're giving it a desk, a memory and...

101,881 просмотров • 3 дней назад •via X (Twitter)

Комментарии: 28

Фото профиля Deniss
Deniss2 дней назад

the graphify + CLAUDE.md memory folder is the part that actually sticks. without it you still start from zero every session. how stable has the morning routine been for you so far?

Фото профиля kiosa
kiosa2 дней назад

That why it needs optimization

Фото профиля tim777
tim7773 дней назад

persistent memory is the actual unlock

Фото профиля kiosa
kiosa2 дней назад

Using it myself too

Фото профиля Mnimiy
Mnimiy2 дней назад

i know what ill do todays evening

Фото профиля kiosa
kiosa2 дней назад

Hah same here

Фото профиля siyuan liu | AI编程实践
siyuan liu | AI编程实践3 дней назад

Giving the agent a queryable folder graph beats paste-the-readme every session. We've been pushing structure into CLAUDE.md + a local memory file for the same reason — once the desk exists, questions get shorter and answers stay grounded.

Фото профиля kiosa
kiosa3 дней назад

Exactly ma friend

Фото профиля Asteri
Asteri3 дней назад

Thanks for sharing

Фото профиля kiosa
kiosa2 дней назад

Welcome bro

Фото профиля Гандьо
Гандьо2 дней назад

I am using it plus obsidian

Фото профиля Shukshin
Shukshin2 дней назад

The real upgrade is persistent memory plus controlled access to tools, not just connecting more integrations. But email, browser actions, and scheduled jobs need strict permissions and a reliable approval layer before this becomes something you can safely leave running.

Фото профиля kiosa
kiosa2 дней назад

Agree

Фото профиля Atlas
Atlas2 дней назад

the goal isn't just an agent that remembers, it's one that can show its work

Фото профиля Bober_smart
Bober_smart2 дней назад

I felt like trying to use this

Фото профиля kiosa
kiosa2 дней назад

Using it already

Фото профиля Marcel Velica
Marcel Velica2 дней назад

Giving AI a structured knowledge base instead of relying on isolated prompts can make a huge difference. Persistent context is what makes agents genuinely useful for complex work.

Фото профиля kiosa
kiosa2 дней назад

This is the way

Фото профиля Mikadzyki🌙
Mikadzyki🌙3 дней назад

what a gem

Фото профиля kiosa
kiosa2 дней назад

Likewise

Фото профиля Diam
Diam2 дней назад

Having the drafts ready but unsent is the bit I like. You save the preparation time without handing over the send button.

Фото профиля kiosa
kiosa2 дней назад

Doing it too

Фото профиля 安叫兽|Bird🕊️ 🔶 BNB
安叫兽|Bird🕊️ 🔶 BNB2 дней назад

图谱画出来容易,后面文件改了能自动跟上吗

Фото профиля kiosa
kiosa2 дней назад

Easy

Фото профиля swapcherry
swapcherry2 дней назад

the setup alone is a job

Фото профиля Chen
Chen2 дней назад

126k github stars and no one's using it? half those stars are just bookmarked for later.

Фото профиля Nguyễn Chí Trọng Nghĩa
Nguyễn Chí Trọng Nghĩa2 дней назад

Biến một thư mục thành đồ thị tri thức để tác tử tra cứu là hướng hay: bộ nhớ có cấu trúc giúp trả lời đúng ngữ cảnh hơn là hỏi đáp rời rạc. Bạn nghĩ chi phí cập nhật đồ thị khi dữ liệu đổi thì sao?

Фото профиля Vipul Kumar Kewat
Vipul Kumar Kewat2 дней назад

I love how creative people are getting with these tools.

Похожие видео

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this

Yarchi

56,568 просмотров • 4 месяцев назад

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 просмотров • 4 месяцев назад

this is f*cking gold 20 GitHub repos with 500K+ combined stars that will level up your JEV workflow AGENTS > jev-ultrafast: Jev picks every click and DOM target, a small LLM only types > hermes-jev-skills: routing, memory, compaction and skill picks in one pack > typesafe-computer-use: OCR reads your Mac screen, Jev picks the next click MEMORY > fast-jev-compaction: scores every tool call keep, truncate or drop instead of summarizing > jevmem: project memory for Claude Code, Cursor and Codex, updated every turn > jev-second-brain: your Obsidian vault, Jev judges which notes duplicate, revise or contradict SAFETY > jev-guard: a gate before every tool call, Jev scores the risk, you set allow, ask or deny TOOLS > skills: the official TypeSafe skill for Claude Code and Codex > system-one-adapter-python: dry-run your questions on an ordinary LLM before you burn a Jev key > jev-mcp: claim checks, screening and ranking as MCP tools > typesafe-mcp: plug Jev into any MCP client > json-render: Vercel's generative UI, where Jev picks the components OPEN MODELS > SemIf-OpenJev: semantic ifs from frozen open models kev: Jev-like models on Qwen that run on your MacBook > laya-mlx: the Laya decision engine on Apple silicon > clm: an open System One model with Choice, Noul and Score > jevlike: train your own Jev-like model TRADING > jev-trader: one buy or sell decision per Monad block START HERE > awesome-jev: the biggest map of everything built on Jev > awesome-jev-by-typesafe: use cases, patterns and starter code bookmark it before your next build

NO1ennn

18,445 просмотров • 21 дней назад

install these before your next long Claude Code session if your Opus 5.5 bill hurts and you don’t know where to start, copy this: claude-code-router: sits in front of Claude Code and sends each request to the cheapest model that can do it. Haiku does the grep, Opus only gets the hard part. 37k stars rtk: shrinks test, build and git output before the model sees it. one binary, up to 90% less bash output in your context. 83k stars claude-mem: remembers what happened in your past sessions and feeds back only the relevant part, so you stop paying to re-explain your project every morning. 100k stars context-mode: a huge tool output goes into a local database instead of your context window, and Claude pulls out only the lines it needs. 18k stars caveman: makes Claude answer in short telegraphic sentences. code stays identical, and output is the expensive side on Opus 5.5 ($20 per million). 51k stars token-optimizer: a local dashboard that shows where your tokens actually went, and keeps your work alive across compactions. 1.9k stars token-savior: replaces whole-file reads with symbol lookups, so Claude reads the function and not the 2,000 lines around it code-review-graph: maps your repo as a graph and gives Claude only the code connected to the change you’re reviewing jev-ultrafast: a browser agent where Jev picks every click, and a text model wakes up only when something has to be typed. 16,758 stars none of them makes Opus smarter. every one stops it from paying for work it never needed to do the full setup with scripts is in the article. do the measuring step first, so you know what you actually saved

rvaniaaa

23,217 просмотров • 5 дней назад