Video wird geladen...

Video konnte nicht geladen werden

Beim Laden dieses Videos ist ein Problem aufgetreten. Dies könnte an einem vorübergehenden Netzwerkproblem liegen oder das Video ist möglicherweise nicht verfügbar.

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 Aufrufe • vor 2 Monaten •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

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

12,969 Aufrufe • vor 2 Monaten

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,156,581 Aufrufe • vor 3 Monaten

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 Aufrufe • vor 8 Monaten

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

173,339 Aufrufe • vor 29 Tagen

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

214,959 Aufrufe • vor 1 Monat

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)

42,501 Aufrufe • vor 27 Tagen

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,011 Aufrufe • vor 2 Monaten

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 Aufrufe • vor 1 Jahr

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

56,495 Aufrufe • vor 20 Tagen

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,337 Aufrufe • vor 29 Tagen

Using Claude Code as a general agent part 3: Getting Claude Code to Ask me clarifying questions... inline, by creating a Clarifying-Questions .md file What's in this file is how the agent should format clarifying questions before doing a specific task. Rather than coming up with ALL of the context I need to give to the agent, I state what I want at the top of the docuemnt then i tell claude to ask me clarifying questions IN THE DOCUMENT. The agent knows to format them as empty code blocks and all i need to do is fill them in then tell Claude Code to finish the task at hand. Kinda niche, but I use this for EVERYTHING now: 1. State what I want at top (Ad Scripts) 2. Type out relevant context that's in my head 3. Tell the agent to ask @ clarifying-questions 4. Quickly answer them with wispr flow in the document 5. Tell Claude to continue This would be useful for nearly every workflow.

Using Claude Code as a general agent part 3: Getting Claude Code to Ask me clarifying questions... inline, by creating a Clarifying-Questions .md file What's in this file is how the agent should format clarifying questions before doing a specific task. Rather than coming up with ALL of the context I need to give to the agent, I state what I want at the top of the docuemnt then i tell claude to ask me clarifying questions IN THE DOCUMENT. The agent knows to format them as empty code blocks and all i need to do is fill them in then tell Claude Code to finish the task at hand. Kinda niche, but I use this for EVERYTHING now: 1. State what I want at top (Ad Scripts) 2. Type out relevant context that's in my head 3. Tell the agent to ask @ clarifying-questions 4. Quickly answer them with wispr flow in the document 5. Tell Claude to continue This would be useful for nearly every workflow.

Riley Brown

27,664 Aufrufe • vor 7 Monaten

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

129,065 Aufrufe • vor 4 Monaten

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,399 Aufrufe • vor 7 Monaten

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 Aufrufe • vor 5 Monaten

🚨 OpenAI just launched Codex, a brand-new autonomous coding agent that can build features and fix bugs on its own. We’ve been using it Every 📧 for a few days, and I’m impressed. I invited Alexander Embiricos (ben davies), a member of the product staff responsible for Codex, to demo Codex and talk about it live on a special edition of AI & I: What Codex is and how it works Codex is designed to be used by senior engineers—it performs coding tasks like adding features or fixing bugs autonomously. It's built to allow you to start many sessions at once, so you can have multiple agents working in parallel. Codex is built to have "taste" OpenAI trained Codex to have the taste of a senior software engineer. It knows how big codebases work, how to write a good PR, and uses clean, minimal code. Why an “abundance mindset” is best for interacting with agents Codex is designed to allow users to delegate many tasks at once without getting caught up in the details. This lets you point an abundance of agents at a specific task like a difficult bug—it’s worth it even if only one of them succeeds. How OpenAI is thinking about agents Codex is one piece of a unified super-assistant OpenAI wants to eventually build—an agent that helps users easily get things done by selecting the right tools for them behind the scenes. OpenAI’s vision for the future of programming In the future developers will probably spend less time writing routine code and more time guiding agents, reviewing their work, and making strategy decisions. Programming will become more social, letting teams easily delegate multiple tasks at once, allowing people to focus on ideas and collaboration instead of routine coding. Watch below!

Dan Shipper 📧

145,487 Aufrufe • vor 1 Jahr

Claude Code creator Boris Cherny: "Verification is the single most important part of closed-loop development" "Companies underinvest in it, and that is the biggest mistake" In a 26-minute talk, Boris breaks down real AI coding loops with Spotify's Chief Engineer: 00:00 - Closed-loop development 08:33 - Why one-shot code generation fails 10:02 - Agentic verifier and PR success rate 12:00 - Verification loops without humans in the loop 14:00 - Tests, skills, CLAUDE.md, and MCP as the loop infrastructure 20:11 - Why consistent codebases make agents work better This one video is worth more than 100 Claude coding setup tutorials Bookmark and watch it today Then read the full guide on loop engineering below

Claude Code creator Boris Cherny: "Verification is the single most important part of closed-loop development" "Companies underinvest in it, and that is the biggest mistake" In a 26-minute talk, Boris breaks down real AI coding loops with Spotify's Chief Engineer: 00:00 - Closed-loop development 08:33 - Why one-shot code generation fails 10:02 - Agentic verifier and PR success rate 12:00 - Verification loops without humans in the loop 14:00 - Tests, skills, CLAUDE.md, and MCP as the loop infrastructure 20:11 - Why consistent codebases make agents work better This one video is worth more than 100 Claude coding setup tutorials Bookmark and watch it today Then read the full guide on loop engineering below

rari

69,140 Aufrufe • vor 3 Tagen

Loop engineering is great until something breaks. Here is how I improve the reliability of my agentic loops. I use human-in-the-loop (HITL). It's easy and extremely effective. Anyone can build this. My setup: I recorded a quick demo of how it all works. I shared recently that I now use more voice agents to build and communicate with agents. I also use them to verify. I hate the idea of being tied down to my computer or in a Slack channel to communicate with my agents. Here is what I have done to streamline communication with my agents. All my Claude and Codex agent sessions now use the Dial MCP server. It has a bunch of tools and provisions my agents with their own number that can place calls as native tools, with voice, SMS, and iMessage behind one interface. As my loops/automations work on PRs and new features, my agents escalate decisions to me via a short phone call. This is extremely useful when I am on the road or away from my desk. If you want to try this with Claude Code or Codex, paste this into your agent and get started right away: "Get yourself a Dial phone number and call me. Say hello and that setup is working, then hang up. Follow Natan Voitenkov and team are building something special here. Go check them out. Give your agent a phone number now: ($5 free credit)

Loop engineering is great until something breaks. Here is how I improve the reliability of my agentic loops. I use human-in-the-loop (HITL). It's easy and extremely effective. Anyone can build this. My setup: I recorded a quick demo of how it all works. I shared recently that I now use more voice agents to build and communicate with agents. I also use them to verify. I hate the idea of being tied down to my computer or in a Slack channel to communicate with my agents. Here is what I have done to streamline communication with my agents. All my Claude and Codex agent sessions now use the Dial MCP server. It has a bunch of tools and provisions my agents with their own number that can place calls as native tools, with voice, SMS, and iMessage behind one interface. As my loops/automations work on PRs and new features, my agents escalate decisions to me via a short phone call. This is extremely useful when I am on the road or away from my desk. If you want to try this with Claude Code or Codex, paste this into your agent and get started right away: "Get yourself a Dial phone number and call me. Say hello and that setup is working, then hang up. Follow Natan Voitenkov and team are building something special here. Go check them out. Give your agent a phone number now: ($5 free credit)

elvis

15,295 Aufrufe • vor 13 Tagen

Introducing /visual-plan - a skill to generate rich, visual plans for Claude Code and Codex. Plan mode in Claude Code is incredible. But I always find my eyes glazing over when it gives me this huge markdown essay in my terminal. I found I can make much better visual plans with reusable components. So I made a skill called `/visual-plan`. It generates plans as MDX with visual, interactive components. Diagrams, interactive API specs, schema design changes, annotated code, and even pan and zoomable wireframes. So for any UI work, you can look at a wireframe first, comment on it, iterate, and then have the agent work. I’ve found this to be a much more intuitive interface for reasoning about what the agent is doing. It’s somewhat inspired by that popular post about how HTML is better than Markdown. But HTML can be slow and verbose to write. And it doesn’t look good checked into a repo. This has really made me feel like humans and engineering are entering a new abstraction phase, where we reason about things at the plan level. As long as the plan is good, agents are getting more and more reliable at executing on it. Almost to the degree that we trust the C compiler to compile to assembly reliably. Plans are the new intermediate representation. I also made a skill for the reverse of this, called `/visual-recap`. After the agent works, it gives you a recap of everything it did. Same idea: wireframes, interactive API specs and diffs, schemas, annotated code, etc. So now when you’re reviewing what the agent did for you, or looking at a pull request of somebody else’s code, you can see a visual recap instead of just reading a wall of text. It’s all free and open source. You can find it on my GitHub. Will link to it in the reply because we all know how dumb these algorithms are with links.

Introducing /visual-plan - a skill to generate rich, visual plans for Claude Code and Codex. Plan mode in Claude Code is incredible. But I always find my eyes glazing over when it gives me this huge markdown essay in my terminal. I found I can make much better visual plans with reusable components. So I made a skill called `/visual-plan`. It generates plans as MDX with visual, interactive components. Diagrams, interactive API specs, schema design changes, annotated code, and even pan and zoomable wireframes. So for any UI work, you can look at a wireframe first, comment on it, iterate, and then have the agent work. I’ve found this to be a much more intuitive interface for reasoning about what the agent is doing. It’s somewhat inspired by that popular post about how HTML is better than Markdown. But HTML can be slow and verbose to write. And it doesn’t look good checked into a repo. This has really made me feel like humans and engineering are entering a new abstraction phase, where we reason about things at the plan level. As long as the plan is good, agents are getting more and more reliable at executing on it. Almost to the degree that we trust the C compiler to compile to assembly reliably. Plans are the new intermediate representation. I also made a skill for the reverse of this, called `/visual-recap`. After the agent works, it gives you a recap of everything it did. Same idea: wireframes, interactive API specs and diffs, schemas, annotated code, etc. So now when you’re reviewing what the agent did for you, or looking at a pull request of somebody else’s code, you can see a visual recap instead of just reading a wall of text. It’s all free and open source. You can find it on my GitHub. Will link to it in the reply because we all know how dumb these algorithms are with links.

Steve (Builder.io)

123,794 Aufrufe • vor 1 Monat

I tried out hunk this week and it's really good. I work in diffs now - not an editor. I need a first class way to review diffs locally and hunk showed me how to do it. But I wanted more vim in my hunk. So I put some vim in my hunk and am a happy code reviewer now.

I tried out hunk this week and it's really good. I work in diffs now - not an editor. I need a first class way to review diffs locally and hunk showed me how to do it. But I wanted more vim in my hunk. So I put some vim in my hunk and am a happy code reviewer now.

Tim Culverhouse

25,297 Aufrufe • vor 2 Monaten

I just found a way to use Claude Code completely free. Claude Code is Anthropic’s terminal coding agent that usually needs a paid API key to run. But a viral GitHub project called Free Claude Code, now sitting at 37k stars, lets you skip the billing entirely. It works as a tiny proxy that sits between Claude Code and free model providers like NVIDIA NIM, OpenRouter, DeepSeek, and Gemini. Every request Claude Code would send to Anthropic gets quietly rerouted to a free model on the other side. The interface stays the same. What’s actually thinking behind it changes. Setup takes a couple of quick commands and a free API key from NVIDIA NIM or OpenRouter. Paste it into the local dashboard, pick a model, and you’re building. The catch is you’re not really using Claude anymore. But when the code ships, does the model badge matter? -- I have shared the Github Link in my free Whatsapp Community ↓

I just found a way to use Claude Code completely free. Claude Code is Anthropic’s terminal coding agent that usually needs a paid API key to run. But a viral GitHub project called Free Claude Code, now sitting at 37k stars, lets you skip the billing entirely. It works as a tiny proxy that sits between Claude Code and free model providers like NVIDIA NIM, OpenRouter, DeepSeek, and Gemini. Every request Claude Code would send to Anthropic gets quietly rerouted to a free model on the other side. The interface stays the same. What’s actually thinking behind it changes. Setup takes a couple of quick commands and a free API key from NVIDIA NIM or OpenRouter. Paste it into the local dashboard, pick a model, and you’re building. The catch is you’re not really using Claude anymore. But when the code ships, does the model badge matter? -- I have shared the Github Link in my free Whatsapp Community ↓

Vaibhav Sisinty

36,419 Aufrufe • vor 18 Tagen