Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

I’ve been asked a lot why I keep Claude Code auto-compact turned off. Here’s why 👇 If you configure commands, sub-agents, and hooks properly, you almost never hit auto-compact. Every time it triggered for me, I lost important context. After looking at how compaction actually works, it was clear...

dani_avila7's profile picture

Daniel San

32,511 subscribers

105,569 görüntüleme • 5 ay önce •via X (Twitter)

EğitimBilim & Teknoloji
LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

Share Claude Code sessions with this command 👇 Just shipped v1.26.1 of claude-code-templates because I kept needing to hand off work mid-session. Run: npx claude-code-templates@latest --chats - All your sessions grouped by chat - Download any conversation To share a session: - Share the file, and add it to your project - Then run: claude "read @ chat-file .md and continue" Or if you are in the same account click on "Resume" and you will see the command: claude --resume session_id Built this to keep context flowing across the team without losing momentum.
0:34

Share Claude Code sessions with this command 👇 Just shipped v1.26.1 of claude-code-templates because I kept needing to hand off work mid-session. Run: npx claude-code-templates@latest --chats - All your sessions grouped by chat - Download any conversation To share a session: - Share the file, and add it to your project - Then run: claude "read @ chat-file .md and continue" Or if you are in the same account click on "Resume" and you will see the command: claude --resume session_id Built this to keep context flowing across the team without losing momentum.

Daniel San

10,787 görüntüleme • 7 ay önce

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 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 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

56,934 görüntüleme • 5 ay önce

Claude Code Teams as a flow diagram Just run: npx claude-code-templates@latest --teams You’ll get a full view of how the lead and the team communicate: messages, tasks, and the tools they executed. The more observability you have into your Claude Code agents’ workflows, the better your workflows, and the better the results. Open source project:
0:52

Claude Code Teams as a flow diagram Just run: npx claude-code-templates@latest --teams You’ll get a full view of how the lead and the team communicate: messages, tasks, and the tools they executed. The more observability you have into your Claude Code agents’ workflows, the better your workflows, and the better the results. Open source project:

Daniel San

85,347 görüntüleme • 4 ay önce

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

305,852 görüntüleme • 14 gün önce

Introducing Claude Code Templates 🚀 I originally built this to streamline how I set up new projects with Claude Code…just a small tool to make my own workflow smoother. No install, just run: npx claude-code-templates Right now, it configures Commands, Hooks, MCPs, and settings.json for JavaScript/TypeScript and Python projects. It made things so much easier for me that I decided to share it with the community. Open-source and open to ideas — feel free to contribute! Big thanks to the team at Anthropic and everyone behind Claude Code Community 🙌
0:50

Introducing Claude Code Templates 🚀 I originally built this to streamline how I set up new projects with Claude Code…just a small tool to make my own workflow smoother. No install, just run: npx claude-code-templates Right now, it configures Commands, Hooks, MCPs, and settings.json for JavaScript/TypeScript and Python projects. It made things so much easier for me that I decided to share it with the community. Open-source and open to ideas — feel free to contribute! Big thanks to the team at Anthropic and everyone behind Claude Code Community 🙌

Daniel San

28,410 görüntüleme • 11 ay önce

Working with Claude Code involves a lot of waiting around for Claude to figure out what it needs to complete a task. There's a better way though! Priming Claude Code with Repo Prompt context lets you get better code faster from agents like Claude Code. Let's dive in 👇
5:10

Working with Claude Code involves a lot of waiting around for Claude to figure out what it needs to complete a task. There's a better way though! Priming Claude Code with Repo Prompt context lets you get better code faster from agents like Claude Code. Let's dive in 👇

eric provencher

42,523 görüntüleme • 10 ay önce

you're running /compact every 10 minutes to fix a problem that disappears the second you give Claude one job instead of five. Anthropic shipped a clean 4-minute video on context management. /compact when the window fills up. /clear to reset. small files over big files. the practical tips work. the video covers the cleanup. it doesn't cover why your window keeps filling up in the first place, and the answer is usually that you're holding too many jobs in one prompt. look at what most people put in a single Claude call: > guess the right answer > choose between options > set the position size > watch the exit window > read the news for sentiment five tools' worth of state in one conversation. of course the window fills. i ran into this on a Polymarket bot: the prediction-layer version ate context constantly. /compact every 8-10 turns. i thought i needed better memory hygiene. i needed fewer jobs per call. i stripped the prompt down to one job: veto an entry i had already decided to take. the context window stopped filling. /compact went from every 8 turns to once a session, if ever. over 90 days that prompt blocked 128 trades. watch the 4 min, then ask why your window keeps needing it. clean context. lean prompt. nothing to compact.
3:26

you're running /compact every 10 minutes to fix a problem that disappears the second you give Claude one job instead of five. Anthropic shipped a clean 4-minute video on context management. /compact when the window fills up. /clear to reset. small files over big files. the practical tips work. the video covers the cleanup. it doesn't cover why your window keeps filling up in the first place, and the answer is usually that you're holding too many jobs in one prompt. look at what most people put in a single Claude call: > guess the right answer > choose between options > set the position size > watch the exit window > read the news for sentiment five tools' worth of state in one conversation. of course the window fills. i ran into this on a Polymarket bot: the prediction-layer version ate context constantly. /compact every 8-10 turns. i thought i needed better memory hygiene. i needed fewer jobs per call. i stripped the prompt down to one job: veto an entry i had already decided to take. the context window stopped filling. /compact went from every 8 turns to once a session, if ever. over 90 days that prompt blocked 128 trades. watch the 4 min, then ask why your window keeps needing it. clean context. lean prompt. nothing to compact.

Mnimiy

20,635 görüntüleme • 24 gün önce

Best way to debug Claude Code sessions and inspect agent context. Just Run: npx claude-code-templates@latest --chats Browser interface with advanced search across all your sessions (name, ID, directory, dates, message content). Shows every tool call with exact JSON executed. Resume button lets you continue any session - efficient context loading. Runs completely local and open source 👏
0:36

Best way to debug Claude Code sessions and inspect agent context. Just Run: npx claude-code-templates@latest --chats Browser interface with advanced search across all your sessions (name, ID, directory, dates, message content). Shows every tool call with exact JSON executed. Resume button lets you continue any session - efficient context loading. Runs completely local and open source 👏

Daniel San

32,842 görüntüleme • 7 ay önce

Introducing Claude Code Analytics Dashboard 🙌 Open source project to monitor your Claude Code agents in real-time as they work on your projects. Just run: npx claude-code-templates@latest --analytics Dashboard opens at localhost:3333 showing: - All active Claude Code sessions - Token usage & conversation stats - Real-time activity monitoring - Message history with export (CSV/JSON) Perfect for devs running multiple Claude Code agents - finally see what they're actually doing! The conversation view shows full chat history, token breakdowns, and current status. Finally understand your AI workflow patterns. Best part... Everything runs locally with total privacy! Sharing repo in first comment if you want to star or contribute 👇
0:40

Introducing Claude Code Analytics Dashboard 🙌 Open source project to monitor your Claude Code agents in real-time as they work on your projects. Just run: npx claude-code-templates@latest --analytics Dashboard opens at localhost:3333 showing: - All active Claude Code sessions - Token usage & conversation stats - Real-time activity monitoring - Message history with export (CSV/JSON) Perfect for devs running multiple Claude Code agents - finally see what they're actually doing! The conversation view shows full chat history, token breakdowns, and current status. Finally understand your AI workflow patterns. Best part... Everything runs locally with total privacy! Sharing repo in first comment if you want to star or contribute 👇

Daniel San

62,057 görüntüleme • 11 ay önce

Here's what you get when you let Claude Code run wild on an idea. I didn't add any specific prompts for these details. The first prompt was to create a theme park, then let it keep iterating and improving. The result looks amazing
0:32

Here's what you get when you let Claude Code run wild on an idea. I didn't add any specific prompts for these details. The first prompt was to create a theme park, then let it keep iterating and improving. The result looks amazing

Dilum Sanjaya

16,310 görüntüleme • 4 ay önce

Anthropic didn't build a better model to make Claude Code work. They built a better environment around it. 55 directories. 331 modules. Context compaction so sessions run for hours. Streaming tool execution that saves seconds per turn. Read this article for full breakdown.
25:51

Anthropic didn't build a better model to make Claude Code work. They built a better environment around it. 55 directories. 331 modules. Context compaction so sessions run for hours. Streaming tool execution that saves seconds per turn. Read this article for full breakdown.

Rohit

124,776 görüntüleme • 2 ay önce

Claude Code Templates now supports Settings & Hooks! just got a major update. You can now: ✅ Browse and install Settings & Hooks alongside Agents, Commands & MCPs ✅ Build complete stacks with one command ✅ Customize your Claude Code experience exactly how you want Select what you need → Add to cart → Copy command → Install. Done 🙌 Check it out on GitHub
0:42

Claude Code Templates now supports Settings & Hooks! just got a major update. You can now: ✅ Browse and install Settings & Hooks alongside Agents, Commands & MCPs ✅ Build complete stacks with one command ✅ Customize your Claude Code experience exactly how you want Select what you need → Add to cart → Copy command → Install. Done 🙌 Check it out on GitHub

Daniel San

29,737 görüntüleme • 10 ay önce

built a small CLI tool that moves your AI coding session context between Claude Code, Gemini, Copilot, Codex and OpenCode when you hit rate limits. no more re-explaining what you were doing, or painful copy/paste from terminal that lose tool-call context. just `npx continues`
0:30

built a small CLI tool that moves your AI coding session context between Claude Code, Gemini, Copilot, Codex and OpenCode when you hit rate limits. no more re-explaining what you were doing, or painful copy/paste from terminal that lose tool-call context. just `npx continues`

Yigit Konur

213,400 görüntüleme • 3 ay önce

So many people wanted to see my knowledge management system in Claude code, so here it is. All you need is Obsidian, Claude Code, GitHub, and the will to live and you too can set up your second brain in under 2 hours. If you want to learn how to build this, here’s the demo link:
1:34

So many people wanted to see my knowledge management system in Claude code, so here it is. All you need is Obsidian, Claude Code, GitHub, and the will to live and you too can set up your second brain in under 2 hours. If you want to learn how to build this, here’s the demo link:

Allie K. Miller

51,555 görüntüleme • 2 ay önce

I just discovered that Claude Code can build entire N8N workflows The results are actually shocking... If you want to know how to do it, just watch this:
14:15

I just discovered that Claude Code can build entire N8N workflows The results are actually shocking... If you want to know how to do it, just watch this:

David Ondrej

43,087 görüntüleme • 10 ay önce

ASCII diagrams in Claude Code were driving me crazy. So I built a tool where Claude writes JSON → renders as interactive flowcharts and mockups → I edit visually → Claude sees my changes. Shoutout to Every 📧 for having me on the Vibe Code Camp livestream to demo this today We want to make this available! If you want access, comment "flowy" on this post. Here's 2 min on how it works:
2:21

ASCII diagrams in Claude Code were driving me crazy. So I built a tool where Claude writes JSON → renders as interactive flowcharts and mockups → I edit visually → Claude sees my changes. Shoutout to Every 📧 for having me on the Vibe Code Camp livestream to demo this today We want to make this available! If you want access, comment "flowy" on this post. Here's 2 min on how it works:

CJ Hess

199,773 görüntüleme • 4 ay önce

Someone gave Claude Code permanent memory. → 95% fewer tokens per session → Never hits context limits → Picks up exactly where you left off → 46,000 GitHub stars in 48 hours One command: `npx claude-mem install` Completely free. Community-built. Not Anthropic. Claude Code is exceptional. It just kept forgetting everything. This fixes that.
0:22

Someone gave Claude Code permanent memory. → 95% fewer tokens per session → Never hits context limits → Picks up exactly where you left off → 46,000 GitHub stars in 48 hours One command: `npx claude-mem install` Completely free. Community-built. Not Anthropic. Claude Code is exceptional. It just kept forgetting everything. This fixes that.

Charlie Hills

119,773 görüntüleme • 1 ay önce

CLAUDE CODE JUST SHIPPED THE FEATURE THAT SOLVES THE BIGGEST PROBLEM EVERY BUILDER HAS WITH AI AGENTS. The problem: Claude starts a task, gets distracted by a sub-problem, goes down a rabbit hole, and never finishes the original thing you asked for. The solution: /goal One command. You set the goal at the start of the session. Claude now has a north star it checks against every action it takes. Not just at the beginning. Throughout the entire session. Every time Claude is about to do something it asks: does this action move me toward the goal the user set or am I drifting? If it is drifting it corrects. If it completes a sub-task it returns to the primary goal. If it hits a blocker it reports back instead of spending 45 minutes solving the wrong problem. This sounds like a small feature. It is not. The reason most people do not trust Claude Code for long autonomous runs is not capability. It is reliability. A Claude Code session that reliably finishes what it started is worth 10 times more than one that is more capable but wanders. /goal is the feature that makes long autonomous sessions reliable. Set the goal. Let it run. Come back to a finished result. Not a result that got 70% done before Claude decided the sub-problem was more interesting. Done. The builders running overnight agent sessions are going to use this command on everything from today forward. Bookmark this. Follow CyrilXBT for every Claude Code feature the moment it ships.
0:24

CLAUDE CODE JUST SHIPPED THE FEATURE THAT SOLVES THE BIGGEST PROBLEM EVERY BUILDER HAS WITH AI AGENTS. The problem: Claude starts a task, gets distracted by a sub-problem, goes down a rabbit hole, and never finishes the original thing you asked for. The solution: /goal One command. You set the goal at the start of the session. Claude now has a north star it checks against every action it takes. Not just at the beginning. Throughout the entire session. Every time Claude is about to do something it asks: does this action move me toward the goal the user set or am I drifting? If it is drifting it corrects. If it completes a sub-task it returns to the primary goal. If it hits a blocker it reports back instead of spending 45 minutes solving the wrong problem. This sounds like a small feature. It is not. The reason most people do not trust Claude Code for long autonomous runs is not capability. It is reliability. A Claude Code session that reliably finishes what it started is worth 10 times more than one that is more capable but wanders. /goal is the feature that makes long autonomous sessions reliable. Set the goal. Let it run. Come back to a finished result. Not a result that got 70% done before Claude decided the sub-problem was more interesting. Done. The builders running overnight agent sessions are going to use this command on everything from today forward. Bookmark this. Follow CyrilXBT for every Claude Code feature the moment it ships.

CyrilXBT

19,526 görüntüleme • 27 gün önce

Trump: "When you go to a voting booth, and you do it the right way, and you go to a state that runs it properly, you go in -- they even asked me, they asked me for my license plate. I said, 'I don't know if I have it.' They said, 'Sir, you have to have it.' I was very impressed actually."
0:22

Trump: "When you go to a voting booth, and you do it the right way, and you go to a state that runs it properly, you go in -- they even asked me, they asked me for my license plate. I said, 'I don't know if I have it.' They said, 'Sir, you have to have it.' I was very impressed actually."

Aaron Rupar

1,125,017 görüntüleme • 9 ay önce

You can just tell Claude Code to learn skills and it will. I asked Claude to create an app that uses tldraw and it one shotted it with sqlite db, and then I asked Claude Code to create a skill so that it could read and write on the canvas. 10 minutes later it could do it. Weirrrrdddd times.
0:25

You can just tell Claude Code to learn skills and it will. I asked Claude to create an app that uses tldraw and it one shotted it with sqlite db, and then I asked Claude Code to create a skill so that it could read and write on the canvas. 10 minutes later it could do it. Weirrrrdddd times.

Riley Brown

73,418 görüntüleme • 5 ay önce