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

I’ve been working on dunk. It’s a terminal diff reviewer where you mark issues inline, then let a coding agent fix them. It started as a fork of hunk, but I stripped it down to the loop I need: review → my comments → agent fixes I’m spending time... show more

Amir Salihefendić

34,052 subscribers

13,156 görüntüleme • 4 ay ö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 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,118 görüntüleme • 5 ay önce

well thats fucking it - anthropic has officially replaced software engineers. claude is now a 24 hr autonomous coding agent. claude can now operate your entire computer and CLAUDE CODE = end-to-end software engineering: - claude writes the code for you - then literally opens the app it coded - clicks through the entire app and find bugs - then fixes the bugs and improves the app in hours. previously claude generated code, you run it and give claude feedback. thats completely gone now. all in a continuous loop without leaving your terminal 😂 we're barely through monday. well done lol

well thats fucking it - anthropic has officially replaced software engineers. claude is now a 24 hr autonomous coding agent. claude can now operate your entire computer and CLAUDE CODE = end-to-end software engineering: - claude writes the code for you - then literally opens the app it coded - clicks through the entire app and find bugs - then fixes the bugs and improves the app in hours. previously claude generated code, you run it and give claude feedback. thats completely gone now. all in a continuous loop without leaving your terminal 😂 we're barely through monday. well done lol

Ejaaz

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

The bottleneck in coding is now the time it takes a human to review agent-generated code. But existing review UIs don't work well for agents. So we built a new one into Amp.

The bottleneck in coding is now the time it takes a human to review agent-generated code. But existing review UIs don't work well for agents. So we built a new one into Amp.

Beyang

63,082 görüntüleme • 11 ay önce

This is one of the coolest open-source AI agent projects I've seen in a while: 'Understand Anything' It's a plugin for Claude Code, Codex, OpenCode etc. that analyzes your codebase and turns it into a knowledge base that you can interact with. It explains the codebase to you, rather than showing you the structure. It seems like it's designed for code but I opened my Obsidian vault of podcast highlights in Claude Code, then ran /understand. The result is a knowledge graph that I can search of highlights from 888 podcast episodes and 144K lines of markdown text.

This is one of the coolest open-source AI agent projects I've seen in a while: 'Understand Anything' It's a plugin for Claude Code, Codex, OpenCode etc. that analyzes your codebase and turns it into a knowledge base that you can interact with. It explains the codebase to you, rather than showing you the structure. It seems like it's designed for code but I opened my Obsidian vault of podcast highlights in Claude Code, then ran /understand. The result is a knowledge graph that I can search of highlights from 888 podcast episodes and 144K lines of markdown text.

Dan McAteer

174,887 görüntüleme • 3 ay önce

Lead of Claude Code: "100% of our code at Anthropic is now shipped by Claude. Over 30% of it is written using /loops. Loop engineering is the future of coding. Loops are as big a shift as move from source coding to agents" in a 1-hour podcast, a Claude Code lead engineer shares the internal setup for building the #1 coding tool. It’s the most useful breakdown of how the Anthropic team uses Claude internally that I’ve seen on YouTube. Worth more than a $500 vibe-coding course.

Lead of Claude Code: "100% of our code at Anthropic is now shipped by Claude. Over 30% of it is written using /loops. Loop engineering is the future of coding. Loops are as big a shift as move from source coding to agents" in a 1-hour podcast, a Claude Code lead engineer shares the internal setup for building the #1 coding tool. It’s the most useful breakdown of how the Anthropic team uses Claude internally that I’ve seen on YouTube. Worth more than a $500 vibe-coding course.

Codez

37,770 görüntüleme • 3 ay önce

My favorite way of interacting with Claude Code is to have it generate static HTML files as outputs (reports, explorations, code structure, mockups etc.) I wanted to iterate on the file by commenting in browser and having Claude update the output live. So, I built this Claude Skill👇 How it works: - Install Claude Code skill (ask it to clone repo) - Build an HTML page for anything (e.g. research coding agents and generate HTML report) - Ask it to make the page interactive That's it. CC will launch a localhost server and allow you to then leave comments on the page itself and once it updates, will give you a tour of changes. It's like Google Docs kind of comments/iteration but for HTML pages.

My favorite way of interacting with Claude Code is to have it generate static HTML files as outputs (reports, explorations, code structure, mockups etc.) I wanted to iterate on the file by commenting in browser and having Claude update the output live. So, I built this Claude Skill👇 How it works: - Install Claude Code skill (ask it to clone repo) - Build an HTML page for anything (e.g. research coding agents and generate HTML report) - Ask it to make the page interactive That's it. CC will launch a localhost server and allow you to then leave comments on the page itself and once it updates, will give you a tour of changes. It's like Google Docs kind of comments/iteration but for HTML pages.

Paras Chopra

216,101 görüntüleme • 4 ay ö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 • 3 ay önce

You don’t need new ways to talk to your agents, you need new ways for your agents to talk to you 🫵 (do you?) Introducing Remoko: your mobile agent relay I wanted a way for my long-running agents to send me iOS push notifications via MCP: questions, approvals, check-ins, feedback, update/cancel, execution reports, etc since I had to make it a testflight, you can try it too with your Codex, Claude Code, etc:

You don’t need new ways to talk to your agents, you need new ways for your agents to talk to you 🫵 (do you?) Introducing Remoko: your mobile agent relay I wanted a way for my long-running agents to send me iOS push notifications via MCP: questions, approvals, check-ins, feedback, update/cancel, execution reports, etc since I had to make it a testflight, you can try it too with your Codex, Claude Code, etc:

Yohei

62,022 görüntüleme • 1 ay önce

AI is changing the software engineering craft. Anders Hejlsberg (Anders Hejlsberg) - creator of C#, TypeScript and industry legend - on why code review needs to get more enjoyable in response: #1 - AI is shifting the craft from writing code, to reviewing code: "In a sense, we're all turning into project managers. We can have an army of junior programmers, called agents, that will just spit out reams of code but someone's got to have the big picture and review all of that. And so, increasingly, our craft is going from one of writing the code, to one of reviewing the code and building the architecture of the code and overseeing the work. It's a different kind of craft. It's a different kind of enjoyment. I've always liked writing the code. To me that was the fulfilling part, seeing it work. In a way, AI robs a little bit of that, because I am less interested in reviewing code." #2 - The code review experience should be improved: "I think we could also make the process of reviewing code much more interesting than it is today. I mean, today, you see a list of diffs in alphabetical order and now it's up to you to make heads or tails of it. There are more pedagogical ways of presenting that. And you could have commentary generated by the AI that tells you what the changes are and whatever, and then tries to guide you along. So that symbiotic relationship, I think we need to work on that more and to keep the enjoyment in there."

AI is changing the software engineering craft. Anders Hejlsberg (Anders Hejlsberg) - creator of C#, TypeScript and industry legend - on why code review needs to get more enjoyable in response: #1 - AI is shifting the craft from writing code, to reviewing code: "In a sense, we're all turning into project managers. We can have an army of junior programmers, called agents, that will just spit out reams of code but someone's got to have the big picture and review all of that. And so, increasingly, our craft is going from one of writing the code, to one of reviewing the code and building the architecture of the code and overseeing the work. It's a different kind of craft. It's a different kind of enjoyment. I've always liked writing the code. To me that was the fulfilling part, seeing it work. In a way, AI robs a little bit of that, because I am less interested in reviewing code." #2 - The code review experience should be improved: "I think we could also make the process of reviewing code much more interesting than it is today. I mean, today, you see a list of diffs in alphabetical order and now it's up to you to make heads or tails of it. There are more pedagogical ways of presenting that. And you could have commentary generated by the AI that tells you what the changes are and whatever, and then tries to guide you along. So that symbiotic relationship, I think we need to work on that more and to keep the enjoyment in there."

The Pragmatic Engineer

39,073 görüntüleme • 4 ay önce

I recorded Claude fix two MiniJinja issues itself. It's Rust (which it sucks at), in a code base not really set up for vibe coding and it still succeeds. Yes, it takes 30 minutes, but it's hands off. Usually I let this work alone and review later.

I recorded Claude fix two MiniJinja issues itself. It's Rust (which it sucks at), in a code base not really set up for vibe coding and it still succeeds. Yes, it takes 30 minutes, but it's hands off. Usually I let this work alone and review later.

Armin Ronacher ⇌

39,262 görüntüleme • 1 yıl önce

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

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

Kanika

20,671 görüntüleme • 2 ay önce

If you're running multiple coding agents (Codex, Claude Code, Pi) at once, you're going to want to watch this. Herdr is a terminal multiplexer that actually understands your agents. Oh, and it has incredible mouse support. Bet I can convince you in 6 minutes:

If you're running multiple coding agents (Codex, Claude Code, Pi) at once, you're going to want to watch this. Herdr is a terminal multiplexer that actually understands your agents. Oh, and it has incredible mouse support. Bet I can convince you in 6 minutes:

Jilles Soeters

59,148 görüntüleme • 2 ay önce

SpaceXAI engineer Lauren Tan: "I'm running 20+ GrokBot agents with /loop and /goal inside pstack My bots ship code while I sleep At SpaceXAI, 85% of engineers are already running 10+ GrokBot agents as a team One Chief of Staff agent knows every other bot and manages the entire system" GrokBot → /loop → /goal → Chief of Staff → Agent Teams In a 1-hour workshop, Lauren shows how to build a team of GrokBot agents from scratch Research → Code → Review → Ship Worth more than most $1000 agent engineering courses Bookmark and watch it today Then read the full article on building a GrokBot agent team from scratch

SpaceXAI engineer Lauren Tan: "I'm running 20+ GrokBot agents with /loop and /goal inside pstack My bots ship code while I sleep At SpaceXAI, 85% of engineers are already running 10+ GrokBot agents as a team One Chief of Staff agent knows every other bot and manages the entire system" GrokBot → /loop → /goal → Chief of Staff → Agent Teams In a 1-hour workshop, Lauren shows how to build a team of GrokBot agents from scratch Research → Code → Review → Ship Worth more than most $1000 agent engineering courses Bookmark and watch it today Then read the full article on building a GrokBot agent team from scratch

kaori

100,219 görüntüleme • 21 gün önce

Zuckerberg says Meta's Llama race changes in the next 12-18 months: most of the code will be written by AI - not autocomplete, but agents that run tests and improve the model loop. "We're not trying to build a general developer tool. We are trying to build a coding agent and an AI research agent that basically advances Llama research specifically." "Sometime in the next 12 to 18 months, we'll reach the point where most of the code that's going towards these efforts is written by AI." "And I don't mean autocomplete." "I'm talking more like you give it a goal, it can run tests, it can improve things, it can find issues." "It writes higher quality code than the average very good person on the team already." The hidden bottleneck is not chat UX. It is closing the loop between AI research, code, tests, and self-improvement inside the lab.

Zuckerberg says Meta's Llama race changes in the next 12-18 months: most of the code will be written by AI - not autocomplete, but agents that run tests and improve the model loop. "We're not trying to build a general developer tool. We are trying to build a coding agent and an AI research agent that basically advances Llama research specifically." "Sometime in the next 12 to 18 months, we'll reach the point where most of the code that's going towards these efforts is written by AI." "And I don't mean autocomplete." "I'm talking more like you give it a goal, it can run tests, it can improve things, it can find issues." "It writes higher quality code than the average very good person on the team already." The hidden bottleneck is not chat UX. It is closing the loop between AI research, code, tests, and self-improvement inside the lab.

Karl Mehta

36,347 görüntüleme • 3 ay önce

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 way you like to work. Your agents know how to help you. They just don’t share a memory of you. memU just shipped an update that fixes this. One personal memory, shared across every agent and device you use. What Codex learned last night, Claude Code can remember this morning. 🧵

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 way you like to work. Your agents know how to help you. They just don’t share a memory of you. memU just shipped an update that fixes this. One personal memory, shared across every agent and device you use. What Codex learned last night, Claude Code can remember this morning. 🧵

Hasan

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

Have you ever been working in Claude Code or Codex and wished you could pick up this exact session in Hermes Agent? Now there's a single command that makes this possible! hermes --resume @(claude or codex) I made a video showing how to use them! Check it out!

Have you ever been working in Claude Code or Codex and wished you could pick up this exact session in Hermes Agent? Now there's a single command that makes this possible! hermes --resume @(claude or codex) I made a video showing how to use them! Check it out!

tonbi

68,018 görüntüleme • 20 gün önce

i hate the way tool calling works today, so i built a fix for it its called `executor` and it lets your agent run code to call any API / MCP / GraphQL server rather than installing CLIs this is a soft launch, you can try it with npm i -g executor but im still making it great

i hate the way tool calling works today, so i built a fix for it its called `executor` and it lets your agent run code to call any API / MCP / GraphQL server rather than installing CLIs this is a soft launch, you can try it with npm i -g executor but im still making it great

Rhys

130,265 görüntüleme • 6 ay önce

Reviewing AI-generated code is the new bottleneck. Writing code was slow before. Now, in a few minutes, you can generate virtually unlimited lines of code using AI. But developers are now spending 70% of their time checking that code. That's the new bottleneck. I've been using Cline, and they have a feature that actually helps with this: You can click a button and have Cline generate an inline explanation for every single line of AI-generated code. Take a look at the attached video. What it does: 1. You can read the code and the explanation together 2. You don't lose context while reviewing code 3. You understand the "why" behind each change And here is the best part: It works on any git diff. You can use it to review PRs, understand commits from other people, or catch up on a codebase you haven't touched in a while.

Reviewing AI-generated code is the new bottleneck. Writing code was slow before. Now, in a few minutes, you can generate virtually unlimited lines of code using AI. But developers are now spending 70% of their time checking that code. That's the new bottleneck. I've been using Cline, and they have a feature that actually helps with this: You can click a button and have Cline generate an inline explanation for every single line of AI-generated code. Take a look at the attached video. What it does: 1. You can read the code and the explanation together 2. You don't lose context while reviewing code 3. You understand the "why" behind each change And here is the best part: It works on any git diff. You can use it to review PRs, understand commits from other people, or catch up on a codebase you haven't touched in a while.

Santiago

64,438 görüntüleme • 9 ay önce

i vibecoded a fully working terminal from scratch using parallel remote agents, w/o editing a single line of code. took the best agent just ~6 hrs would take me ~6-12 mo to do the same by hand w/o ai the terminal def has bugs (i posted the gh link in the article so you can test it) but can run opencode, claude code, etc! i've been able to replace iterm with it. wrote up a guide for Extreme Vibecoding with Remote Agents👇

i vibecoded a fully working terminal from scratch using parallel remote agents, w/o editing a single line of code. took the best agent just ~6 hrs would take me ~6-12 mo to do the same by hand w/o ai the terminal def has bugs (i posted the gh link in the article so you can test it) but can run opencode, claude code, etc! i've been able to replace iterm with it. wrote up a guide for Extreme Vibecoding with Remote Agents👇

andrew gao

57,629 görüntüleme • 7 ay önce