Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

Clude is now available as a custom connector on Anthropic Claude. Giving it persistent memory across every conversation. It remembers your projects, your preferences, and the decisions you make, so you never start from zero again. Use Clude across Chat / Co-Work and Claude Code. Add it in 30... seconds, no API key: 1. In Claude: Customize, Add custom connector URL: Enter your email. That's it. Recap for people unfamiliar: Clude deviates from the traditional vector database that many others bolt onto Claude. We are a cognitive memory system modeled on how human memory works. Think traditional memory systems: Calculator > It computes. Fullstop. Excel > Dynamic, formula run, able to share and manipulate Clude scored 86% on LongMemEval, one of the toughest long-term memory benchmarks. This means less hallucinations to traditional platforms. It scores memories by relevance, recency, and importance, links them into a knowledge graph, and consolidates them over time. Tell Claude something, open a new chat, and watch it remember.show more

seb

13,321 subscribers

19,640 views • 23 days ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Claude Code With UNLIMITED Memory! Solves Claude's Memory Problem! It’s called Claude-Mem, and it lets Claude remember your work across sessions. ⚡ Slash token usage by up to 95% every time you start a session. 🔧 Unlock the ability to make 20× more tool calls before hitting limits. My Video:

Claude Code With UNLIMITED Memory! Solves Claude's Memory Problem! It’s called Claude-Mem, and it lets Claude remember your work across sessions. ⚡ Slash token usage by up to 95% every time you start a session. 🔧 Unlock the ability to make 20× more tool calls before hitting limits. My Video:

WorldofAI

28,687 views • 5 months ago

We just launched a new primitive for AI Walrus Memory gives your agents persistent, portable memory that you own, and it drops straight into the platforms you already build on. Anthropic Claude, OpenAI ChatGPT, and Google Gemini, you name it plus native MCP and SDKs, added in a few lines of code LIVE TODAY

We just launched a new primitive for AI Walrus Memory gives your agents persistent, portable memory that you own, and it drops straight into the platforms you already build on. Anthropic Claude, OpenAI ChatGPT, and Google Gemini, you name it plus native MCP and SDKs, added in a few lines of code LIVE TODAY

Adeniyi.sui

46,072 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$

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 • 1 month ago

do you understand what Claude just did? > you can now tell Claude to use your entire computer. open apps. navigate your browser. fill spreadsheets. anything you’d do sitting at your desk > uses your connected apps first… Slack, Calendar, integrations. when there’s no connector, it asks permission to open the app on your screen directly > assign a task from your phone. walk away. come back to finished work on your computer > tell it once to scan your email every morning or pull a report every Friday and it just handles it > macOS only right now. research preview in Cowork and Claude Code > not long ago you needed a custom framework just to get Claude running on a loop. now it’s fully native → dispatch from your phone… native → scheduled recurring tasks… native → remote monitoring… native → multi-agent coordination… native → persistent memory across sessions… native every feature that made agentic frameworks valuable is becoming a platform feature for Claude the AI race just got way more interesting

do you understand what Claude just did? > you can now tell Claude to use your entire computer. open apps. navigate your browser. fill spreadsheets. anything you’d do sitting at your desk > uses your connected apps first… Slack, Calendar, integrations. when there’s no connector, it asks permission to open the app on your screen directly > assign a task from your phone. walk away. come back to finished work on your computer > tell it once to scan your email every morning or pull a report every Friday and it just handles it > macOS only right now. research preview in Cowork and Claude Code > not long ago you needed a custom framework just to get Claude running on a loop. now it’s fully native → dispatch from your phone… native → scheduled recurring tasks… native → remote monitoring… native → multi-agent coordination… native → persistent memory across sessions… native every feature that made agentic frameworks valuable is becoming a platform feature for Claude the AI race just got way more interesting

klöss

463,336 views • 3 months ago

LLMs are stateless. We built Dria Mem Agent to change that: Making memory a first-class feature. A 4B agent with local interoperable memory across Claude, ChatGPT and LM Studio. It turns LLMs from stateless chat into stateful agents with persistent human-readable memory.

Sensitive content

LLMs are stateless. We built Dria Mem Agent to change that: Making memory a first-class feature. A 4B agent with local interoperable memory across Claude, ChatGPT and LM Studio. It turns LLMs from stateless chat into stateful agents with persistent human-readable memory.

Dria

169,981 views • 10 months ago

$This is the setup that changed everything for me, Claude can now browse the internet on its own. Not with your browser. Its own dedicated browser.. It can now login with your credentials, scrape data, monitors communities and generates leads.. all in the background while you sleep First how you can set it up, > Open Claude Desktop > Click the plus (+) icon in the chat bar and select Connectors (or "Manage Connectors") > Click Add Custom Connector and enter the following details - Name: Firecrawl - URL: dev/{FIRECRAWL_API_KEY}/v2/mcp - API Key: Paste your API key from the Firecrawl dashboard. > Click Add. then just enable and Authorize, > Once added, find "Firecrawl" in your connectors list and toggle it on. > Claude will ask for approval to use the connector; select Always Allow to let it run tasks without prompting you every time can start using it normally in chat now.. Prompt it like: "Go to [website], extract [data], and organize it" It opens its own browser, navigates, scrapes, and brings you clean results. will share how i use this setup in my next post, so be sure to follow me and turn post notifications on.$

This is the setup that changed everything for me, Claude can now browse the internet on its own. Not with your browser. Its own dedicated browser.. It can now login with your credentials, scrape data, monitors communities and generates leads.. all in the background while you sleep First how you can set it up, > Open Claude Desktop > Click the plus (+) icon in the chat bar and select Connectors (or "Manage Connectors") > Click Add Custom Connector and enter the following details - Name: Firecrawl - URL: dev/{FIRECRAWL_API_KEY}/v2/mcp - API Key: Paste your API key from the Firecrawl dashboard. > Click Add. then just enable and Authorize, > Once added, find "Firecrawl" in your connectors list and toggle it on. > Claude will ask for approval to use the connector; select Always Allow to let it run tasks without prompting you every time can start using it normally in chat now.. Prompt it like: "Go to [website], extract [data], and organize it" It opens its own browser, navigates, scrapes, and brings you clean results. will share how i use this setup in my next post, so be sure to follow me and turn post notifications on.

Axel Bitblaze 🪓

179,605 views • 3 months 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

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

Khairallah AL-Awady

39,176 views • 27 days ago

A conversation with Boris Cherny and Cat Wu on the path from Claude Code to Claude Tag, and how it spread from engineering to the rest of Anthropic. Claude Fable 5 is now available in Claude Tag.

A conversation with Boris Cherny and Cat Wu on the path from Claude Code to Claude Tag, and how it spread from engineering to the rest of Anthropic. Claude Fable 5 is now available in Claude Tag.

Claude

513,233 views • 10 days ago

Claude Tag is the next evolution of agents. It's a proactive, multiplayer agent with memory and identity, built on top of Claude Code. Learn more about how Claude Tag works and best practices for using it in this deep dive.

Claude Tag is the next evolution of agents. It's a proactive, multiplayer agent with memory and identity, built on top of Claude Code. Learn more about how Claude Tag works and best practices for using it in this deep dive.

ClaudeDevs

443,121 views • 17 days ago

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

102,324 views • 14 days ago

Andrej Karpathy quietly shipped the best second brain idea in years not an app. a pattern. let an llm maintain a wiki of your notes. you dump sources, it reads them, links them, files them. knowledge compounds like interest. someone built it into a free claude code plugin. setup is two commands: claude plugin marketplace add AgriciDaniel/claude-obsidian claude plugin install claude-obsidian@agricidaniel-claude-obsidian then open obsidian, open claude code in the same folder, type /wiki. that's it. your notes are now queryable by claude and they get richer every time you read something. bookmark this. best thing you'll build this weekend.

Andrej Karpathy quietly shipped the best second brain idea in years not an app. a pattern. let an llm maintain a wiki of your notes. you dump sources, it reads them, links them, files them. knowledge compounds like interest. someone built it into a free claude code plugin. setup is two commands: claude plugin marketplace add AgriciDaniel/claude-obsidian claude plugin install claude-obsidian@agricidaniel-claude-obsidian then open obsidian, open claude code in the same folder, type /wiki. that's it. your notes are now queryable by claude and they get richer every time you read something. bookmark this. best thing you'll build this weekend.

Avid

336,261 views • 29 days ago

We’re excited to launch OpenMemory MCP, a private memory for MCP-compatible clients powered by mem0 Today, most AI assistants and dev tools operate without memory. You plan your roadmap in Claude, implement tasks in Cursor, but none of them know what the other did. Each tool operates in isolation, and your context disappears as soon as the session ends. OpenMemory MCP solves this. Built on the open Model Context Protocol (MCP), OpenMemory MCP runs 100% locally and provides a persistent, portable memory layer for all your AI tools. It enables agents and assistants to read from and write to a shared memory, securely and privately. Key capabilities: ✅Works across MCP clients like Cursor, Claude Desktop, Windsurf, Cline and more ✅Provides standardized memory operations (add_memories, search_memory, list_memories, delete_all_memories) ✅Stores data on your machine, fully private ✅Offers a centralized dashboard for visibility and control ✅Simple Docker-based setup with no vendor lock-in If you're building on MCP, OpenMemory MCP is the easiest way to add persistent, private memory to your clients with zero cloud dependencies and full local control. We’ve put together a short demo to show how it works Check it out in the links below 👇

We’re excited to launch OpenMemory MCP, a private memory for MCP-compatible clients powered by mem0 Today, most AI assistants and dev tools operate without memory. You plan your roadmap in Claude, implement tasks in Cursor, but none of them know what the other did. Each tool operates in isolation, and your context disappears as soon as the session ends. OpenMemory MCP solves this. Built on the open Model Context Protocol (MCP), OpenMemory MCP runs 100% locally and provides a persistent, portable memory layer for all your AI tools. It enables agents and assistants to read from and write to a shared memory, securely and privately. Key capabilities: ✅Works across MCP clients like Cursor, Claude Desktop, Windsurf, Cline and more ✅Provides standardized memory operations (add_memories, search_memory, list_memories, delete_all_memories) ✅Stores data on your machine, fully private ✅Offers a centralized dashboard for visibility and control ✅Simple Docker-based setup with no vendor lock-in If you're building on MCP, OpenMemory MCP is the easiest way to add persistent, private memory to your clients with zero cloud dependencies and full local control. We’ve put together a short demo to show how it works Check it out in the links below 👇

Taranjeet

471,767 views • 1 year ago

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.

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

I FINALLY FIGURED OUT WHY CLAUDE KEEPS FORGETTING THINGS. For months, I thought Claude’s memory was broken. I’d spend 20 minutes explaining my project few chats later, it would forget important stuff and remember something completely random. Turns out the problem wasn’t Claude. It was how I was using it. Here’s the system that fixed it LEVEL 1: Clean up the basics (5 mins) - Remove old memories you don’t need - Add proper project instructions - Tell Claude exactly what should and shouldn’t be remembered Most people never do this and then wonder why memory feels inconsistent. LEVEL 2: Build a context system (30-60 mins) Create a folder with: → Instructions.md → Memory.md → Context.md → Archive.md Now Claude has a dedicated place to store information instead of trying to remember everything from chat history. Massive difference. LEVEL 3: Build a real AI second brain → Connect Claude to your notes. → Research. → Documents. → Knowledge base. Instead of starting from zero every session, it builds context over time. This is when Claude stops feeling like a chatbot and starts feeling like an actual assistant. Most people are obsessed with prompts. The real power comes from building better context.

I FINALLY FIGURED OUT WHY CLAUDE KEEPS FORGETTING THINGS. For months, I thought Claude’s memory was broken. I’d spend 20 minutes explaining my project few chats later, it would forget important stuff and remember something completely random. Turns out the problem wasn’t Claude. It was how I was using it. Here’s the system that fixed it LEVEL 1: Clean up the basics (5 mins) - Remove old memories you don’t need - Add proper project instructions - Tell Claude exactly what should and shouldn’t be remembered Most people never do this and then wonder why memory feels inconsistent. LEVEL 2: Build a context system (30-60 mins) Create a folder with: → Instructions.md → Memory.md → Context.md → Archive.md Now Claude has a dedicated place to store information instead of trying to remember everything from chat history. Massive difference. LEVEL 3: Build a real AI second brain → Connect Claude to your notes. → Research. → Documents. → Knowledge base. Instead of starting from zero every session, it builds context over time. This is when Claude stops feeling like a chatbot and starts feeling like an actual assistant. Most people are obsessed with prompts. The real power comes from building better context.

nordin.eth

50,500 views • 1 month ago

Really interesting Boris Cherny and Cat Wu interview on the move from Claude Code to Claude Tag. Anthropic's launched Claude Tag last week and it added a layer of persistent context and memory that would have been difficult to maintain with previous tools. - Claude Tag shows a bigger shift than faster coding inside Anthropic’s daily work. Claude Code helped one person work faster, but Claude Tag changes group behavior. - AI becomes more useful when it enters shared workspaces. - People no longer need to open a separate tool, frame a task, and monitor it. Claude can sit inside a channel, notice useful work, act, and report back. - That institutional memory turns AI from a helper into a workflow layer. A channel can teach Claude what to watch, what to ignore, and how to respond. That means the system improves through normal corrections, not separate training sessions. - Visibility spreads skill faster than private AI use. When stronger users show Claude how to debug, analyze data, or write PRs, others copy those patterns. - This turns AI adoption from individual experimentation into social learning across the company.

Really interesting Boris Cherny and Cat Wu interview on the move from Claude Code to Claude Tag. Anthropic's launched Claude Tag last week and it added a layer of persistent context and memory that would have been difficult to maintain with previous tools. - Claude Tag shows a bigger shift than faster coding inside Anthropic’s daily work. Claude Code helped one person work faster, but Claude Tag changes group behavior. - AI becomes more useful when it enters shared workspaces. - People no longer need to open a separate tool, frame a task, and monitor it. Claude can sit inside a channel, notice useful work, act, and report back. - That institutional memory turns AI from a helper into a workflow layer. A channel can teach Claude what to watch, what to ignore, and how to respond. That means the system improves through normal corrections, not separate training sessions. - Visibility spreads skill faster than private AI use. When stronger users show Claude how to debug, analyze data, or write PRs, others copy those patterns. - This turns AI adoption from individual experimentation into social learning across the company.

Rohan Paul

14,519 views • 9 days ago

Built a 3-layer Memory Stack that wires Claude Code directly into Obsidian with skills so it never forgets your project DNA, your notes, your standards, or your goals. Fixes most of Claude Code's memory issues.

Built a 3-layer Memory Stack that wires Claude Code directly into Obsidian with skills so it never forgets your project DNA, your notes, your standards, or your goals. Fixes most of Claude Code's memory issues.

WorldofAI

115,934 views • 3 months ago

I built a Claude skill that turns Claude Code into your personal coding tutor. The core insight: Claude Opus 4.5 is already the best tutor in the world. Anthropic cooked with this model! It has incredible emotional intelligence and deep coding knowledge. What this skill does is just provide a harness—a way for Claude to agentically build the right context about YOU so it can personalize the tutoring experience in exactly the right way. Here's what makes it work: Learner profile from day one. The first time you use it, Claude interviews you. It asks about your programming background, your goal (where do you want this to take you?), and who you are as a person. This gets saved and informs every single tutorial it ever writes for you. From the very first interaction, everything is 100% personalized. Tutorials that use YOUR code. When you ask to learn something, Claude doesn't give you generic examples from some blog post. It finds examples in the actual codebase you're working in. This makes concepts stick in a way abstract examples never do. Quiz mode with spaced repetition. You can run "/quiz-me" and Claude will test you on concepts you've learned. It tracks your understanding score for each tutorial. Then it uses spaced repetition to prioritize the next quiz—concepts you're shaky on come back in 2 days, concepts you've mastered fade to 55+ day intervals. It literally builds retention into the learning process. One central knowledge base across all your projects. Whether you're joining a new company and want to understand their codebase, learning from an open source project, or leveling up on your own vibe-coded project—all your tutorials live in one place (~/coding-tutor-tutorials/). So your personal coding-tutor accompanies you across all your coding adventures. The whole thing is a feedback loop: learn → quiz → retain → learn more → quiz → retain. Your tutorials evolve, your knowledge compounds, and Claude gets better at teaching YOU specifically over time. To install it in Claude Code: • Run /plugin to open the plugin manager • Add marketplace nityeshaga/claude-code-essentials • Enable coding-tutor plugin Here's the Github: And here's 20-mins of me walking you through how to use this plugin and how it works 👇🏽 Let me know if you use it to teach yourself something cool!

Nityesh

64,494 views • 6 months ago

Claude Code tip: create an agent that specialises in code review and security. Then add a new memory entry with a nickname for it so you can call it anytime. My code review and security agent is called Big Tony.

Claude Code tip: create an agent that specialises in code review and security. Then add a new memory entry with a nickname for it so you can call it anytime. My code review and security agent is called Big Tony.

Richie - oss/acc

134,422 views • 6 months ago

We've rolled out a new auto-memory feature. Claude now remembers what it learns across sessions — your project context, debugging patterns, preferred approaches — and recalls it later without you having to write anything down.

We've rolled out a new auto-memory feature. Claude now remembers what it learns across sessions — your project context, debugging patterns, preferred approaches — and recalls it later without you having to write anything down.

Thariq

3,191,737 views • 4 months ago

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

113,042 views • 29 days ago