正在加载视频...

视频加载失败

Introducing Supersonic. It's a terminal-first CRM that you use through Claude Code. It updates itself from emails, builds a knowledge graph, and has agentic Skills and Recipes.

77,366 次观看 • 5 个月前 •via X (Twitter)

0 条评论

暂无评论

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

相关视频

Claude Code is a major (and accidental!) hit for Anthropic that surprised even its creator, Boris Cherny. Claude Code, an Agentic AI coding product that lives in the terminal. Most of the new code at Anthropic is created through it today. And in the last 5 months since it was launched publicly, Claude Code went from $0 to $400M in revenue run rate (as per The Information). 00:00 – Intro 01:15 – Did You Expect Claude Code’s Success? 04:22 – How Claude Code Works and Origins 08:05 – Command Line vs IDE: Why Start Claude Code in the Terminal? 11:31 – The Evolution of Programming: From Punch Cards to Agents 13:20 – Product Follows Model: Simple Interfaces and Fast Evolution 15:17 – Who Is Claude Code For? (Engineers, Designers, PMs & More) 17:46 – What Can Claude Code Actually Do? (Actions & Capabilities) 21:14 – Agentic Actions, Subagents, and Workflows 25:30 – Claude Code’s Awareness, Memory, and Knowledge Sharing 33:28 – Model Context Protocol (MCP) and Customization 35:30 – Safety, Human Oversight, and Enterprise Considerations 38:10 – UX/UI: Making Claude Code Useful and Enjoyable 40:44 – Pricing for Power Users and Subscription Models 43:36 – Real-World Use Cases: Debugging, Testing, and More 46:44 – How Does Claude Code Transform Onboarding? 49:36 – The Future of Coding: Agents, Teams, and Collaboration 54:11 – The AI Coding Wars: Competition & Ecosystem 57:27 – The Future of Coding as a Profession 58:41 – What’s Next for Claude Code

Matt Turck

82,161 次观看 • 1 年前

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

55,345 次观看 • 2 个月前