Loading video...

Video Failed to Load

Go Home

someone just rebuilt claude code in pure python and made it 230x cheaper to run it's called clawcodex. a full from-scratch port of the claude code agent loop. 230k+ lines of python, MIT licensed it keeps your request prefix byte-stable, so DeepSeek's prompt cache covers your entire system +...

alextalksai's profile picture

alex

31,035 subscribers

158,729 views • 12 days ago •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Peter Steinberger Quietly Started A Shift That Makes Claude 35x Cheaper To Run The way Claude Code talks to tools matters more than people think. Most use MCP, and it quietly eats tokens, it loads everything into context every time, even tools you never call. One benchmark: MCP burned 35x more tokens than a CLI on the same task. Peter Steinberger, the OpenClaw guy, got annoyed by this and started building lean CLIs himself. That kicked off a tool called Printing Press. You point Claude Code at any website, even ones with no API like ESPN or Craigslist, and it builds a small command tool for it in about 10 minutes. In one demo, a request pulled 132,000 tokens of raw data, but the tool processed it locally and only handed Claude a 2,000-token summary. The rest never touched the context window. It also comes with ~50 ready-made tools you can grab right away. To start, point Claude Code at the links from and ask it to set it up. Bookmark this.
14:45

Peter Steinberger Quietly Started A Shift That Makes Claude 35x Cheaper To Run The way Claude Code talks to tools matters more than people think. Most use MCP, and it quietly eats tokens, it loads everything into context every time, even tools you never call. One benchmark: MCP burned 35x more tokens than a CLI on the same task. Peter Steinberger, the OpenClaw guy, got annoyed by this and started building lean CLIs himself. That kicked off a tool called Printing Press. You point Claude Code at any website, even ones with no API like ESPN or Craigslist, and it builds a small command tool for it in about 10 minutes. In one demo, a request pulled 132,000 tokens of raw data, but the tool processed it locally and only handed Claude a 2,000-token summary. The rest never touched the context window. It also comes with ~50 ready-made tools you can grab right away. To start, point Claude Code at the links from and ask it to set it up. Bookmark this.

Ridark

32,351 views • 1 month ago

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 views • 2 months ago

THE GUY WHO WON ANTHROPIC'S HACKATHON JUST GAVE AWAY HIS ENTIRE CLAUDE CODE PLAYBOOK FOR FREE. 10 MONTHS OF WORK, ALL PUBLIC Affaan Mustafa won the Anthropic x Forum Ventures hackathon by building a full startup in 8 hours with Claude Code. Then he open-sourced the exact setup that did it. It's called Everything Claude Code, and it turns Claude from one assistant into an entire engineering team Repo: affaan-m/ecc This isn't a prompt pack. It's a system he refined over 10+ months of daily use shipping real products What's inside: A huge library of skills, dozens of specialized subagents, and ready-made commands, all working together. Each piece does one job. One subagent reviews security against OWASP standards. One optimizes memory so Claude stops forgetting earlier decisions around hour three. One learns from your past sessions and projects so the setup gets smarter the more you use it. Others handle planning, test-driven development, and language-specific code review Instead of one assistant writing code, you get an orchestrated team. A main session delegates to the right specialist when the task calls for it, the way a real dev team splits work The best part: it's not locked to one tool. It runs in Claude Code, Cursor, Codex and OpenCode, across Windows, Mac and Linux. Free, MIT licensed This is the difference between using Claude like a search box and running it like a team that ships. The guy spent 10 months figuring out what actually works so you don't have to Bookmark this
9:32

THE GUY WHO WON ANTHROPIC'S HACKATHON JUST GAVE AWAY HIS ENTIRE CLAUDE CODE PLAYBOOK FOR FREE. 10 MONTHS OF WORK, ALL PUBLIC Affaan Mustafa won the Anthropic x Forum Ventures hackathon by building a full startup in 8 hours with Claude Code. Then he open-sourced the exact setup that did it. It's called Everything Claude Code, and it turns Claude from one assistant into an entire engineering team Repo: affaan-m/ecc This isn't a prompt pack. It's a system he refined over 10+ months of daily use shipping real products What's inside: A huge library of skills, dozens of specialized subagents, and ready-made commands, all working together. Each piece does one job. One subagent reviews security against OWASP standards. One optimizes memory so Claude stops forgetting earlier decisions around hour three. One learns from your past sessions and projects so the setup gets smarter the more you use it. Others handle planning, test-driven development, and language-specific code review Instead of one assistant writing code, you get an orchestrated team. A main session delegates to the right specialist when the task calls for it, the way a real dev team splits work The best part: it's not locked to one tool. It runs in Claude Code, Cursor, Codex and OpenCode, across Windows, Mac and Linux. Free, MIT licensed This is the difference between using Claude like a search box and running it like a team that ships. The guy spent 10 months figuring out what actually works so you don't have to Bookmark this

Yarchi

814,590 views • 2 months ago

Boris Cherny, Head of Claude Code at Anthropic: "I do not prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops." The person who built the most used AI coding tool stopped prompting entirely. Most people using it every day are still typing one request at a time. This Github repo changes that. ↳ Seven production loop patterns with real token cost estimates ↳ CLI that scaffolds your entire loop in five minutes ↳ Starters for Grok, Claude Code, Codex, and Opencode The repo gives you the framework. My article covers the mental shift that makes it actually work.
0:31

Boris Cherny, Head of Claude Code at Anthropic: "I do not prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops." The person who built the most used AI coding tool stopped prompting entirely. Most people using it every day are still typing one request at a time. This Github repo changes that. ↳ Seven production loop patterns with real token cost estimates ↳ CLI that scaffolds your entire loop in five minutes ↳ Starters for Grok, Claude Code, Codex, and Opencode The repo gives you the framework. My article covers the mental shift that makes it actually work.

Kanika

20,576 views • 22 days ago

THE GUY RUNNING CLAUDE CODE AT ANTHROPIC JUST SAID HE DOESN’T PROMPT AI ANYMORE. He writes loops. That’s a huge difference. A prompt tells Claude what to do once. A loop gives Claude a goal. Then Claude keeps checking its own work… Finding mistakes. Writing its next prompt. Trying again. Over and over… Until it actually reaches the target you defined. But here’s what most people miss. A loop is only as smart as the context you give it. That’s exactly why Claude Repositories matter. I broke down how to connect your entire codebase so Claude can actually reason across your project instead of a single file. Full guide below
1:36

THE GUY RUNNING CLAUDE CODE AT ANTHROPIC JUST SAID HE DOESN’T PROMPT AI ANYMORE. He writes loops. That’s a huge difference. A prompt tells Claude what to do once. A loop gives Claude a goal. Then Claude keeps checking its own work… Finding mistakes. Writing its next prompt. Trying again. Over and over… Until it actually reaches the target you defined. But here’s what most people miss. A loop is only as smart as the context you give it. That’s exactly why Claude Repositories matter. I broke down how to connect your entire codebase so Claude can actually reason across your project instead of a single file. Full guide below

kiosa

16,808 views • 1 month ago

Complete Claude Code Training 6 HOURS. The most comprehensive Claude training on the internet. From A to Z: setup, workflow creation, website deployment, agent team creation, browser automation, client prospecting and pricing your services. All of it without writing a single line of code. In the end: you use Claude Code like a pro and you monetize your skills. Beginner or advanced, everything is there in one place, this course covers it all. It's worth more than all those $500 courses you almost bought. Keep it bookmarked and watch later.
5:59:20

Complete Claude Code Training 6 HOURS. The most comprehensive Claude training on the internet. From A to Z: setup, workflow creation, website deployment, agent team creation, browser automation, client prospecting and pricing your services. All of it without writing a single line of code. In the end: you use Claude Code like a pro and you monetize your skills. Beginner or advanced, everything is there in one place, this course covers it all. It's worth more than all those $500 courses you almost bought. Keep it bookmarked and watch later.

Rahul

242,725 views • 2 months ago

If you use Claude Code, install this immediately. It's called Claude Code Templates. It adds an entire ecosystem of AI tools to Claude. Here's what you get: 1. Agent Teams Visual dashboards showing how multiple AI agents collaborate on code. 2. Specialized Agents Front-end developers, backend engineers, QA testers, marketers. 3. MCP Integrations Connect Claude to external tools and workflows. 4. Real-Time Monitoring Track AI development sessions and performance analytics. 5. Automation Scheduling Run tasks automatically every day. Example: You can schedule an agent team to run daily at 5AM. It researches trends, generates content, and builds workflows. All automatically. The best part? Everything is free and open source.
9:25

If you use Claude Code, install this immediately. It's called Claude Code Templates. It adds an entire ecosystem of AI tools to Claude. Here's what you get: 1. Agent Teams Visual dashboards showing how multiple AI agents collaborate on code. 2. Specialized Agents Front-end developers, backend engineers, QA testers, marketers. 3. MCP Integrations Connect Claude to external tools and workflows. 4. Real-Time Monitoring Track AI development sessions and performance analytics. 5. Automation Scheduling Run tasks automatically every day. Example: You can schedule an agent team to run daily at 5AM. It researches trends, generates content, and builds workflows. All automatically. The best part? Everything is free and open source.

Julian Goldie SEO

107,310 views • 5 months ago

AMD'S NEW MINI PC RUNS CLAUDE CODE OFFLINE FOR $0/MONTH AND REPLACES $200 OPENAI + $200 CLAUDE CODE SUBSCRIPTIONS amd's ryzen ai max+ 395 is the first x86 chip that runs a 200 billion parameter model on a single piece of silicon with 128gb of unified memory the gmktec evo-x2 runs qwen3 coder 30b at 40 to 50 tokens per second and llama 3.3 70b at 20 to 25 tokens per second locally. on linux you get 110gb of usable vram out of 128gb setup takes 90 minutes. wipe windows for linux, install ollama with one command, pull the model, point claude code at localhost. same interface, same agent loop, nothing leaves your network a heavy ai user pays $200 for claude code max, $200 for chatgpt pro and $20 for cursor. that's $5,040 a year and the box pays itself off in 5 months after break-even every month is $420 that used to leave your account. three year math is roughly $13,000 not paid to ai companies plus zero rate limits on overnight agents bookmark this and read the article below
0:52

AMD'S NEW MINI PC RUNS CLAUDE CODE OFFLINE FOR $0/MONTH AND REPLACES $200 OPENAI + $200 CLAUDE CODE SUBSCRIPTIONS amd's ryzen ai max+ 395 is the first x86 chip that runs a 200 billion parameter model on a single piece of silicon with 128gb of unified memory the gmktec evo-x2 runs qwen3 coder 30b at 40 to 50 tokens per second and llama 3.3 70b at 20 to 25 tokens per second locally. on linux you get 110gb of usable vram out of 128gb setup takes 90 minutes. wipe windows for linux, install ollama with one command, pull the model, point claude code at localhost. same interface, same agent loop, nothing leaves your network a heavy ai user pays $200 for claude code max, $200 for chatgpt pro and $20 for cursor. that's $5,040 a year and the box pays itself off in 5 months after break-even every month is $420 that used to leave your account. three year math is roughly $13,000 not paid to ai companies plus zero rate limits on overnight agents bookmark this and read the article below

starmex

33,516 views • 2 months ago

Okay, this is the first AI content setup I've seen that actually closes the loop. Sabrina Ramonov (founder of Blotato) runs all her content solo, and her Claude agent is pulling 41M cross-platform views in 30 days. She went 0 to 3M followers in 2 years on $0 ads. Most AI content tools stop at "here's your draft." You still grade it, schedule it, and publish it by hand. Here's her full setup: → connect Claude to Blotato → install 7 free Claude skills (open sourced, no email gate) → write, grade, and schedule your first post from the same agent The skills do the real work: content-coach, post-writer, post-grader, viral-hooks, repurpose, brand-brief, post-scheduler. What sold me: it's built for agents. Blotato ships an LLM-readable API spec, so Claude Code, Codex, or Hermes can run the whole thing end to end. She breaks down the exact system in the piece. Worth the full read. (clip attached is a Claude Code agent-workflow talk worth watching alongside this.)
4:00

Okay, this is the first AI content setup I've seen that actually closes the loop. Sabrina Ramonov (founder of Blotato) runs all her content solo, and her Claude agent is pulling 41M cross-platform views in 30 days. She went 0 to 3M followers in 2 years on $0 ads. Most AI content tools stop at "here's your draft." You still grade it, schedule it, and publish it by hand. Here's her full setup: → connect Claude to Blotato → install 7 free Claude skills (open sourced, no email gate) → write, grade, and schedule your first post from the same agent The skills do the real work: content-coach, post-writer, post-grader, viral-hooks, repurpose, brand-brief, post-scheduler. What sold me: it's built for agents. Blotato ships an LLM-readable API spec, so Claude Code, Codex, or Hermes can run the whole thing end to end. She breaks down the exact system in the piece. Worth the full read. (clip attached is a Claude Code agent-workflow talk worth watching alongside this.)

Prajwal Tomar

138,908 views • 11 days ago

this is f**king gold someone just figured out how to run Claude Fable 5 and GPT 5.6 Sol in the same loop gpt-5.6 came out yesterday. fable 5 leaves in 48 hours. this window has never existed before and never will again. here is how to use it: 1. open claude code. install openai's codex plugin 2. type /model. choose fable 5. 3. drop one ROUTING.md in your repo root (full file in comments). 4.paste the prompt (in comments), write what feature you want. boom. save and bookmark this no matter what. it will be the most productive thing you do this weekend
0:20

this is f**king gold someone just figured out how to run Claude Fable 5 and GPT 5.6 Sol in the same loop gpt-5.6 came out yesterday. fable 5 leaves in 48 hours. this window has never existed before and never will again. here is how to use it: 1. open claude code. install openai's codex plugin 2. type /model. choose fable 5. 3. drop one ROUTING.md in your repo root (full file in comments). 4.paste the prompt (in comments), write what feature you want. boom. save and bookmark this no matter what. it will be the most productive thing you do this weekend

Avid

140,354 views • 1 month ago

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,292 views • 2 months ago

If you're hitting Claude Code's context limit, check your terminal output before blaming your project size. Every command Claude runs dumps raw output into your context window. git status : 76% of it is noise. A failed cargo test : 155 lines becomes 3. A grep across your codebase : same story You're not running out of context because your code is too big. You're running out because the commands are bleeding you dry before you get anywhere. RTK intercepts that output, compresses it, and hands Claude a clean version instead. 60–90% fewer tokens. Same information. Runs in the background after a one-command setup. Real numbers from 2,900+ commands: average 89% compression across the board. MIT license. Free. 39k GitHub stars. rtk init -g That's it. Restart Claude Code and every command is compressed automatically.
0:29

If you're hitting Claude Code's context limit, check your terminal output before blaming your project size. Every command Claude runs dumps raw output into your context window. git status : 76% of it is noise. A failed cargo test : 155 lines becomes 3. A grep across your codebase : same story You're not running out of context because your code is too big. You're running out because the commands are bleeding you dry before you get anywhere. RTK intercepts that output, compresses it, and hands Claude a clean version instead. 60–90% fewer tokens. Same information. Runs in the background after a one-command setup. Real numbers from 2,900+ commands: average 89% compression across the board. MIT license. Free. 39k GitHub stars. rtk init -g That's it. Restart Claude Code and every command is compressed automatically.

Charlie Hills

16,680 views • 3 months ago

Andrej Karpathy (co-founder of OpenAI, LLM Wiki pattern creator): "Obsidian is the IDE. The LLM is the programmer. The wiki is the codebase. knowledge compounds like interest when the AI owns the maintenance." Someone built the open-source implementation of that principle. 6,800 stars. MIT licensed. Two minutes to install. Here is what it actually does: → ingest: drop a source, Claude reads it, pulls out people and ideas, creates 8-15 linked pages automatically → batch ingest: parallel agents read an entire pile at once, then cross-reference everything → query: ask your brain anything, it reads the cache, scans the index, cites the exact pages → /autoresearch: three rounds of search, fetch, synthesize, file — autonomous web research → lint: finds orphans, dead links, stale claims, missing cross-references → the real unlock: point every claude code project at the same vault — one brain, every project hot cache refreshed at the end of every session. next session opens with full recent context. no recap, no re-explaining. plain markdown, no subscription, no lock-in. Bookmark so you do not lose it! Follow NeilXbt for more Obsidian and Claude builds that show you what a self-maintaining second brain actually requires.
4:19

Andrej Karpathy (co-founder of OpenAI, LLM Wiki pattern creator): "Obsidian is the IDE. The LLM is the programmer. The wiki is the codebase. knowledge compounds like interest when the AI owns the maintenance." Someone built the open-source implementation of that principle. 6,800 stars. MIT licensed. Two minutes to install. Here is what it actually does: → ingest: drop a source, Claude reads it, pulls out people and ideas, creates 8-15 linked pages automatically → batch ingest: parallel agents read an entire pile at once, then cross-reference everything → query: ask your brain anything, it reads the cache, scans the index, cites the exact pages → /autoresearch: three rounds of search, fetch, synthesize, file — autonomous web research → lint: finds orphans, dead links, stale claims, missing cross-references → the real unlock: point every claude code project at the same vault — one brain, every project hot cache refreshed at the end of every session. next session opens with full recent context. no recap, no re-explaining. plain markdown, no subscription, no lock-in. Bookmark so you do not lose it! Follow NeilXbt for more Obsidian and Claude builds that show you what a self-maintaining second brain actually requires.

NeilXbt

33,993 views • 1 month ago

I just found a way to use Claude Code completely free. Claude Code is Anthropic’s terminal coding agent that usually needs a paid API key to run. But a viral GitHub project called Free Claude Code, now sitting at 37k stars, lets you skip the billing entirely. It works as a tiny proxy that sits between Claude Code and free model providers like NVIDIA NIM, OpenRouter, DeepSeek, and Gemini. Every request Claude Code would send to Anthropic gets quietly rerouted to a free model on the other side. The interface stays the same. What’s actually thinking behind it changes. Setup takes a couple of quick commands and a free API key from NVIDIA NIM or OpenRouter. Paste it into the local dashboard, pick a model, and you’re building. The catch is you’re not really using Claude anymore. But when the code ships, does the model badge matter? -- I have shared the Github Link in my free Whatsapp Community ↓
0:36

I just found a way to use Claude Code completely free. Claude Code is Anthropic’s terminal coding agent that usually needs a paid API key to run. But a viral GitHub project called Free Claude Code, now sitting at 37k stars, lets you skip the billing entirely. It works as a tiny proxy that sits between Claude Code and free model providers like NVIDIA NIM, OpenRouter, DeepSeek, and Gemini. Every request Claude Code would send to Anthropic gets quietly rerouted to a free model on the other side. The interface stays the same. What’s actually thinking behind it changes. Setup takes a couple of quick commands and a free API key from NVIDIA NIM or OpenRouter. Paste it into the local dashboard, pick a model, and you’re building. The catch is you’re not really using Claude anymore. But when the code ships, does the model badge matter? -- I have shared the Github Link in my free Whatsapp Community ↓

Vaibhav Sisinty

36,809 views • 1 month ago

THIS GUY TURNED A DESK LAMP INTO A LIVE CLAUDE CODE STATUS INDICATOR the lamp changes color based on what claude code is doing in real time when claude is thinking it's one color. when it's writing code it shifts. when it's done it changes again. when it errors out you know instantly without even looking at your screen the lamp is a moonside halo and i'm already tryna to buy one I might even buy multiple for the multiple claude sessions running in the background and turn my room into a disco if the color reflected the operational status of claude it would just be red 24/7 it could also track your usage limit. green at the start of the session, slowly fading to red as your tokens drain people are already hooking this up to their philips hue and govee setups at home
0:44

THIS GUY TURNED A DESK LAMP INTO A LIVE CLAUDE CODE STATUS INDICATOR the lamp changes color based on what claude code is doing in real time when claude is thinking it's one color. when it's writing code it shifts. when it's done it changes again. when it errors out you know instantly without even looking at your screen the lamp is a moonside halo and i'm already tryna to buy one I might even buy multiple for the multiple claude sessions running in the background and turn my room into a disco if the color reflected the operational status of claude it would just be red 24/7 it could also track your usage limit. green at the start of the session, slowly fading to red as your tokens drain people are already hooking this up to their philips hue and govee setups at home

Om Patel

108,062 views • 3 months ago

THIS CS TEACHER CONTROLS 4 CLAUDE CODE INSTANCES WITH HIS EYES AND VOICE - AND THEY FIX THEIR OWN MISTAKES AUTOMATICALLY He runs 4 Claude terminals at once - no mouse, no keyboard - eye tracking highlights the window he's looking at and voice dictation sends the prompt the moment he stops talking. But the real setup is what happens inside those terminals. Claude Code has zero memory of what went wrong last session - same bug that took 20 minutes to fix yesterday will happen again tomorrow unless you configure it correctly. His CLAUDE.md grows every time Claude makes a mistake - specific rules Claude reads before touching a single line - and PostToolUse hooks auto-format and type-check every file the moment it's written. Stop hooks run tests automatically when Claude says "done" - if they fail, Claude reads the errors and keeps fixing without any manual input. Before: 45 minutes of back-and-forth per feature, same mistakes on repeat - after: 10 minutes, most of it unattended.
1:23

THIS CS TEACHER CONTROLS 4 CLAUDE CODE INSTANCES WITH HIS EYES AND VOICE - AND THEY FIX THEIR OWN MISTAKES AUTOMATICALLY He runs 4 Claude terminals at once - no mouse, no keyboard - eye tracking highlights the window he's looking at and voice dictation sends the prompt the moment he stops talking. But the real setup is what happens inside those terminals. Claude Code has zero memory of what went wrong last session - same bug that took 20 minutes to fix yesterday will happen again tomorrow unless you configure it correctly. His CLAUDE.md grows every time Claude makes a mistake - specific rules Claude reads before touching a single line - and PostToolUse hooks auto-format and type-check every file the moment it's written. Stop hooks run tests automatically when Claude says "done" - if they fail, Claude reads the errors and keeps fixing without any manual input. Before: 45 minutes of back-and-forth per feature, same mistakes on repeat - after: 10 minutes, most of it unattended.

Noisy

13,772 views • 2 months ago

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,746 views • 4 months ago

ANTHROPIC LEAKED A SETUP WHERE 6 FILES CUT TOKENS BY 84% AND RAISE ACCURACY BY 39% engineers at Google and Microsoft have been running this for a while - they pay $3 where you pay $20. decisions → contracts → dead ends → state → sources → open questions memory moves outside the window - what enters the context is a pointer to a file, not the history. raw history refills the window to 200k every single turn - six pointers take 8k and leave 96% free. same work, same five turns: 1,000,000 tokens against 40,000. decisions written to a file kill the endless "wait, why did we do it this way". written dead ends kill the second lap around the same circle - the agent never walks in there twice. a stable prefix keeps the cache warm - a cache read costs 0.1x of normal input. that's why 20 turns cost 3.15x instead of 20x - one write and nineteen reads. save this and paste it into Claude Code - and your agent stops paying for what it already knew ↓
0:51

ANTHROPIC LEAKED A SETUP WHERE 6 FILES CUT TOKENS BY 84% AND RAISE ACCURACY BY 39% engineers at Google and Microsoft have been running this for a while - they pay $3 where you pay $20. decisions → contracts → dead ends → state → sources → open questions memory moves outside the window - what enters the context is a pointer to a file, not the history. raw history refills the window to 200k every single turn - six pointers take 8k and leave 96% free. same work, same five turns: 1,000,000 tokens against 40,000. decisions written to a file kill the endless "wait, why did we do it this way". written dead ends kill the second lap around the same circle - the agent never walks in there twice. a stable prefix keeps the cache warm - a cache read costs 0.1x of normal input. that's why 20 turns cost 3.15x instead of 20x - one write and nineteen reads. save this and paste it into Claude Code - and your agent stops paying for what it already knew ↓

Noisy

133,906 views • 4 days ago

Anthropic Claude Code engineer: "If you're watching Claude write code, you're the QA tester. That's not what you're paid for." In 37 minutes he lays out how to get your keyboard out of the hot path entirely. The shift is /loop. You tell Claude to wake up every 10 minutes and babysit your PRs, and it just does it, while you're nowhere near the laptop. Routines do the same in the cloud, so the work keeps running with your machine closed. He caps it with remote control: any session, on any surface, driven from your phone. Watch the full talk, then grab the setup below.
37:03

Anthropic Claude Code engineer: "If you're watching Claude write code, you're the QA tester. That's not what you're paid for." In 37 minutes he lays out how to get your keyboard out of the hot path entirely. The shift is /loop. You tell Claude to wake up every 10 minutes and babysit your PRs, and it just does it, while you're nowhere near the laptop. Routines do the same in the cloud, so the work keeps running with your machine closed. He caps it with remote control: any session, on any surface, driven from your phone. Watch the full talk, then grab the setup below.

Hanako

689,850 views • 2 months ago

New on Claude Code Desktop We’re shipping new features for Claude Code on desktop that let you preview running apps, auto-review code, and auto-fix and merge PRs to help close the development loop. - Server previews: Claude starts dev servers and previews your running app in the desktop interface. It reads console logs, catches errors, and keeps iterating on its own. - Local code review: Claude examines your local diffs and leaves inline comments before you push — an immediate second set of eyes on every change. - PR monitoring: Claude tracks CI status after you open a PR. With auto-fix, it attempts to resolve failures automatically. With auto-merge, PRs land as soon as checks pass. You can move on to your next task while Claude handles the last one. - Session mobility: Move sessions from CLI to desktop, and from desktop to the cloud. Start work at your desk, pick it up from the web or your phone.
1:15

New on Claude Code Desktop We’re shipping new features for Claude Code on desktop that let you preview running apps, auto-review code, and auto-fix and merge PRs to help close the development loop. - Server previews: Claude starts dev servers and previews your running app in the desktop interface. It reads console logs, catches errors, and keeps iterating on its own. - Local code review: Claude examines your local diffs and leaves inline comments before you push — an immediate second set of eyes on every change. - PR monitoring: Claude tracks CI status after you open a PR. With auto-fix, it attempts to resolve failures automatically. With auto-merge, PRs land as soon as checks pass. You can move on to your next task while Claude handles the last one. - Session mobility: Move sessions from CLI to desktop, and from desktop to the cloud. Start work at your desk, pick it up from the web or your phone.

Ado

71,910 views • 5 months ago