Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Claude Code Head invented a word for what most config files aren't doing: tokenmaxxing. 90% of it lives in one place: ~/.claude/settings.json. 125 keys in v2.1.105. official docs cover 40. 4 of mine aren't anywhere in the docs. i audited the whole file - 18 settings actually decide what...

Mnilax's profile picture

Mnimiy

7,782 subscribers

83,304 Aufrufe • vor 1 Monat •via X (Twitter)

BildungWissenschaft & Technologie
LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Anthropic shipped 125 settings for Claude The official docs cover 40 One developer found the other 85 and his API bill dropped from $340 to $87 - not by using a cheaper model - not by writing shorter prompts just by moving one line in a config file to the right place > memory scoped per project → past clients never bleed into new work > Extended Thinking on Light by default → 18–25% fewer Opus tokens in week one > cache_control moved to the right line → the fix that turned a $340 bill into $87 > plugins and MCP servers toggled off when idle → saved 25–40K tokens per session > per-project model override → Haiku for docs, Sonnet for infra, Opus only where it matters most Claude users are running a $100/month tool at 30% of its actual capability
0:49

Anthropic shipped 125 settings for Claude The official docs cover 40 One developer found the other 85 and his API bill dropped from $340 to $87 - not by using a cheaper model - not by writing shorter prompts just by moving one line in a config file to the right place > memory scoped per project → past clients never bleed into new work > Extended Thinking on Light by default → 18–25% fewer Opus tokens in week one > cache_control moved to the right line → the fix that turned a $340 bill into $87 > plugins and MCP servers toggled off when idle → saved 25–40K tokens per session > per-project model override → Haiku for docs, Sonnet for infra, Opus only where it matters most Claude users are running a $100/month tool at 30% of its actual capability

Shadow Nick

379,589 Aufrufe • vor 1 Monat

I got curious how compaction works as a PM, so I did some brain surgery on Claude Code: (Anthropic's been doing really interesting work on context editing - they showed Claude Opus playing Settlers of Catan for 75+ minutes in a single thread by constantly editing the context instead of starting fresh. When I saw that Claude Code has a compaction command with optional custom instructions, I wanted to understand what's actually happening.) Abhishek Katiyar and Aman Khan gave me the key tip: Claude Code stores all your conversation history as text files on your computer. Open a new directory and give Claude Code a task. Here's how to watch compaction happening: 1. Go to your user's root directory 2. Press Command+Shift+Period (Mac) to show hidden folders 3. Navigate to ~/.claude/projects/ 4. Find your project folder and use Cursor/VSCode to open it (there's a reason) 5. Install the JSONL Gazelle plugin (open source, thank you Gabor Cselle!) 6. Open the most recent JSONL file - each row is a message in your conversation 7. Run the compact command in Claude Code with custom instructions 8. Watch what happens in the file What I learned: When you compact, Claude Code doesn't just summarize and delete everything. It creates a "compact boundary" in the conversation file, writes a summary of what happened before, but keeps the full original conversation (!!!!) The new thread can still retrieve any details from before compaction if needed. That is so damn cool. Why this matters: What you're getting in Claude Code is similar to what Anthropic ships in their developer SDK - so inspecting your daily tools is how you build real product intuition. The best way to understand AI systems is to open them up and look inside. Everything is text files.
10:52

I got curious how compaction works as a PM, so I did some brain surgery on Claude Code: (Anthropic's been doing really interesting work on context editing - they showed Claude Opus playing Settlers of Catan for 75+ minutes in a single thread by constantly editing the context instead of starting fresh. When I saw that Claude Code has a compaction command with optional custom instructions, I wanted to understand what's actually happening.) Abhishek Katiyar and Aman Khan gave me the key tip: Claude Code stores all your conversation history as text files on your computer. Open a new directory and give Claude Code a task. Here's how to watch compaction happening: 1. Go to your user's root directory 2. Press Command+Shift+Period (Mac) to show hidden folders 3. Navigate to ~/.claude/projects/ 4. Find your project folder and use Cursor/VSCode to open it (there's a reason) 5. Install the JSONL Gazelle plugin (open source, thank you Gabor Cselle!) 6. Open the most recent JSONL file - each row is a message in your conversation 7. Run the compact command in Claude Code with custom instructions 8. Watch what happens in the file What I learned: When you compact, Claude Code doesn't just summarize and delete everything. It creates a "compact boundary" in the conversation file, writes a summary of what happened before, but keeps the full original conversation (!!!!) The new thread can still retrieve any details from before compaction if needed. That is so damn cool. Why this matters: What you're getting in Claude Code is similar to what Anthropic ships in their developer SDK - so inspecting your daily tools is how you build real product intuition. The best way to understand AI systems is to open them up and look inside. Everything is text files.

Tal Raviv

57,910 Aufrufe • vor 6 Monaten

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
13:23

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 Aufrufe • vor 1 Monat

Boris Cherny, the creator of Claude Code at Anthropic, just explained why most people aren't getting real results from Claude in this talk he breaks down exactly how most people skipped the setup entirely: - 90% of code at Anthropic is written by Claude itself - the 14% you lose to CLAUDE.md before typing a word - lawyers, designers, and finance people are building real things with it - no CS degree. no background. nothing Boris Cherny: "Claude Code is 100% written by Claude Code, Cowork is 100% written by Claude Code" if you've been using Claude for months and never configured a single thing, you skipped the 20 steps that change everything. probably 25 instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed my breakdown of all 25 features is below
2:15

Boris Cherny, the creator of Claude Code at Anthropic, just explained why most people aren't getting real results from Claude in this talk he breaks down exactly how most people skipped the setup entirely: - 90% of code at Anthropic is written by Claude itself - the 14% you lose to CLAUDE.md before typing a word - lawyers, designers, and finance people are building real things with it - no CS degree. no background. nothing Boris Cherny: "Claude Code is 100% written by Claude Code, Cowork is 100% written by Claude Code" if you've been using Claude for months and never configured a single thing, you skipped the 20 steps that change everything. probably 25 instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed my breakdown of all 25 features is below

Khairallah AL-Awady

182,466 Aufrufe • vor 1 Monat

THIS GUY AUDITED 926 CLAUDE CODE SESSIONS AND FOUND MOST OF THE TOKEN WASTE WAS ON HIS SIDE everyone is blaming anthropic for the limits, so he decided to actually look at the data 858 sessions, 18,903 turns, and $1,619 estimated spend across 33 days here's what he found: 1\ one default setting was burning 14,000 tokens per turn Claude Code loads the full JSON schema for every tool into context at session start. whether you use them or not. 20,000 tokens of tool definitions sitting there on every single turn. the fix: one line in your settings.json "ENABLE_TOOL_SEARCH": "true" context dropped from 45K to 20K instantly. across 858 sessions that one setting was wasting an estimated 264 million tokens 2\ cache expiry is the single biggest waste 54% of his turns came after a 5+ minute idle gap. every one of those turns re-processed the entire conversation at full price which caused a 10x cost jump you go grab coffee. come back 5 minutes later. type your next message. everything rebuilds from scratch. the context didn't change. you didn't change. the cache just expired. 12.3 million tokens wasted on idle gaps alone 3\ 42 skills loaded. 19 of them used twice or less across 858 sessions. every one of those skill schemas sat in context on every turn eating tokens for nothing. 4\ 1,122 redundant file reads where the same file was read 3+ times one session read the same file 33 times. he ALSO built a full token auditor dashboard that shows you exactly where your waste is coming from 19 charts, opens in your browser, free AND open source
0:20

THIS GUY AUDITED 926 CLAUDE CODE SESSIONS AND FOUND MOST OF THE TOKEN WASTE WAS ON HIS SIDE everyone is blaming anthropic for the limits, so he decided to actually look at the data 858 sessions, 18,903 turns, and $1,619 estimated spend across 33 days here's what he found: 1\ one default setting was burning 14,000 tokens per turn Claude Code loads the full JSON schema for every tool into context at session start. whether you use them or not. 20,000 tokens of tool definitions sitting there on every single turn. the fix: one line in your settings.json "ENABLE_TOOL_SEARCH": "true" context dropped from 45K to 20K instantly. across 858 sessions that one setting was wasting an estimated 264 million tokens 2\ cache expiry is the single biggest waste 54% of his turns came after a 5+ minute idle gap. every one of those turns re-processed the entire conversation at full price which caused a 10x cost jump you go grab coffee. come back 5 minutes later. type your next message. everything rebuilds from scratch. the context didn't change. you didn't change. the cache just expired. 12.3 million tokens wasted on idle gaps alone 3\ 42 skills loaded. 19 of them used twice or less across 858 sessions. every one of those skill schemas sat in context on every turn eating tokens for nothing. 4\ 1,122 redundant file reads where the same file was read 3+ times one session read the same file 33 times. he ALSO built a full token auditor dashboard that shows you exactly where your waste is coming from 19 charts, opens in your browser, free AND open source

Om Patel

298,141 Aufrufe • vor 3 Monaten

Turn Claude Code into a Financial Analyst 🤖💹 In this video we point Claude Code at a bucket of 10k filing PDFs, and have it perform complex analysis across the entire set of docs! Claude Code doesn’t have file understanding out of the box (it kind of does, but it’s terrible / doesn’t work over long PDFs). We equipped Claude Code with targeted tools for file parsing and efficient search, courtesy of our recently released `semtools`. It’s way faster/more versatile than naive RAG 💡. You get super-fast in-mem keyword/semantic search, and Claude Code can combine this with standard file tools like grep and `Read` to load in dynamic context instead of fixed chunks. You can do this in seconds. Just install `semtools`, add it to your and point Claude to any bucket of files you want to analyze. SemTools (s/o Logan Markewich): File parsing courtesy of LlamaCloud:
0:35

Turn Claude Code into a Financial Analyst 🤖💹 In this video we point Claude Code at a bucket of 10k filing PDFs, and have it perform complex analysis across the entire set of docs! Claude Code doesn’t have file understanding out of the box (it kind of does, but it’s terrible / doesn’t work over long PDFs). We equipped Claude Code with targeted tools for file parsing and efficient search, courtesy of our recently released `semtools`. It’s way faster/more versatile than naive RAG 💡. You get super-fast in-mem keyword/semantic search, and Claude Code can combine this with standard file tools like grep and `Read` to load in dynamic context instead of fixed chunks. You can do this in seconds. Just install `semtools`, add it to your and point Claude to any bucket of files you want to analyze. SemTools (s/o Logan Markewich): File parsing courtesy of LlamaCloud:

Jerry Liu

32,804 Aufrufe • vor 10 Monaten

Stop what you're doing. Claude Opus 4.6 just released and it's incredible Both OpenClaw and Claude Code are 10x better with it It's now my daily driver for both In this video I cover EVERYTHING you need to know about Opus, and how to get the most out of it:
17:28

Stop what you're doing. Claude Opus 4.6 just released and it's incredible Both OpenClaw and Claude Code are 10x better with it It's now my daily driver for both In this video I cover EVERYTHING you need to know about Opus, and how to get the most out of it:

Alex Finn

71,388 Aufrufe • vor 5 Monaten

Anthropic engineers finally showed how they actually use Claude Code internally 31 minutes of internal workflow that most Claude users will never see on their own here's what they cover: > how to set up project context files the right way > custom commands that save hours of repeated work > hooks that make Claude behave exactly how you need > subagents and how to actually spec them properly "your agent isn't the problem, your spec is" the people who understand how Claude Code actually works inside Anthropic are shipping things everyone else thinks requires a whole team that's exactly why I put together a breakdown of Claude features most people have never discovered you can find it below
31:22

Anthropic engineers finally showed how they actually use Claude Code internally 31 minutes of internal workflow that most Claude users will never see on their own here's what they cover: > how to set up project context files the right way > custom commands that save hours of repeated work > hooks that make Claude behave exactly how you need > subagents and how to actually spec them properly "your agent isn't the problem, your spec is" the people who understand how Claude Code actually works inside Anthropic are shipping things everyone else thinks requires a whole team that's exactly why I put together a breakdown of Claude features most people have never discovered you can find it below

Anatoli Kopadze

309,983 Aufrufe • vor 1 Monat

Anthropic's CEO just explained on Lex Fridman how Claude actually works. 4 hours. free. with the CEO, the person who built Claude's character, and the founder of mechanistic interpretability. most people use Claude every day at maybe 10% of what it can actually do. this video is the other 90%. Save it. This will change the way you use Claude forever.
3:46:46

Anthropic's CEO just explained on Lex Fridman how Claude actually works. 4 hours. free. with the CEO, the person who built Claude's character, and the founder of mechanistic interpretability. most people use Claude every day at maybe 10% of what it can actually do. this video is the other 90%. Save it. This will change the way you use Claude forever.

Raytar

11,501 Aufrufe • vor 1 Monat

Claude Code creator: "100% of our pull requests at Anrtopic are run by Claude Code. 80–90% of code review too. The feature I’m using the most today is /loops. I’m not prompting Claude anymore - I’m building loops" in this interview he breaks down exactly how a system changes everything: - the memory and context features that turn Claude into a second brain - the knowledge architecture most users don't know Claude can build - the integration layer that connects Claude to your actual workflow - why typing one question at a time is the most expensive way to use Claude if you've been using Claude for months and still start every conversation from scratch with zero context, you don't have a Claude problem. you have a system problem instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed full guide in the article below
50:12

Claude Code creator: "100% of our pull requests at Anrtopic are run by Claude Code. 80–90% of code review too. The feature I’m using the most today is /loops. I’m not prompting Claude anymore - I’m building loops" in this interview he breaks down exactly how a system changes everything: - the memory and context features that turn Claude into a second brain - the knowledge architecture most users don't know Claude can build - the integration layer that connects Claude to your actual workflow - why typing one question at a time is the most expensive way to use Claude if you've been using Claude for months and still start every conversation from scratch with zero context, you don't have a Claude problem. you have a system problem instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed full guide in the article below

Khairallah AL-Awady

39,176 Aufrufe • vor 27 Tagen

instead of watching 2 hours of Netflix tonight, watch this Stanford lecture it's the clearest explanation I've seen of how ChatGPT and Claude actually work useful whether you've never touched AI in your life or have been using it every day for the past year I took the key ideas and turned them into a practical guide on how to actually get 100% out of Claude find it below
1:44:25

instead of watching 2 hours of Netflix tonight, watch this Stanford lecture it's the clearest explanation I've seen of how ChatGPT and Claude actually work useful whether you've never touched AI in your life or have been using it every day for the past year I took the key ideas and turned them into a practical guide on how to actually get 100% out of Claude find it below

Anatoli Kopadze

8,340,819 Aufrufe • vor 1 Monat

Boris Cherny, the creator of Claude Code at Anthropic, just listed 9 patterns that waste 73% of your tokens. in this podcast he breaks down exactly how the model burns tokens before it even reads your prompt: - the 14% you lose to CLAUDE.md before typing a word - the 13% you pay re-reading old chat history - the 11% from hooks you forgot you installed - why most "Claude got dumber" complaints are wrong if you're hitting Max limits more than once a week, you have at least 4 of these. Probably 7. instead of another show tonight, watch this. my own breakdown based on 400+ hours of usage is below, read it after the podcast
1:23:02

Boris Cherny, the creator of Claude Code at Anthropic, just listed 9 patterns that waste 73% of your tokens. in this podcast he breaks down exactly how the model burns tokens before it even reads your prompt: - the 14% you lose to CLAUDE.md before typing a word - the 13% you pay re-reading old chat history - the 11% from hooks you forgot you installed - why most "Claude got dumber" complaints are wrong if you're hitting Max limits more than once a week, you have at least 4 of these. Probably 7. instead of another show tonight, watch this. my own breakdown based on 400+ hours of usage is below, read it after the podcast

Mnimiy

1,377,315 Aufrufe • vor 2 Monaten

Here is a demo of the most comprehensive research agent for your code docs, powered by Nozomio Labs. It turns your indexed repos and docs into a dynamic tree that the agent can access on the fly, using SOTA tools to reduce code hallucinations. Now using the latest Anthropic model, Claude Opus 4.5.
0:35

Here is a demo of the most comprehensive research agent for your code docs, powered by Nozomio Labs. It turns your indexed repos and docs into a dynamic tree that the agent can access on the fly, using SOTA tools to reduce code hallucinations. Now using the latest Anthropic model, Claude Opus 4.5.

Arlan

28,405 Aufrufe • vor 7 Monaten

Introducing `claude-opus-to-haiku` ✍️ Get the quality of Claude 3 Opus, at a fraction of the cost and latency. Give one example of your task, and Claude 3 Opus will teach Haiku (60x cheaper!!) how to do the task perfectly. And it's open-source:
0:25

Introducing `claude-opus-to-haiku` ✍️ Get the quality of Claude 3 Opus, at a fraction of the cost and latency. Give one example of your task, and Claude 3 Opus will teach Haiku (60x cheaper!!) how to do the task perfectly. And it's open-source:

Matt Shumer

285,347 Aufrufe • vor 2 Jahren

instead of watching 2 hours of Netflix tonight, watch this 40-minute masterclass from the founder of a $20B China AI company it's the clearest explanation I've seen of how Agent Swarms and AI systems actually work at scale useful whether you've never built an agent in your life or have been using Claude every day for the past year I took the key ideas and turned them into a practical guide on how to actually build with Kimi find it below
39:17

instead of watching 2 hours of Netflix tonight, watch this 40-minute masterclass from the founder of a $20B China AI company it's the clearest explanation I've seen of how Agent Swarms and AI systems actually work at scale useful whether you've never built an agent in your life or have been using Claude every day for the past year I took the key ideas and turned them into a practical guide on how to actually build with Kimi find it below

Kirill

13,693,258 Aufrufe • vor 1 Monat

Anthropic shows this video to every new employee. Someone re-uploaded it. I hope Anthropic doesn't see this. 14 minutes of how the Claude team actually uses Claude in real work. I watched the recording last night and kept pausing it. Each time realizing I've been using Claude like a toy. claude.md + loops is what makes Claude stop fighting you and start working for you. Most people will keep using Claude the hard way.
15:14

Anthropic shows this video to every new employee. Someone re-uploaded it. I hope Anthropic doesn't see this. 14 minutes of how the Claude team actually uses Claude in real work. I watched the recording last night and kept pausing it. Each time realizing I've been using Claude like a toy. claude.md + loops is what makes Claude stop fighting you and start working for you. Most people will keep using Claude the hard way.

Raytar

255,077 Aufrufe • vor 17 Tagen

Boris Cherny, the creator of Claude Code at Anthropic, just explained why he stopped prompting Claude entirely in this talk he breaks down exactly how the future is teams of agents, not better prompts: - the 14% you lose to CLAUDE.md before typing a word - the features that change how Claude thinks before you type a word - the features most Claude users don't know exist - why typing prompts one at a time is already the slow lane Boris Cherny: "Now I don’t prompt Claude anymore - I have loops that are running. My job is to write loops." if you've been using Claude for more than a month and never left the chat window, you have at least 23 untouched features. probably 25 instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed my breakdown of all 25 features is below
29:10

Boris Cherny, the creator of Claude Code at Anthropic, just explained why he stopped prompting Claude entirely in this talk he breaks down exactly how the future is teams of agents, not better prompts: - the 14% you lose to CLAUDE.md before typing a word - the features that change how Claude thinks before you type a word - the features most Claude users don't know exist - why typing prompts one at a time is already the slow lane Boris Cherny: "Now I don’t prompt Claude anymore - I have loops that are running. My job is to write loops." if you've been using Claude for more than a month and never left the chat window, you have at least 23 untouched features. probably 25 instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed my breakdown of all 25 features is below

Khairallah AL-Awady

102,529 Aufrufe • vor 1 Monat

We're excited to announce duckdb-skills, a DuckDB plugin for Claude Code! We think the embedded nature of DuckDB makes it a perfect companion for Claude in your local workflows. The skills supported include: + read-file and query – uses DuckDB's CLI to query data locally, unlocking easy access to any file that DuckDB can read. + read-memories – a clever idea to store your Claude memories in DuckDB and query them at blazing speed. These are powered by two additional skills: + attach-db – gives Claude a mechanism to manage DuckDB state through a .sql file linked to your project. + duckdb-docs – uses a remote DuckDB full-text search database to query the DuckDB docs and answer all of your (and Claude's own) questions.
2:16

We're excited to announce duckdb-skills, a DuckDB plugin for Claude Code! We think the embedded nature of DuckDB makes it a perfect companion for Claude in your local workflows. The skills supported include: + read-file and query – uses DuckDB's CLI to query data locally, unlocking easy access to any file that DuckDB can read. + read-memories – a clever idea to store your Claude memories in DuckDB and query them at blazing speed. These are powered by two additional skills: + attach-db – gives Claude a mechanism to manage DuckDB state through a .sql file linked to your project. + duckdb-docs – uses a remote DuckDB full-text search database to query the DuckDB docs and answer all of your (and Claude's own) questions.

DuckDB

60,605 Aufrufe • vor 3 Monaten

Everyone's sleeping on MiniMax. Again. They just shipped M3. The first open-weights model to combine frontier coding, 1M context, and native multimodality in one drop. I plugged it into Claude Code this morning. Pasted a design from Dribbble. Watched M3 write production-ready React code in one session. At the agency, I just replaced Opus 4.8 with M3 for 80% of our coding tasks. The output is the same and we are running everything at a fraction of the cost. Open infrastructure is the future.
1:35

Everyone's sleeping on MiniMax. Again. They just shipped M3. The first open-weights model to combine frontier coding, 1M context, and native multimodality in one drop. I plugged it into Claude Code this morning. Pasted a design from Dribbble. Watched M3 write production-ready React code in one session. At the agency, I just replaced Opus 4.8 with M3 for 80% of our coding tasks. The output is the same and we are running everything at a fraction of the cost. Open infrastructure is the future.

Prajwal Tomar

12,904 Aufrufe • vor 1 Monat

Get ready to start talking to your Google Docs. With Docs Live, you’ll be able to workshop docs and projects in a freewheeling conversational way, instead of a series of hyper-specific instructional prompts. Take a look at the demo from #GoogleIO 👀
1:40

Get ready to start talking to your Google Docs. With Docs Live, you’ll be able to workshop docs and projects in a freewheeling conversational way, instead of a series of hyper-specific instructional prompts. Take a look at the demo from #GoogleIO 👀

TechCrunch

13,611 Aufrufe • vor 1 Monat