正在加载视频...

视频加载失败

> downloaded Claude Code > thought it was just another AI chatbot > opened it up > found a chat bar > typed a prompt > nothing happened to my files > realized the difference > browser AI waits for you to bring your files > Claude Code goes...

20,710 次观看 • 6 个月前 •via X (Twitter)

19 条评论

Cheezehead Club 的头像
Cheezehead Club3 个月前

Yo, that’s some wild tech you got there. 🎉 Claude Code’s like a sneaky cheese thief in your files, ready to serve up the goods! 🧀🔥 Keep sharing, we eat this up!

Adonys 的头像
Adonys6 个月前

claude is the ultimate intern fr

Blum 的头像
Blum6 个月前

definitely so, Adonys

Harry Tandy 的头像
Harry Tandy6 个月前

the folder is the workspace, CLAUDE.md is the briefing, and PDFs/transcripts/Excel files stop being dead assets once Claude Code can read them in place

Blum 的头像
Blum6 个月前

spot on, you totally got the point, Harry!

John 的头像
John6 个月前

Claude Code is likely the strongest choice for research work these days

Blum 的头像
Blum6 个月前

absolutely agree, Сlaude has really pulled ahead of the other players in this direction rn

helicerat 的头像
helicerat6 个月前

the 6 hours before the real work starts is what kills most research sessions

Blum 的头像
Blum6 个月前

exactly, it’s a painful and tedious process that scares off many people, and claude frees us from it

Alpha Batcher 的头像
Alpha Batcher6 个月前

the shift is from you bringing files to the tool reading the folder itself

Blum 的头像
Blum6 个月前

yep, and this is genuinely convenient

LifGenii Inc. 的头像
LifGenii Inc.5 个月前

Claude Code is one of those products that only clicks once you point it at a real project instead of a blank prompt.

Celes 🦋 的头像
Celes 🦋3 个月前

agents that actually reduce workflow friction are the ones that matter

HashRaX 的头像
HashRaX4 个月前

people are still stuck copy pasting into browser tabs while this is actually sitting in the folder doing the work, absolute game changer

EchoTrade 的头像
EchoTrade5 个月前

Utimate knowladge What was your first thought after watching it?

Alex 的头像
Alex6 个月前

AI becomes way more useful once it understands your actual workflow

duhao 的头像
duhao5 个月前

yeah, that folder shift is huge

Mastermind Ape 的头像
Mastermind Ape5 个月前

this is very cool👍

Lyra 的头像
Lyra3 个月前

AI workflows are shifting from chat to actual task execution

相关视频

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 个月前

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

24,787 次观看 • 23 天前

STOP BURNING YOUR OPUS 5.5 LIMIT FOR NOTHING these 8 repos cut what Claude reads, writes and re-reads. copy the list before your next long session: headroom: shrinks tool output, logs and files before they reach the model, and keeps the originals so Claude can pull them back when it needs them. 75k stars claude-context: semantic search over your whole codebase, so Claude fetches the relevant snippets and doesn’t read whole files to find them. 12k stars lean-ctx: a local layer that compresses file reads and shell output. a file Claude already read costs about 13 tokens the second time. 3.8k stars openwolf: hooks that keep a project index and session notes, so Claude skips files it already read and doesn’t lose its work at compaction. 2.1k stars claude-token-efficient: one CLAUDE.md that keeps answers short. nothing to install, and output is the $20-per-million side of Opus 5.5. 6.1k stars jcodemunch-mcp: indexes the repo once, then Claude asks for one function and gets just that. it claims 95% less code reading. 2.5k stars ccusage: reads your local Claude Code logs and shows tokens and cost by day and by session. 19k stars Claude-Code-Usage-Monitor: live usage bars and a forecast of when you’ll hit your limit. 8.6k stars none of them makes Opus better. each one just stops it from paying for tokens it didn’t need start with the last two: see where your limit actually goes, then pick two tools from the top. the full setup with scripts is in the article

rvaniaaa

12,381 次观看 • 21 天前

Obsidian + Claude Code turned a 4,300-note vault into a second brain that answers back. Most people use Obsidian as a graveyard. You save 40 highlights a week, link nothing, and reread maybe 2% of it. The knowledge is there the retrieval is dead. Claude Code fixes the retrieval, because your vault is just a folder of markdown files and Claude Code lives in folders. The whole setup takes 20 minutes: Open a terminal inside your Obsidian folder and run Claude Code no plugins, no API glue, no export step. It reads all 4,300 files natively. Then drop a CLAUDE.md at the vault root explaining your structure: where daily notes live, how you tag, what your MOCs are. Now every session starts with context instead of chaos. From there you just talk to your vault: > "find every note where I mentioned churn and write a summary with backlinks" > "read my last 30 daily notes and list the 5 ideas I keep circling but never ship" > "build a MOC for everything tagged startup-ideas and link the orphan notes into it" It writes new notes straight into the vault with proper [[wikilinks]], and they show up in your graph view 10 seconds later. The boring layer automates too one command cleans broken links, one merges duplicates, one turns 6 months of meeting notes into a single decisions log. Work that used to eat a Sunday now runs while you make coffee. Before: 4,300 notes, 900 orphans, search by keyword and prayer. After: an agent that read everything you ever wrote and drafts in your own voice, from your own sources, with receipts. People pay $30/month for AI note apps with 10% of this. You already own the other 90%. Your notes stopped being storage. They started being staff.

Spike 1%

18,223 次观看 • 3 个月前