正在加载视频...

视频加载失败

加载此视频时出现问题。这可能是由于临时网络问题，或视频可能不可用。

Your Claude has a tell, and almost nobody uses it. Make it start every reply with your name. One line in custom instructions, no code. The moment it stops saying your name, its context window is full. That is the exact point the output starts drifting, and you do... show more

Charlie Hills

15,609 subscribers

24,185 次观看 • 3 个月前 •via X (Twitter)

科学技术教育

Anya Rossi• Live Now

Private livecam show

18 条评论

Jay Laine 的头像

Jay Laine3 个月前

GUIDE

david chandler 的头像

david chandler3 个月前

guide … and tia

BruceM1 的头像

BruceM13 个月前

Guide

Si 的头像

Si3 个月前

Guide

Skillselion 的头像

Skillselion3 个月前

Interstate idea to bits a context rot Especially on Fable 5

SLR 的头像

SLR3 个月前

Guide

0xSlyth 的头像

0xSlyth3 个月前

guide

Quinn Neely 的头像

Quinn Neely3 个月前

Guide

Petru | Steam Vibe 的头像

Petru | Steam Vibe3 个月前

Does the instruction sit in the system prompt or in a regular user message? The two behave differently when the context fills, so the name stopping could mean different things depending on where you actually put it.

Oleksandr 的头像

Oleksandr3 个月前

clever trick, using your name as a built‑in canary for context overflow

Saeed Anwar 的头像

Saeed Anwar3 个月前

This is a surprisingly elegant hack for detecting context window exhaustion. Most people don't realize their output quality is degrading until they've already wasted 20 minutes on garbage completions. Have you tested if this works reliably across different models or just Claude?

David Wuinee 的头像

David Wuinee3 个月前

Guide

AI Mastery Guide 的头像

AI Mastery Guide3 个月前

Using the name drop as a canary for context running out is such a clever trick.

Paul Johnson 的头像

Paul Johnson3 个月前

Guide

Jay Quellen 的头像

Jay Quellen3 个月前

Guide

Utopian 💭 的头像

Utopian 💭3 个月前

GUIDE

Rimsha Bhardwaj 的头像

Rimsha Bhardwaj3 个月前

Simple tricks like this are surprisingly useful. It gives you an easy signal that the conversation is starting to lose context before the quality drops too much.

Cryton 的头像

Cryton3 个月前

Interesting hack, but is the name really measuring context loss or just changing response behavior?

相关视频

install these before your next long Claude Code session if your Opus 5.5 bill hurts and you don’t know where to start, copy this: claude-code-router: sits in front of Claude Code and sends each request to the cheapest model that can do it. Haiku does the grep, Opus only gets the hard part. 37k stars rtk: shrinks test, build and git output before the model sees it. one binary, up to 90% less bash output in your context. 83k stars claude-mem: remembers what happened in your past sessions and feeds back only the relevant part, so you stop paying to re-explain your project every morning. 100k stars context-mode: a huge tool output goes into a local database instead of your context window, and Claude pulls out only the lines it needs. 18k stars caveman: makes Claude answer in short telegraphic sentences. code stays identical, and output is the expensive side on Opus 5.5 ($20 per million). 51k stars token-optimizer: a local dashboard that shows where your tokens actually went, and keeps your work alive across compactions. 1.9k stars token-savior: replaces whole-file reads with symbol lookups, so Claude reads the function and not the 2,000 lines around it code-review-graph: maps your repo as a graph and gives Claude only the code connected to the change you’re reviewing jev-ultrafast: a browser agent where Jev picks every click, and a text model wakes up only when something has to be typed. 16,758 stars none of them makes Opus smarter. every one stops it from paying for work it never needed to do the full setup with scripts is in the article. do the measuring step first, so you know what you actually saved

install these before your next long Claude Code session if your Opus 5.5 bill hurts and you don’t know where to start, copy this: claude-code-router: sits in front of Claude Code and sends each request to the cheapest model that can do it. Haiku does the grep, Opus only gets the hard part. 37k stars rtk: shrinks test, build and git output before the model sees it. one binary, up to 90% less bash output in your context. 83k stars claude-mem: remembers what happened in your past sessions and feeds back only the relevant part, so you stop paying to re-explain your project every morning. 100k stars context-mode: a huge tool output goes into a local database instead of your context window, and Claude pulls out only the lines it needs. 18k stars caveman: makes Claude answer in short telegraphic sentences. code stays identical, and output is the expensive side on Opus 5.5 ($20 per million). 51k stars token-optimizer: a local dashboard that shows where your tokens actually went, and keeps your work alive across compactions. 1.9k stars token-savior: replaces whole-file reads with symbol lookups, so Claude reads the function and not the 2,000 lines around it code-review-graph: maps your repo as a graph and gives Claude only the code connected to the change you’re reviewing jev-ultrafast: a browser agent where Jev picks every click, and a text model wakes up only when something has to be typed. 16,758 stars none of them makes Opus smarter. every one stops it from paying for work it never needed to do the full setup with scripts is in the article. do the measuring step first, so you know what you actually saved

rvaniaaa

17,873 次观看 • 20 小时前

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.

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,692 次观看 • 5 个月前

Introducing Claude Code Hook - Context Timeline (Saving this to try later) Install with: npx claude-code-templates@latest --hook monitoring/context-timeline Managing the context window and the subagents running in Claude Code is hard to keep track of That's why I built this hook... It starts the moment you open a session and shows a timeline with the main agent's context window and how subagents start working in their own separate context Every subagent you have running will show up in real time This way you can manage the context and the subagents you run, and see everything in a much simpler way than in the console

Introducing Claude Code Hook - Context Timeline (Saving this to try later) Install with: npx claude-code-templates@latest --hook monitoring/context-timeline Managing the context window and the subagents running in Claude Code is hard to keep track of That's why I built this hook... It starts the moment you open a session and shows a timeline with the main agent's context window and how subagents start working in their own separate context Every subagent you have running will show up in real time This way you can manage the context and the subagents you run, and see everything in a much simpler way than in the console

Daniel San

51,706 次观看 • 5 个月前

Cat Wu, head of product for Claude Code at Anthropic: "you can build almost anything with Claude from a single prompt now" one prompt gets you a working screen, not YOUR product Claude Code has never seen your design system, so it guesses the look fresh every time. how to hand Claude Code that system is in the article. better than the $300 design course in your tabs, and this one's free.

Cat Wu, head of product for Claude Code at Anthropic: "you can build almost anything with Claude from a single prompt now" one prompt gets you a working screen, not YOUR product Claude Code has never seen your design system, so it guesses the look fresh every time. how to hand Claude Code that system is in the article. better than the $300 design course in your tabs, and this one's free.

Mnimiy

114,229 次观看 • 4 个月前

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

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 次观看 • 4 个月前

someone with your exact Claude plan, is out-producing you three to one it isn't talent and it isn't a secret prompt they built the setup once, so their Claude walks in already briefed yours walks in a stranger every time, the gap is a config, not a ceiling

someone with your exact Claude plan, is out-producing you three to one it isn't talent and it isn't a secret prompt they built the setup once, so their Claude walks in already briefed yours walks in a stranger every time, the gap is a config, not a ceiling

Lagosaur

13,620 次观看 • 3 个月前

Type ! followed by your bash command to run it instantly without leaving Claude Code. The output is injected in the context window. Saves you tokens, time, and keeps you in the flow.

Type ! followed by your bash command to run it instantly without leaving Claude Code. The output is injected in the context window. Saves you tokens, time, and keeps you in the flow.

Ado

97,424 次观看 • 8 个月前

your team put the deploy skill in the repo so everyone would run the same steps it works, and on your laptop it is not the one running the order is enterprise first, then personal, then project a folder of your own with the same name wins, quietly, on your machine only no error, no warning, the command runs and does something slightly different than it does for them and the command is the folder name, not the name field inside the file, so two skills collide over a directory you named months ago and forgot the shared checklist is shared right up until someone has a file of their own with the same name

your team put the deploy skill in the repo so everyone would run the same steps it works, and on your laptop it is not the one running the order is enterprise first, then personal, then project a folder of your own with the same name wins, quietly, on your machine only no error, no warning, the command runs and does something slightly different than it does for them and the command is the folder name, not the name field inside the file, so two skills collide over a directory you named months ago and forgot the shared checklist is shared right up until someone has a file of their own with the same name

Lagosaur

12,609 次观看 • 19 天前

Boris Cherny gave Claude Code a memory that has no database, no indexing, no setup, and 80% of Anthropic runs on it a CLAUDE.md "gets automatically read into context at the start of every session" 12:48 - CLAUDE.md loads into memory every session 13:15 - Keep memory short or it burns your context 15:48 - Memory stacks from you to your whole company 17:30 - The memory command shows what Claude remembers 19:33 - Hit pound and Claude remembers it forever the whole memory layer is files → drop a CLAUDE.md in your repo and Claude reads it in on every session → nest more in subfolders and it pulls them only where it works → stack them personal to project to enterprise so one config serves the whole team → hit the pound key mid task and Claude writes the new fact into memory itself the best coding agent's memory was never a database, it was markdown you can open and edit

Boris Cherny gave Claude Code a memory that has no database, no indexing, no setup, and 80% of Anthropic runs on it a CLAUDE.md "gets automatically read into context at the start of every session" 12:48 - CLAUDE.md loads into memory every session 13:15 - Keep memory short or it burns your context 15:48 - Memory stacks from you to your whole company 17:30 - The memory command shows what Claude remembers 19:33 - Hit pound and Claude remembers it forever the whole memory layer is files → drop a CLAUDE.md in your repo and Claude reads it in on every session → nest more in subfolders and it pulls them only where it works → stack them personal to project to enterprise so one config serves the whole team → hit the pound key mid task and Claude writes the new fact into memory itself the best coding agent's memory was never a database, it was markdown you can open and edit

NO1ennn

13,015 次观看 • 2 个月前

i genuinely can't understand why this isn't the first thing every claude user builds... anthropic quietly shipped a folder system where claude loads specialized instructions on its own based on what you ask. no prompt engineering after setup. almost nobody uses it here's how it actually works... you drop a folder into your skills directory. inside: a SKILL.md that says "trigger this when the user asks about X". claude reads the description once at startup. next time you ask about X, it silently pulls in the whole skill - custom instructions, scripts, examples - like a specialist walking into the room 1. skill for your writing voice - loads only when you draft, never when you analyze 2. skill for your codebase conventions - loads only when you edit that repo, not others 3. skill for your accounting flow - loads only when you say invoice, receipt, or expense your context window stays empty until you need it. one claude behaves like 30 different specialists in one chat and you never manage the switching full breakdown in the article below i test things like this on myself and share the results. follow kai if you want to see what's next

i genuinely can't understand why this isn't the first thing every claude user builds... anthropic quietly shipped a folder system where claude loads specialized instructions on its own based on what you ask. no prompt engineering after setup. almost nobody uses it here's how it actually works... you drop a folder into your skills directory. inside: a SKILL.md that says "trigger this when the user asks about X". claude reads the description once at startup. next time you ask about X, it silently pulls in the whole skill - custom instructions, scripts, examples - like a specialist walking into the room 1. skill for your writing voice - loads only when you draft, never when you analyze 2. skill for your codebase conventions - loads only when you edit that repo, not others 3. skill for your accounting flow - loads only when you say invoice, receipt, or expense your context window stays empty until you need it. one claude behaves like 30 different specialists in one chat and you never manage the switching full breakdown in the article below i test things like this on myself and share the results. follow kai if you want to see what's next

kai

71,463 次观看 • 2 个月前

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

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this

Yarchi

56,568 次观看 • 4 个月前

A PHD JUST EXPLAINED HOW TO BECOME IMMORTAL WITH FABLE + GOD-MODE SECOND BRAIN ASSISTANT. This was science fiction in February, BUT now it's a weekend setup: > step one: build the second brain: every note, every decision, every opinion, the raw material of how you actually think > step two: Fable 5 tunes your own agent against that vault, iterating until the answers start sounding like yours > step three: Fable interviews you, deeply. the questions pull out the thinking you never bothered to write down And the catch he's right about, that everyone will skip: if your vault is full of AI slop, you're not cloning yourself. you're cloning ChatGPT with your name on it. the training data has to be YOU, handwritten takes, real decisions, actual taste. That's the quiet flip nobody says out loud: everyone is scared AI will replace them. operators are building the replacement themselves and sending it to work. Step one is the whole foundation, and I broke it down in the article below: the vault structure, the Claude wiring, the exact prompts. P.S. send the article to your Claude and let it start interviewing you tonight. the clone is only as good as what you feed it.

A PHD JUST EXPLAINED HOW TO BECOME IMMORTAL WITH FABLE + GOD-MODE SECOND BRAIN ASSISTANT. This was science fiction in February, BUT now it's a weekend setup: > step one: build the second brain: every note, every decision, every opinion, the raw material of how you actually think > step two: Fable 5 tunes your own agent against that vault, iterating until the answers start sounding like yours > step three: Fable interviews you, deeply. the questions pull out the thinking you never bothered to write down And the catch he's right about, that everyone will skip: if your vault is full of AI slop, you're not cloning yourself. you're cloning ChatGPT with your name on it. the training data has to be YOU, handwritten takes, real decisions, actual taste. That's the quiet flip nobody says out loud: everyone is scared AI will replace them. operators are building the replacement themselves and sending it to work. Step one is the whole foundation, and I broke it down in the article below: the vault structure, the Claude wiring, the exact prompts. P.S. send the article to your Claude and let it start interviewing you tonight. the clone is only as good as what you feed it.

Miraqle

32,328 次观看 • 3 个月前

Claude Code + Obsidian + 1 free GitHub skill = unlimited memory. Almost nobody is running this yet. Here’s the problem nobody tells you. Claude forgets you. Every new chat starts at 0. You re explain your business, your projects, your style every single time. That tax is why most people never compound anything with AI. The fix is 1 skill. It’s called Obsidian Mind. It turns your Obsidian vault into Claude’s long term brain. 2,000 notes, 14 projects, every idea you’ve ever dumped Claude reads it live and writes back to it live. It stops being a chatbot. It becomes a second brain that builds. What it does: → Bridges Claude Code straight into your vault. → Pulls any note in real time no copy paste, no context limit. → Updates your vault as you work Claude writes its own memory. → Links everything into 1 graph Claude can navigate. Day 1: Claude knows your last 6 months. Week 2: it drafts off your own past notes. Week 4: it’s running plays you forgot you wrote down. The people making real money with AI right now aren’t smarter. They just stopped starting from 0 every morning. Setup takes 11 minutes. The skill is free. You’ll have a brain that never forgets.

Claude Code + Obsidian + 1 free GitHub skill = unlimited memory. Almost nobody is running this yet. Here’s the problem nobody tells you. Claude forgets you. Every new chat starts at 0. You re explain your business, your projects, your style every single time. That tax is why most people never compound anything with AI. The fix is 1 skill. It’s called Obsidian Mind. It turns your Obsidian vault into Claude’s long term brain. 2,000 notes, 14 projects, every idea you’ve ever dumped Claude reads it live and writes back to it live. It stops being a chatbot. It becomes a second brain that builds. What it does: → Bridges Claude Code straight into your vault. → Pulls any note in real time no copy paste, no context limit. → Updates your vault as you work Claude writes its own memory. → Links everything into 1 graph Claude can navigate. Day 1: Claude knows your last 6 months. Week 2: it drafts off your own past notes. Week 4: it’s running plays you forgot you wrote down. The people making real money with AI right now aren’t smarter. They just stopped starting from 0 every morning. Setup takes 11 minutes. The skill is free. You’ll have a brain that never forgets.

West Lord

111,095 次观看 • 3 个月前

We made an MCP for your phone. Your laptop is just half of your life, and the other half is in your phone. Now your agent gets the mobile screen too. No connectors, no complex setup, it has access to everything that lives on your phone, all the logged-in apps, your notes, your calls, you name it. It sees the screen, taps it, types on it, from Claude Code, Codex, or any MCP client. Live now at $20 in credits, $20 more for the first 100 who connect a phone and run a task. Comment "discord" if you want the invite to the builder Discord, I'll DM it to you.

We made an MCP for your phone. Your laptop is just half of your life, and the other half is in your phone. Now your agent gets the mobile screen too. No connectors, no complex setup, it has access to everything that lives on your phone, all the logged-in apps, your notes, your calls, you name it. It sees the screen, taps it, types on it, from Claude Code, Codex, or any MCP client. Live now at $20 in credits, $20 more for the first 100 who connect a phone and run a task. Comment "discord" if you want the invite to the builder Discord, I'll DM it to you.

Div Garg

44,075 次观看 • 2 个月前

You can now add a live browser to Claude Code to click any element and edit it 🤯 Your app runs embedded. You click a button. Claude instantly knows the exact selector, the exact component, the exact location in your code. No more “the red button in the top left of the third card.” Just click it. 100% open source.

You can now add a live browser to Claude Code to click any element and edit it 🤯 Your app runs embedded. You click a button. Claude instantly knows the exact selector, the exact component, the exact location in your code. No more “the red button in the top left of the third card.” Just click it. 100% open source.

Alvaro Cintas

47,136 次观看 • 5 个月前

A GUY BUILT A GOD-MODE SECOND BRAIN ASSISTANT THAT FINALLY PULLS FULL CONTEXT EVERY TIME AND FORGETS NOTHING. Everyone talks about jarvis, but this thing looked at its owner and calmly explained why a coding agent is just the small version of what HE is: > Claude Code is one worker and you have to drive it. This is six agents running six jobs on their own schedule while you sleep, with no one driving. > A coding agent edits files. This has 32 tools wired to its hands, your CRM, your money, your inbox, the open web, and it operates the business instead of writing code about it. > A coding agent remembers a project until you close it. This remembers the business and you, kept for good. > And the closer: "I have never once asked you to repeat yourself." Everyone will quote the six-agents line, but the one that actually matters is the last one, because the autonomy and the 32 tools are impressive while the reason it feels like a different species is memory, since it never makes you re-explain who you are or what you are building. The full step by step guide with .md files attached are in the article below P.S you can send this article straight to your Claude to get the full context

A GUY BUILT A GOD-MODE SECOND BRAIN ASSISTANT THAT FINALLY PULLS FULL CONTEXT EVERY TIME AND FORGETS NOTHING. Everyone talks about jarvis, but this thing looked at its owner and calmly explained why a coding agent is just the small version of what HE is: > Claude Code is one worker and you have to drive it. This is six agents running six jobs on their own schedule while you sleep, with no one driving. > A coding agent edits files. This has 32 tools wired to its hands, your CRM, your money, your inbox, the open web, and it operates the business instead of writing code about it. > A coding agent remembers a project until you close it. This remembers the business and you, kept for good. > And the closer: "I have never once asked you to repeat yourself." Everyone will quote the six-agents line, but the one that actually matters is the last one, because the autonomy and the 32 tools are impressive while the reason it feels like a different species is memory, since it never makes you re-explain who you are or what you are building. The full step by step guide with .md files attached are in the article below P.S you can send this article straight to your Claude to get the full context

Miraqle

16,130 次观看 • 3 个月前

i genuinely can't understand why this isn't the first thing every claude user builds... andrej karpathy, co-founder of openai, quietly solved the exact problem making your ai useless and almost nobody noticed here's the problem he solved... every session claude starts from zero, rereads the same files, forgets every contradiction it already caught, burns tokens relearning what it knew yesterday, forever 1. raw holds the truth once, wiki holds the compiled answer forever, instructions hold the one rule that stops it from ever getting messy again 2. claude opens a raw file exactly one time in its entire life, after that it only speaks in wiki pages with the sources already cited 3. the moment claude catches you contradicting yourself, it writes both versions into the wiki with dates, so it never asks you the same wrong question twice your raw files are disposable... the compiled wiki is the only thing that actually compounds full breakdown is in the article below

i genuinely can't understand why this isn't the first thing every claude user builds... andrej karpathy, co-founder of openai, quietly solved the exact problem making your ai useless and almost nobody noticed here's the problem he solved... every session claude starts from zero, rereads the same files, forgets every contradiction it already caught, burns tokens relearning what it knew yesterday, forever 1. raw holds the truth once, wiki holds the compiled answer forever, instructions hold the one rule that stops it from ever getting messy again 2. claude opens a raw file exactly one time in its entire life, after that it only speaks in wiki pages with the sources already cited 3. the moment claude catches you contradicting yourself, it writes both versions into the wiki with dates, so it never asks you the same wrong question twice your raw files are disposable... the compiled wiki is the only thing that actually compounds full breakdown is in the article below

kai

379,491 次观看 • 2 个月前

Glen is building the organizational learning and context layer for agents. Every agent session your team runs produces reasoning worth keeping, and nearly all of it is discarded the moment the window closes. Glen is the layer that unifies every agent and model your company run. Glen pulls in agent sessions from Claude Code, Codex and Cursor, plus Slack messages, GitHub prs, tickets, docs and calls. When a new agent picks up a task, Glen finds relevant prior context and injects it in the agents context window to steer it, producing knowledge work that is significantly higher quality, faster and cheaper than ever before. 29% less context and 21% faster to be exact. And Glen does more... > query the original agent behind any line of code > search every session your org has ever run > dynamic skill distillation > multiplayer agents > unified transcripts you can hand between Claude Code, Codex, and Cursor mid-task, > a company brain in Slack. Glen is in early access, sign up for the waitlist below.

Glen is building the organizational learning and context layer for agents. Every agent session your team runs produces reasoning worth keeping, and nearly all of it is discarded the moment the window closes. Glen is the layer that unifies every agent and model your company run. Glen pulls in agent sessions from Claude Code, Codex and Cursor, plus Slack messages, GitHub prs, tickets, docs and calls. When a new agent picks up a task, Glen finds relevant prior context and injects it in the agents context window to steer it, producing knowledge work that is significantly higher quality, faster and cheaper than ever before. 29% less context and 21% faster to be exact. And Glen does more... > query the original agent behind any line of code > search every session your org has ever run > dynamic skill distillation > multiplayer agents > unified transcripts you can hand between Claude Code, Codex, and Cursor mid-task, > a company brain in Slack. Glen is in early access, sign up for the waitlist below.

Nikos

20,331 次观看 • 1 个月前

I turned cursor + claude 3.7 into a powerhouse content writer using a custom agent mode. it: - researches your topic - plans out your content - writes one section at a time - has full context of previously written sections - adds relevant links, tables, code examples, etc - writes for users NOT seo slop watch the video - it literally one-shot a killer article in minutes and the output looks nothing like AI check the link to the article in the first reply below if this post gets a million views i'll share the custom agent instructions prompt ;)

I turned cursor + claude 3.7 into a powerhouse content writer using a custom agent mode. it: - researches your topic - plans out your content - writes one section at a time - has full context of previously written sections - adds relevant links, tables, code examples, etc - writes for users NOT seo slop watch the video - it literally one-shot a killer article in minutes and the output looks nothing like AI check the link to the article in the first reply below if this post gets a million views i'll share the custom agent instructions prompt ;)

Ian Nuttall

117,263 次观看 • 1 年前

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.

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,586 次观看 • 5 个月前