Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

You probably don’t use just one AI agent anymore. Maybe Codex for coding. Claude Code for research. Cursor for quick edits. Hermes for the rest. Each one is great at something different. But every time you switch, you have to start over — re-explaining your project, preferences, and the... show more

Hasan

50,699 subscribers

22,362 görüntüleme • 17 gün önce •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

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

Benzer Videolar

I've spent 2 months teaching my AI how I work again and again Claude Code knows one thing. Cursor knows another. Codex starts from scratch. OpenClaw has its own memory. None of them remember what the others learned. Memmy brings those histories into one local, user-controlled memory—so you can switch agents without re-explaining your projects, decisions, and preferences. Switch agents without rebuilding your context. Let every AI remember the same you. GitHub: ProductHunt:

I've spent 2 months teaching my AI how I work again and again Claude Code knows one thing. Cursor knows another. Codex starts from scratch. OpenClaw has its own memory. None of them remember what the others learned. Memmy brings those histories into one local, user-controlled memory—so you can switch agents without re-explaining your projects, decisions, and preferences. Switch agents without rebuilding your context. Let every AI remember the same you. GitHub: ProductHunt:

Priyank Ahuja

13,228 görüntüleme • 15 gün önce

🧲 Meet Magnet — the AI workspace for agentic coding. Build software with Claude Code, Cursor, Codex & co. → Write a ticket → Magnet assembles context → Fires to Claude Code, Deep Research, and other agent sessions in parallel Git worktree sandboxes → PRs appear → Use agents to help you spec, research, and decompose tasks Let your agents cook!

🧲 Meet Magnet — the AI workspace for agentic coding. Build software with Claude Code, Cursor, Codex & co. → Write a ticket → Magnet assembles context → Fires to Claude Code, Deep Research, and other agent sessions in parallel Git worktree sandboxes → PRs appear → Use agents to help you spec, research, and decompose tasks Let your agents cook!

Nicolae Rusan

16,608 görüntüleme • 1 yıl önce

Introducing watchmen. It writes the skill files your coding agents should already have from your own sessions, shared across Claude Code, Codex, and pi, so you stop paying tokens to re-explain what your agent learned last week. Local and open-source.

Introducing watchmen. It writes the skill files your coding agents should already have from your own sessions, shared across Claude Code, Codex, and pi, so you stop paying tokens to re-explain what your agent learned last week. Local and open-source.

Dria

43,967 görüntüleme • 2 ay önce

If you use Cursor for coding, Claude Code for debugging, and local agents for automation, you almost certainly have a context problem. Every tool acts like an isolated employee. One assistant forgets what the other just learned. The biggest bottleneck in multi-agent workflows right now isn’t reasoning. It’s collective amnesia, combined with zero communication between agents. Memmy just launched a smart fix for this: a local, cross-agent memory layer. Instead of re-pasting your context everywhere, Memmy gives your stack a shared memory hub: → accumulate knowledge once, then use it across Cursor, Codex, and OpenClaw → automatically scan and import your existing agent history, so you don’t have to start from zero → keep your memory local, while model usage depends on your chosen provider or BYOK setup And it isn’t just a memory plugin. It’s a complete personal AI runtime with both MCP and a CLI. Memmy officially launched on Product Hunt, and the team is giving early users experiencing context fragmentation a free trial with 2M GPT tokens. Check it out and support the team with an upvote: → Best part? It’s also open-source for devs who want to build their own agents 🔥 Repo in 🧵↓

If you use Cursor for coding, Claude Code for debugging, and local agents for automation, you almost certainly have a context problem. Every tool acts like an isolated employee. One assistant forgets what the other just learned. The biggest bottleneck in multi-agent workflows right now isn’t reasoning. It’s collective amnesia, combined with zero communication between agents. Memmy just launched a smart fix for this: a local, cross-agent memory layer. Instead of re-pasting your context everywhere, Memmy gives your stack a shared memory hub: → accumulate knowledge once, then use it across Cursor, Codex, and OpenClaw → automatically scan and import your existing agent history, so you don’t have to start from zero → keep your memory local, while model usage depends on your chosen provider or BYOK setup And it isn’t just a memory plugin. It’s a complete personal AI runtime with both MCP and a CLI. Memmy officially launched on Product Hunt, and the team is giving early users experiencing context fragmentation a free trial with 2M GPT tokens. Check it out and support the team with an upvote: → Best part? It’s also open-source for devs who want to build their own agents 🔥 Repo in 🧵↓

Charly Wargnier

203,456 görüntüleme • 14 gün önce

I built a new plugin! You can now trigger Codex from Claude Code! Use the Codex plugin for Claude Code to delegate tasks to Codex or have Codex review your changes using your ChatGPT subscription. Start by installing the plugin:

I built a new plugin! You can now trigger Codex from Claude Code! Use the Codex plugin for Claude Code to delegate tasks to Codex or have Codex review your changes using your ChatGPT subscription. Start by installing the plugin:

dominik kundel

1,287,342 görüntüleme • 4 ay önce

Wow Anthropic just released Claude Code for Web/Mobile, and it changes everything Now AI Agents can build apps for you 24/7 Here's your full beginner's guide to building an AI agent army that works for you all day (trust me you want to bookmark this one)

Wow Anthropic just released Claude Code for Web/Mobile, and it changes everything Now AI Agents can build apps for you 24/7 Here's your full beginner's guide to building an AI agent army that works for you all day (trust me you want to bookmark this one)

Alex Finn

160,772 görüntüleme • 9 ay önce

Today we open the Zapier SDK to everyone. If you're building with AI agents, this is for you. I've been using this for 2 months. It's totally changed how I do my job. You install it in your coding agent. Cursor, Claude Code, Codex, whatever you use. Now that agent has access to 8,000+ apps through Zapier and can do anything those APIs can do. I think it’s the most powerful thing we’ve launched in years. Now in open beta. Just give this link right to your agent:

Today we open the Zapier SDK to everyone. If you're building with AI agents, this is for you. I've been using this for 2 months. It's totally changed how I do my job. You install it in your coding agent. Cursor, Claude Code, Codex, whatever you use. Now that agent has access to 8,000+ apps through Zapier and can do anything those APIs can do. I think it’s the most powerful thing we’ve launched in years. Now in open beta. Just give this link right to your agent:

Wade Foster

174,901 görüntüleme • 4 ay önce

Don’t know how to use Remotion with Claude Code? We got you. This video is fully made with Video Agent. Avatar, script, motion graphics, and the final edits all with one prompt. Try Video Agent for free on HeyGen

Joshua Xu

172,749 görüntüleme • 6 ay önce

CLAUDE CODE IS NOW FREE AND YOU CAN BUILD AN ENTIRE AI CODING SYSTEM WITH 1M CONTEXT, AGENT OS AND OBSIDIAN MEMORY WITHOUT PAYING FOR ANY OF IT. The stack gets smarter over time and costs you nothing to run.

CLAUDE CODE IS NOW FREE AND YOU CAN BUILD AN ENTIRE AI CODING SYSTEM WITH 1M CONTEXT, AGENT OS AND OBSIDIAN MEMORY WITHOUT PAYING FOR ANY OF IT. The stack gets smarter over time and costs you nothing to run.

0xMarioNawfal

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

Claude Code sub-agents is probably the easiest way to build complex, custom agentic systems. Not just for code, but for anything you can imagine. Watch me build a multi-agent deep research system with Claude Code subagents. Chain subagents with /commands for reliability.

Claude Code sub-agents is probably the easiest way to build complex, custom agentic systems. Not just for code, but for anything you can imagine. Watch me build a multi-agent deep research system with Claude Code subagents. Chain subagents with /commands for reliability.

elvis

190,095 görüntüleme • 1 yıl önce

HERMES AGENT LEARNS FROM ITS OWN MISTAKES. UPDATES ITS MEMORY. CREATES ITS OWN SKILLS. NO CLOUD. EVERYTHING STORED LOCALLY. THIS IS HOW THE SELF-IMPROVING LOOP WORKS. most agents start from zero every session. Hermes carries forward what it learned. THREE MEMORY SYSTEMS: 1. PROCEDURAL MEMORY (how to act) stored in ~/.hermes/skills/ as SKILL.md files. when the agent repeats a complex workflow, it saves the procedure as a reusable skill. next time the same task comes up, it follows the skill instead of figuring it out again. you can also create skills explicitly: "create a skill called video-prep that captures how I format my video scripts. spoken english, define jargon inline, no em-dashes, close with a catchphrase." the agent writes the SKILL.md. available as a slash command from that moment. Hermes ships with 90+ skills. the number grows the longer you use it. 2. SEMANTIC MEMORY (durable facts about you) stored in ~/.hermes/memory/memory.md the agent scans conversations for facts worth remembering. preferences, habits, corrections, project details. real example from the video: agent tried to scrape a YouTube channel. URL was wrong. it failed. it updated memory.md with the correct URL pattern so it never makes the same mistake again. you can also save explicitly: "save to memory that my favorite testing framework is pytest" the agent updates memory.md immediately. this file loads into context on every session. the agent knows you better every week. 3. EPISODIC MEMORY (chat history) stored in ~/.hermes/state.db (local SQLite). every conversation. every tool call. every result. searchable with FTS5 full-text search. "search our past sessions. what was the first thing I ever said to you?" the agent queries state.db and finds it. over time, auxiliary models consolidate episodic memory into semantic memory. distilling recurring patterns into durable facts. THE SELF-IMPROVING LOOP: every agent run follows this cycle: → you send a prompt → working memory loads: SOUL.md + memory.md + relevant skills + chat history → agent calls tools (terminal, browser, delegate_task) → agent completes the task, replies to you → AFTER the reply: agent checks "did I learn something worth saving?" → if yes: updates memory.md or creates a new skill → next session starts smarter than the last this happens automatically. you don't ask the agent to learn. it decides what to remember on its own. WHAT MAKES THIS DIFFERENT FROM CLAUDE CODE: Claude Code has memory too. but Hermes stores everything locally. no cloud. your data never leaves your machine. Claude Code doesn't auto-create skills from experience. Hermes turns repeated workflows into reusable procedures. Claude Code memory is instruction-based. Hermes memory is conversational and self-updating. over months of usage, Hermes builds a knowledge base of your preferences, your projects, your mistakes, and the procedures that work for your specific workflow. the agent that remembers your birthday also remembers why your last deploy failed. NO EMBEDDINGS. PLAIN TEXT. Hermes does not use embeddings or RAG for memory. skill and memory search runs on plain text keyword matching. simpler. faster. no vector database to maintain. works entirely offline on your local machine. DELEGATE TO CLAUDE CODE: Hermes can spawn a sub-agent that runs Claude Code in headless mode: "spawn a sub-agent using Claude CLI to build a Python script that fetches the top 5 Hacker News stories to markdown." Hermes delegates. Claude Code writes the code. result returns to Hermes. Hermes runs the script and delivers the output. use Hermes for orchestration. use Claude Code for heavy coding. both tools. not competitors. WHAT HERMES DOES NOT HAVE: no built-in eval or LMOps system. no LangSmith, no LangFuse integration out of the box. trajectory export and logs exist but there is no automated quality tracking. if you need eval, build it yourself or connect external tools. the loop is self-improving. measuring how well it improves is on you. comment LOOP and I'll send you the configs that control how fast Hermes learns and what it remembers. memory limits, skill auto-creation triggers, and the auxiliary model that runs the learning. Replace your entire team with 8 hermes agents👇

HERMES AGENT LEARNS FROM ITS OWN MISTAKES. UPDATES ITS MEMORY. CREATES ITS OWN SKILLS. NO CLOUD. EVERYTHING STORED LOCALLY. THIS IS HOW THE SELF-IMPROVING LOOP WORKS. most agents start from zero every session. Hermes carries forward what it learned. THREE MEMORY SYSTEMS: 1. PROCEDURAL MEMORY (how to act) stored in ~/.hermes/skills/ as SKILL.md files. when the agent repeats a complex workflow, it saves the procedure as a reusable skill. next time the same task comes up, it follows the skill instead of figuring it out again. you can also create skills explicitly: "create a skill called video-prep that captures how I format my video scripts. spoken english, define jargon inline, no em-dashes, close with a catchphrase." the agent writes the SKILL.md. available as a slash command from that moment. Hermes ships with 90+ skills. the number grows the longer you use it. 2. SEMANTIC MEMORY (durable facts about you) stored in ~/.hermes/memory/memory.md the agent scans conversations for facts worth remembering. preferences, habits, corrections, project details. real example from the video: agent tried to scrape a YouTube channel. URL was wrong. it failed. it updated memory.md with the correct URL pattern so it never makes the same mistake again. you can also save explicitly: "save to memory that my favorite testing framework is pytest" the agent updates memory.md immediately. this file loads into context on every session. the agent knows you better every week. 3. EPISODIC MEMORY (chat history) stored in ~/.hermes/state.db (local SQLite). every conversation. every tool call. every result. searchable with FTS5 full-text search. "search our past sessions. what was the first thing I ever said to you?" the agent queries state.db and finds it. over time, auxiliary models consolidate episodic memory into semantic memory. distilling recurring patterns into durable facts. THE SELF-IMPROVING LOOP: every agent run follows this cycle: → you send a prompt → working memory loads: SOUL.md + memory.md + relevant skills + chat history → agent calls tools (terminal, browser, delegate_task) → agent completes the task, replies to you → AFTER the reply: agent checks "did I learn something worth saving?" → if yes: updates memory.md or creates a new skill → next session starts smarter than the last this happens automatically. you don't ask the agent to learn. it decides what to remember on its own. WHAT MAKES THIS DIFFERENT FROM CLAUDE CODE: Claude Code has memory too. but Hermes stores everything locally. no cloud. your data never leaves your machine. Claude Code doesn't auto-create skills from experience. Hermes turns repeated workflows into reusable procedures. Claude Code memory is instruction-based. Hermes memory is conversational and self-updating. over months of usage, Hermes builds a knowledge base of your preferences, your projects, your mistakes, and the procedures that work for your specific workflow. the agent that remembers your birthday also remembers why your last deploy failed. NO EMBEDDINGS. PLAIN TEXT. Hermes does not use embeddings or RAG for memory. skill and memory search runs on plain text keyword matching. simpler. faster. no vector database to maintain. works entirely offline on your local machine. DELEGATE TO CLAUDE CODE: Hermes can spawn a sub-agent that runs Claude Code in headless mode: "spawn a sub-agent using Claude CLI to build a Python script that fetches the top 5 Hacker News stories to markdown." Hermes delegates. Claude Code writes the code. result returns to Hermes. Hermes runs the script and delivers the output. use Hermes for orchestration. use Claude Code for heavy coding. both tools. not competitors. WHAT HERMES DOES NOT HAVE: no built-in eval or LMOps system. no LangSmith, no LangFuse integration out of the box. trajectory export and logs exist but there is no automated quality tracking. if you need eval, build it yourself or connect external tools. the loop is self-improving. measuring how well it improves is on you. comment LOOP and I'll send you the configs that control how fast Hermes learns and what it remembers. memory limits, skill auto-creation triggers, and the auxiliary model that runs the learning. Replace your entire team with 8 hermes agents👇

YanXbt

22,720 görüntüleme • 1 ay önce

Have you started to write code with Cursor using AI but don’t know how to deploy it? Just use Replit’s new 1-click “Connect to Cursor” button. It’s the easiest way to get your project live on the internet for you to share. Takes <5min to deploy.

Have you started to write code with Cursor using AI but don’t know how to deploy it? Just use Replit’s new 1-click “Connect to Cursor” button. It’s the easiest way to get your project live on the internet for you to share. Takes <5min to deploy.

Mckay Wrigley

154,266 görüntüleme • 1 yıl önce

Three skills I use every day in Claude Code and Codex to solve my hardest problems: 1️⃣ /agent-watchdog When I have one agent like Codex working on a task and I don't fully trust it's going to do everything right, I'll open up another one like Claude Code and tell it to watchdog the Codex thread. You can copy the Codex deep link into Claude Code and it'll look at the prompt you sent, watch the Codex thread until it's done, then compare the Codex solution to how it was planning to solve it and automatically fix anything that Codex missed. It can also test the work of the other agent end-to-end. Similar to the idea of OpenRouter's new Fusion feature, I've definitely found that two models thinking through a problem and checking each other's work can be wildly more impactful than just one. 2️⃣ /plan-arbiter Similar ideas as /agent-watchdog - but with this one you have both make plans, compare plans, negotiate the differences, and make a final plan to execute. I find Claude Code is better at writing plans, but Codex is faster and cheaper to execute on them. Then I usually have Claude Code watchdog the Codex work and fix anything that was missed. 3️⃣ /read-the-damn-docs One thing that drives me crazy with coding agents is they're so reluctant to look up docs. They'll just guess and guess and guess at the right API surface for things, or the right solution to an integration of two things. Once I explicitly tell it to look up the docs, it says "Oh, I see the answer," and it fixes the problem. So I made the /read-the-damn-docs skill. Add it and your agents will know when and how to do efficient web searches to look up docs for the types of problems you really should look up docs for. All of these are totally open source over on my GitHub. If you try them, let me know your feedback. Will link to them below:

Three skills I use every day in Claude Code and Codex to solve my hardest problems: 1️⃣ /agent-watchdog When I have one agent like Codex working on a task and I don't fully trust it's going to do everything right, I'll open up another one like Claude Code and tell it to watchdog the Codex thread. You can copy the Codex deep link into Claude Code and it'll look at the prompt you sent, watch the Codex thread until it's done, then compare the Codex solution to how it was planning to solve it and automatically fix anything that Codex missed. It can also test the work of the other agent end-to-end. Similar to the idea of OpenRouter's new Fusion feature, I've definitely found that two models thinking through a problem and checking each other's work can be wildly more impactful than just one. 2️⃣ /plan-arbiter Similar ideas as /agent-watchdog - but with this one you have both make plans, compare plans, negotiate the differences, and make a final plan to execute. I find Claude Code is better at writing plans, but Codex is faster and cheaper to execute on them. Then I usually have Claude Code watchdog the Codex work and fix anything that was missed. 3️⃣ /read-the-damn-docs One thing that drives me crazy with coding agents is they're so reluctant to look up docs. They'll just guess and guess and guess at the right API surface for things, or the right solution to an integration of two things. Once I explicitly tell it to look up the docs, it says "Oh, I see the answer," and it fixes the problem. So I made the /read-the-damn-docs skill. Add it and your agents will know when and how to do efficient web searches to look up docs for the types of problems you really should look up docs for. All of these are totally open source over on my GitHub. If you try them, let me know your feedback. Will link to them below:

Steve (Builder.io)

43,089 görüntüleme • 1 ay önce

Imagine a computer where you don’t need to learn 10 apps to get work done. You just tell it what you want, and it adapts to how you work. I tested Happycapy with a real use case and created an image and a video. No coding, no complex software. Do this: - Build automations that run on schedule - Deploy agent teams that work for you AI molds how you work, not the other way around. If you can use a computer, you can make anything happen. Start your first Automation and Agent teams today.

Imagine a computer where you don’t need to learn 10 apps to get work done. You just tell it what you want, and it adapts to how you work. I tested Happycapy with a real use case and created an image and a video. No coding, no complex software. Do this: - Build automations that run on schedule - Deploy agent teams that work for you AI molds how you work, not the other way around. If you can use a computer, you can make anything happen. Start your first Automation and Agent teams today.

Aaliya

17,042 görüntüleme • 6 ay önce

How to manage multiple AI agents at once: I run 10 to 15 parallel AI agent threads a day. Some days even more. Hermes, OpenClaw, Claude Code, Codex, all going at once. But the problem is more agents doesn't equal more output. Past a certain number of threads, you lose context. You forget what you told which agent. You duplicate work across two threads doing the same job. This is how we're solving for it:

How to manage multiple AI agents at once: I run 10 to 15 parallel AI agent threads a day. Some days even more. Hermes, OpenClaw, Claude Code, Codex, all going at once. But the problem is more agents doesn't equal more output. Past a certain number of threads, you lose context. You forget what you told which agent. You duplicate work across two threads doing the same job. This is how we're solving for it:

ericosiu

11,868 görüntüleme • 1 ay önce

Software Engineering Expectations for 2026 - The majority of your code should be written by AI now - Cursor/Codex/Claude Code/Gemini/etc - You should try all the tooling and switch between them, as each one gets an edge over the others depending on the release cycle. - You should be using AI to check the code that is written by AI - Have AI write tests - Have AI read logs - Have AI navigate your browser - I don't do this every time because sometimes it's simple enough to check it myself - You should still skim code changes - This can be a lighter skim on internal tools and a heavier read through on customer facing code - Use AI to help you define specs

Software Engineering Expectations for 2026 - The majority of your code should be written by AI now - Cursor/Codex/Claude Code/Gemini/etc - You should try all the tooling and switch between them, as each one gets an edge over the others depending on the release cycle. - You should be using AI to check the code that is written by AI - Have AI write tests - Have AI read logs - Have AI navigate your browser - I don't do this every time because sometimes it's simple enough to check it myself - You should still skim code changes - This can be a lighter skim on internal tools and a heavier read through on customer facing code - Use AI to help you define specs

Ben Awad

534,861 görüntüleme • 7 ay önce

OpenAI has just released GPT-5-Codex specifically for coding! Friendly reminder that they've a VS Code extension that you can use with your ChatGPT account at NO additional cost. Basically a strong alternative to Claude Code or Cursor. (Setup below)

OpenAI has just released GPT-5-Codex specifically for coding! Friendly reminder that they've a VS Code extension that you can use with your ChatGPT account at NO additional cost. Basically a strong alternative to Claude Code or Cursor. (Setup below)

Paul Couvert

261,956 görüntüleme • 11 ay önce

I have built a Windows x64 sampling profiler for native code+C# to be used by coding agents. Why? Because it is irresponsible to let computers write code but give them no tools to evaluate the performance of their code. Stop guessing, start measuring. -> How does it work? Just point your agent to the profiler and let them measure and optimize. Or record a trace yourself and let the agent interpret the results for you. Works with Claude Code, Codex, pi, etc. The profiler also has a couple of neat features by itself like giving you estimates for how much time your code is spending on memory stalls and annotating disassembly with inlining information. Take a look and try it for free!

I have built a Windows x64 sampling profiler for native code+C# to be used by coding agents. Why? Because it is irresponsible to let computers write code but give them no tools to evaluate the performance of their code. Stop guessing, start measuring. -> How does it work? Just point your agent to the profiler and let them measure and optimize. Or record a trace yourself and let the agent interpret the results for you. Works with Claude Code, Codex, pi, etc. The profiler also has a couple of neat features by itself like giving you estimates for how much time your code is spending on memory stalls and annotating disassembly with inlining information. Take a look and try it for free!

Sebastian Schöner

13,057 görüntüleme • 3 ay önce

🚨 this chinese guy makes over $1,000,000 a year… by building AI agents. no employees. no massive startup. he just keeps building. while most people are still asking ChatGPT random questions, he’s using Claude to build software that solves real problems. this is what people call vibe coding. he opens Claude and says: “build me an AI agent for real estate businesses that creates property videos.” Claude writes the code. builds the interface. adds subscriptions. helps deploy the app. within a day, he has a working product. then he starts building the next one. that’s the part most people don’t understand. he isn’t trying to build one billion-dollar company. he’s building dozens of AI agents, each solving one problem for one industry. → an AI agent for dentists → an AI agent for ecommerce brands → an AI agent for podcasters → an AI agent for real estate businesses each one automates work that people normally do by hand. each one is built with simple prompts. each one can become a real business. the crazy part? you don’t need to be a software engineer anymore. you need to know how to think like a builder. how to spot problems. how to explain solutions to AI. and how to ship. that’s exactly why i’m reading this article: “How to Actually Build Your First AI Agent.” because this is the skill that’s creating the next generation of builders. the people who learn to build AI agents today won’t just use AI. they’ll own the tools everyone else ends up paying for.

🚨 this chinese guy makes over $1,000,000 a year… by building AI agents. no employees. no massive startup. he just keeps building. while most people are still asking ChatGPT random questions, he’s using Claude to build software that solves real problems. this is what people call vibe coding. he opens Claude and says: “build me an AI agent for real estate businesses that creates property videos.” Claude writes the code. builds the interface. adds subscriptions. helps deploy the app. within a day, he has a working product. then he starts building the next one. that’s the part most people don’t understand. he isn’t trying to build one billion-dollar company. he’s building dozens of AI agents, each solving one problem for one industry. → an AI agent for dentists → an AI agent for ecommerce brands → an AI agent for podcasters → an AI agent for real estate businesses each one automates work that people normally do by hand. each one is built with simple prompts. each one can become a real business. the crazy part? you don’t need to be a software engineer anymore. you need to know how to think like a builder. how to spot problems. how to explain solutions to AI. and how to ship. that’s exactly why i’m reading this article: “How to Actually Build Your First AI Agent.” because this is the skill that’s creating the next generation of builders. the people who learn to build AI agents today won’t just use AI. they’ll own the tools everyone else ends up paying for.

MIKE

38,108 görüntüleme • 1 ay önce

Start building for an agent-first world. If you have a product, you need to start offering skills for Claude, Codex, Cursor, and any other agents. Your skills should specify: • How to navigate and use your product • Best practices the agent must follow • Detailed instructions on how to accomplish things • Anti-patterns to avoid Redis is one of the most popular in-memory data stores in the world, and they just released their agent skills. It takes one second to install, and it will turn your agent into a Senior Redis Engineer: $ npx skills add redis/agent-skills In the attached video, I show you how to install it as a plugin in Claude Code and some of its benefits. This is the easiest way to "teach" models what they don't know and keep their knowledge up to date. If you ask me, skills is literally one of the most brilliant ideas that Anthropic has put out there. If you use Redis, their skill is a must-have. If you don't, this skill will show you how to build and structure yours. Here is what their skill teaches your agent: 1. Current patterns for common use cases: caching, rate limiting, session management, vector search, semantic caching, pub/sub, streams. 2. Which data structure to use and when: hashes vs. JSON vs. sorted sets vs. vector sets. 3. Anti-patterns to avoid: no KEYS in loops, no unbounded key growth, no large values that amplify every operation. 4. Production-aware defaults: connection pooling, pipelining, cluster compatibility, error handling that doesn't silently swallow failures.

Start building for an agent-first world. If you have a product, you need to start offering skills for Claude, Codex, Cursor, and any other agents. Your skills should specify: • How to navigate and use your product • Best practices the agent must follow • Detailed instructions on how to accomplish things • Anti-patterns to avoid Redis is one of the most popular in-memory data stores in the world, and they just released their agent skills. It takes one second to install, and it will turn your agent into a Senior Redis Engineer: $ npx skills add redis/agent-skills In the attached video, I show you how to install it as a plugin in Claude Code and some of its benefits. This is the easiest way to "teach" models what they don't know and keep their knowledge up to date. If you ask me, skills is literally one of the most brilliant ideas that Anthropic has put out there. If you use Redis, their skill is a must-have. If you don't, this skill will show you how to build and structure yours. Here is what their skill teaches your agent: 1. Current patterns for common use cases: caching, rate limiting, session management, vector search, semantic caching, pub/sub, streams. 2. Which data structure to use and when: hashes vs. JSON vs. sorted sets vs. vector sets. 3. Anti-patterns to avoid: no KEYS in loops, no unbounded key growth, no large values that amplify every operation. 4. Production-aware defaults: connection pooling, pipelining, cluster compatibility, error handling that doesn't silently swallow failures.

Santiago

37,546 görüntüleme • 5 ay önce