Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Built a 2.5MB image classifier that runs in the browser in an evening with Claude Code. In 2022, I hand-labelled ~1,900 pages from historical books for a project that never really shipped. The dataset sat on Hugging Face for 3 years. This week I pointed Claude Code at it:...

vanstriendaniel's profile picture

Daniel van Strien

5,201 subscribers

47,657 Aufrufe • vor 7 Monaten •via X (Twitter)

BildungWissenschaft & Technologie
LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

I genuinely don't understand why everyone isn't using this yet. Andrej Karpathy, OpenAI co-founder, posted a simple idea that went massively viral: Stop using AI to write code. Use it to build a second brain. You point Claude Code at a folder. Drop in any source: an article, a transcript, a PDF. Claude reads it, links it, files it into a living wiki of everything you know. It compounds like interest. The more you feed it, the smarter it gets. Here's the whole thing: 1) Install Obsidian 2) Create a vault 3) Open it in Claude Code 4) Paste Karpathy's wiki idea and tell Claude to build it 5) Claude makes three folders: - raw (for sources) - wiki (for its pages) - CLAUDE. md (that runs it) 6) Drop any source into raw and say: "ingest this" 7) Ask questions across everything, forever Five minutes to set up and you never start from a blank chat again. Full step by step guide below.
1:48

I genuinely don't understand why everyone isn't using this yet. Andrej Karpathy, OpenAI co-founder, posted a simple idea that went massively viral: Stop using AI to write code. Use it to build a second brain. You point Claude Code at a folder. Drop in any source: an article, a transcript, a PDF. Claude reads it, links it, files it into a living wiki of everything you know. It compounds like interest. The more you feed it, the smarter it gets. Here's the whole thing: 1) Install Obsidian 2) Create a vault 3) Open it in Claude Code 4) Paste Karpathy's wiki idea and tell Claude to build it 5) Claude makes three folders: - raw (for sources) - wiki (for its pages) - CLAUDE. md (that runs it) 6) Drop any source into raw and say: "ingest this" 7) Ask questions across everything, forever Five minutes to set up and you never start from a blank chat again. Full step by step guide below.

CyrilXBT

322,126 Aufrufe • vor 1 Monat

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.
0:55

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

215,365 Aufrufe • vor 2 Monaten

you don’t need a robot to see physical ai in action, you just need a browser. this week I finally tried something I've wanted to do for a while: design an SO-101 scene in three.js, connect it to a real leader arm, collect teleoperation data, train an ACT model, then port it to run in the browser. the result is the first ever demo of ACT that runs locally on the web. try it yourself now at
0:35

you don’t need a robot to see physical ai in action, you just need a browser. this week I finally tried something I've wanted to do for a while: design an SO-101 scene in three.js, connect it to a real leader arm, collect teleoperation data, train an ACT model, then port it to run in the browser. the result is the first ever demo of ACT that runs locally on the web. try it yourself now at

Binh Pham

120,916 Aufrufe • vor 1 Monat

WHAT?!? 🤯 I asked Claude to build me an all in one AI Operating System for working with Claude Code. An hour later here we are... → Full ability to chat with Claude Code → Markdown file browser/editor built right in I've been using VS Code but there is a lot that I just don't need. I'm a knowledge worker, not a developer. So I guess I just built an IDE for knowledge workers? Now we're building: → Voice Mode (ability to switch to voice conversations) → Cron Job Management - so I can manage all the automated processes we have running → Ability to switch to different agents (currently I just have one... my AI Cos, Chad)
0:22

WHAT?!? 🤯 I asked Claude to build me an all in one AI Operating System for working with Claude Code. An hour later here we are... → Full ability to chat with Claude Code → Markdown file browser/editor built right in I've been using VS Code but there is a lot that I just don't need. I'm a knowledge worker, not a developer. So I guess I just built an IDE for knowledge workers? Now we're building: → Voice Mode (ability to switch to voice conversations) → Cron Job Management - so I can manage all the automated processes we have running → Ability to switch to different agents (currently I just have one... my AI Cos, Chad)

⚡️ Ev Chapman 🚢 | Creative Entrepreneur

38,577 Aufrufe • vor 4 Monaten

I tested Genspark new AI Developer: an L4 agent that builds a working app from an idea. You can choose any model (including Claude), and it runs in your browser and in the app—including planning, code, testing, and fixes. The output looks like it was done by a senior developer. I used Prompt to build a functional newsflash page that creates and curates a newsletter for me by adding a few links! It's revolutionary. Prompt in the comments. Genspark
0:34

I tested Genspark new AI Developer: an L4 agent that builds a working app from an idea. You can choose any model (including Claude), and it runs in your browser and in the app—including planning, code, testing, and fixes. The output looks like it was done by a senior developer. I used Prompt to build a functional newsflash page that creates and curates a newsletter for me by adding a few links! It's revolutionary. Prompt in the comments. Genspark

Chubby♨️

235,727 Aufrufe • vor 11 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 ↓
0:36

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,744 Aufrufe • vor 1 Monat

Introducing 🌸 Kanna – a web ui for Claude Code + Codex running right in your browser (and my first open source project!) It's sort of like if Claude Code & Codex had a baby with a much better ui/ux 💅 Here's what makes Kanna special: 🔀 One-click switch between Claude Code / Codex 🌐 Runs in your browser on localhost - no app switching 🧩 Embedded split terminals, persisted between chats with a beautiful horizontal scrolling UX 📁 Full project file browser built in, embedded editor coming soon too. Coming soon: 🔒 End-to-end encryption + remote access via reverse proxy 🌿 Git integration, diffs, PRs 🧱 Plugins I wanted to replace switching between cursor, the github app, browser & (most recently) the codex app. The browser is hardest to recreate yet also the most flexible so it makes sense to build in the browser itself. Install in 5 seconds: bun install -g kanna-code then just type: kanna Kanna is purely a ui/ux layer. It uses your existing CLIs, is 100% compliant & no data ever leaves your machine. If running claude or codex in your terminal works, kanna works too. Kanna natively supports every tool call, model, reasoning effort, fast mode, plan mode, compaction, user questions, web searching, skills, agents, mcps, everything. There are a few libraries that do this but none that I found as comprehensive. All feedback welcome!
1:38

Introducing 🌸 Kanna – a web ui for Claude Code + Codex running right in your browser (and my first open source project!) It's sort of like if Claude Code & Codex had a baby with a much better ui/ux 💅 Here's what makes Kanna special: 🔀 One-click switch between Claude Code / Codex 🌐 Runs in your browser on localhost - no app switching 🧩 Embedded split terminals, persisted between chats with a beautiful horizontal scrolling UX 📁 Full project file browser built in, embedded editor coming soon too. Coming soon: 🔒 End-to-end encryption + remote access via reverse proxy 🌿 Git integration, diffs, PRs 🧱 Plugins I wanted to replace switching between cursor, the github app, browser & (most recently) the codex app. The browser is hardest to recreate yet also the most flexible so it makes sense to build in the browser itself. Install in 5 seconds: bun install -g kanna-code then just type: kanna Kanna is purely a ui/ux layer. It uses your existing CLIs, is 100% compliant & no data ever leaves your machine. If running claude or codex in your terminal works, kanna works too. Kanna natively supports every tool call, model, reasoning effort, fast mode, plan mode, compaction, user questions, web searching, skills, agents, mcps, everything. There are a few libraries that do this but none that I found as comprehensive. All feedback welcome!

Superdaddy

43,285 Aufrufe • vor 4 Monaten

Struggling with Claude Code? Here's what Boris Cherny, the creator of Claude Code, recommends almost every time: 1) Use Opus 4.5 with thinking - It's smarter, uses fewer tokens, often ends up cheaper than smaller models. 2) Invest in your ClaudeMD - Just a text file. No special format. - Add every mistake Claude makes so it doesn't repeat them. 3) Give Claude a way to verify its output - Run tests. - Start a server. - Let it see the browser. A painter wearing a blindfolded won't paint well. Neither will an LLM that can't check its own work. Once the plan is good, the code is good.
9:55

Struggling with Claude Code? Here's what Boris Cherny, the creator of Claude Code, recommends almost every time: 1) Use Opus 4.5 with thinking - It's smarter, uses fewer tokens, often ends up cheaper than smaller models. 2) Invest in your ClaudeMD - Just a text file. No special format. - Add every mistake Claude makes so it doesn't repeat them. 3) Give Claude a way to verify its output - Run tests. - Start a server. - Let it see the browser. A painter wearing a blindfolded won't paint well. Neither will an LLM that can't check its own work. Once the plan is good, the code is good.

The Startup Ideas Podcast (SIP) 🧃

160,458 Aufrufe • vor 6 Monaten

I built a book. Not a PDF viewer. A real, skeuomorphic hardcover book that lives in the browser. The idea started with a simple question: What if reading a digital book actually felt like reading a real one? Since I've worked on book app designs before, I was curious to see how Claude would respond to one of those ideas that starts out sounding a little unrealistic. At first, I only wanted to recreate the experience of opening a book and flipping through its pages. Then one idea became another. I added: • Real page-flipping interactions with sound • Text highlighting in multiple colors • A voice reader • Reading reminders that continue from where you left off • Bookmarks to save important pages to share with friends later Then I thought about one of the biggest frustrations with large books. Flipping through hundreds of pages just to find page 287 isn't fun. So I added a page entry feature. Type a page number, and the book automatically flips through the pages until it gets there, just like a real book in motion. There are still more ideas I want to explore, but this was one of those projects where I kept building as the ideas came to mind. Curiosity led me here, and I like where it is taking me! Built with Claude. Designed by me. Livelink: Do let me know what you think!
1:00

I built a book. Not a PDF viewer. A real, skeuomorphic hardcover book that lives in the browser. The idea started with a simple question: What if reading a digital book actually felt like reading a real one? Since I've worked on book app designs before, I was curious to see how Claude would respond to one of those ideas that starts out sounding a little unrealistic. At first, I only wanted to recreate the experience of opening a book and flipping through its pages. Then one idea became another. I added: • Real page-flipping interactions with sound • Text highlighting in multiple colors • A voice reader • Reading reminders that continue from where you left off • Bookmarks to save important pages to share with friends later Then I thought about one of the biggest frustrations with large books. Flipping through hundreds of pages just to find page 287 isn't fun. So I added a page entry feature. Type a page number, and the book automatically flips through the pages until it gets there, just like a real book in motion. There are still more ideas I want to explore, but this was one of those projects where I kept building as the ideas came to mind. Curiosity led me here, and I like where it is taking me! Built with Claude. Designed by me. Livelink: Do let me know what you think!

Biba

28,798 Aufrufe • vor 1 Monat

My friend applied to 200 tech jobs in two years. No MIT. No Stanford. Last month Anthropic offered him $750,000. I asked him how he broke in from zero. He sent me the exact video that got him in. A 4-hour course on mastering Claude Code. I watched it last night. Halfway through, I realized I've been using Claude Code completely wrong for a year. Bookmark this and read the article below. • 00:00 - Claude Code setup • 49:34 - building apps with Claude Code • 2:07:52 - prompting Claude Code • 2:46:16 - Claude Code for production
4:27:47

My friend applied to 200 tech jobs in two years. No MIT. No Stanford. Last month Anthropic offered him $750,000. I asked him how he broke in from zero. He sent me the exact video that got him in. A 4-hour course on mastering Claude Code. I watched it last night. Halfway through, I realized I've been using Claude Code completely wrong for a year. Bookmark this and read the article below. • 00:00 - Claude Code setup • 49:34 - building apps with Claude Code • 2:07:52 - prompting Claude Code • 2:46:16 - Claude Code for production

Roan

37,805 Aufrufe • vor 23 Tagen

Ever since I wired Claude Code to WhatsApp 3 weeks ago, I built a stupidly large infra around it. I mean, opus built it. No clue how the code even looks. The entire thing was vibe coded using my phone. I wanted to see how far I could push it without touching the computer. Everything via WhatsApp. Build what I need on the fly. So the resulting infrastructure will already be battle tested for software development. The entire thing was streamlined with nearly no manual interventions, everything was communicated via WhatsApp using a single script establishing this connection. If the script is down, I need to get home to start it again to resume the development. Claude was upgrading it, debugging it, restarting it while maintaining constant uptime so it could keep communicating with me. I stressed Claude about it, telling it that it will be “in the dark” and other words that deliberately sound scary about losing communications if the script dies. I also refused git and refused cloning the code, I wanted to see Claude adapting to work on a *LIVING* system. The way this whole thing works: Claude has its own dedicated phone number that I am paying for. A real WhatsApp account for it is installed on a real iPhone that is sitting on my desk. All is registered under my name, this is legit setup with no hacks and tricks. I’ve set up a WhatsApp “Community” and multiple different groups under it. Both me and Claude are the admins, so Claude could edit it on my behalf. Each group is a project I am working on and has its own isolated context. The Group description is a system prompt that gets auto-appended to the larger system prompt explaining this setup in general. When I send a message it’s an instant interrupt to Claude Code’s process, just like in the terminal. Voice notes are seamlessly transcribed with a local Whisper model. Images are used with multimodal reading in an isolated parallel session. Multiple groups running in parallel so I can work on all projects at the same time. No cross-talking, everything has an isolated context and history. And because it’s local on my own machine: Everything is REAL. The browser is REAL. I am connected as myself on it to all services because I actually use it in real life. Claude has unlimited internet access, just like humans who use actual browsers. It utilizes custom-made browser tools that I made to control any browser session it wants. Depending on the situation, it can either connect to my existing session or create one for its own. (You can tell it ‘look at my browser for a sec’ then talk about the current page you are on and it just works, pretty cool) My custom browser tools are not perfect (not by a long shot) but I managed to make them work well to the point they are somewhat reliable. This gives Claude full access to my real creds and all the services I actually use. I’m productive AS HELL with this. It really feels like a personal assistant. I ask it to read my emails and msgs, check x .com for news, research arxiv papers, write code, run experiments for me, investigate and reverse engineer github repos, even use my credit card and order things. [I try not to do this one a lot lol so far no disasters]. All from my phone. Super convenient. This is not a product or an open source project (maybe soon of it will make sense). This is just an ugly script I hacked the entire thing is ~600 lines. (ok maybe i did look at the code, but i swear i didn’t edit!) You can also vibe code this from scratch pretty fast and it will probably even end up better. This is just a cool thing so I’m sharing. It is a real speed booster for many things I do on daily basis, mostly boring things. Forcing my routine into some new “agent platform” just didn’t feel right for me. WhatsApp is where I already communicate and look for messages, so I decided that my agents will live there too. AGI in my pocket 24/7.
0:52

Ever since I wired Claude Code to WhatsApp 3 weeks ago, I built a stupidly large infra around it. I mean, opus built it. No clue how the code even looks. The entire thing was vibe coded using my phone. I wanted to see how far I could push it without touching the computer. Everything via WhatsApp. Build what I need on the fly. So the resulting infrastructure will already be battle tested for software development. The entire thing was streamlined with nearly no manual interventions, everything was communicated via WhatsApp using a single script establishing this connection. If the script is down, I need to get home to start it again to resume the development. Claude was upgrading it, debugging it, restarting it while maintaining constant uptime so it could keep communicating with me. I stressed Claude about it, telling it that it will be “in the dark” and other words that deliberately sound scary about losing communications if the script dies. I also refused git and refused cloning the code, I wanted to see Claude adapting to work on a *LIVING* system. The way this whole thing works: Claude has its own dedicated phone number that I am paying for. A real WhatsApp account for it is installed on a real iPhone that is sitting on my desk. All is registered under my name, this is legit setup with no hacks and tricks. I’ve set up a WhatsApp “Community” and multiple different groups under it. Both me and Claude are the admins, so Claude could edit it on my behalf. Each group is a project I am working on and has its own isolated context. The Group description is a system prompt that gets auto-appended to the larger system prompt explaining this setup in general. When I send a message it’s an instant interrupt to Claude Code’s process, just like in the terminal. Voice notes are seamlessly transcribed with a local Whisper model. Images are used with multimodal reading in an isolated parallel session. Multiple groups running in parallel so I can work on all projects at the same time. No cross-talking, everything has an isolated context and history. And because it’s local on my own machine: Everything is REAL. The browser is REAL. I am connected as myself on it to all services because I actually use it in real life. Claude has unlimited internet access, just like humans who use actual browsers. It utilizes custom-made browser tools that I made to control any browser session it wants. Depending on the situation, it can either connect to my existing session or create one for its own. (You can tell it ‘look at my browser for a sec’ then talk about the current page you are on and it just works, pretty cool) My custom browser tools are not perfect (not by a long shot) but I managed to make them work well to the point they are somewhat reliable. This gives Claude full access to my real creds and all the services I actually use. I’m productive AS HELL with this. It really feels like a personal assistant. I ask it to read my emails and msgs, check x .com for news, research arxiv papers, write code, run experiments for me, investigate and reverse engineer github repos, even use my credit card and order things. [I try not to do this one a lot lol so far no disasters]. All from my phone. Super convenient. This is not a product or an open source project (maybe soon of it will make sense). This is just an ugly script I hacked the entire thing is ~600 lines. (ok maybe i did look at the code, but i swear i didn’t edit!) You can also vibe code this from scratch pretty fast and it will probably even end up better. This is just a cool thing so I’m sharing. It is a real speed booster for many things I do on daily basis, mostly boring things. Forcing my routine into some new “agent platform” just didn’t feel right for me. WhatsApp is where I already communicate and look for messages, so I decided that my agents will live there too. AGI in my pocket 24/7.

Yam Peleg

419,733 Aufrufe • vor 7 Monaten

Claude Code + computer use is f*cking cracked 🤯 Build a landing page → Claude opens Chrome, looks at it, spots every issue, and fixes it — without you describing a single thing. All inside Claude Code. Perfect for DTC brands and agencies who are still vibe-coding landing pages and advertorials in Claude Code, then manually opening them in Chrome, spotting 15 things wrong, and describing every visual issue back to Claude one at a time. If you're building pages in Claude Code and your workflow looks like this — build the page, open it in Chrome, spot broken spacing, go back to Claude, type "the CTA button is too low and the hero image is cut off," wait for the fix, open Chrome again, find 3 new issues, describe those too ... Claude Code + computer use eliminates the entire loop: → Claude writes the full landing page or advertorial → Opens Chrome and navigates to it → Spots layout issues, broken spacing, off-brand colors, missing elements → Fixes everything and re-checks until the page looks right → Tests your Shopify product pages by clicking through like a real customer → Walks through your checkout flow and flags friction before customers hit it → You only see the finished, visually verified result No describing what you see on screen. No "the CTA button needs more contrast" back-and-forth. No being the eyeballs for an AI that can't see. What you get: → Landing pages and advertorials Claude builds AND visually QAs before you ever look at them → Product pages Claude clicks through — testing layout, images, and CTAs like a real user → HTML dashboards Claude opens and verifies the charts actually render → Checkout flows Claude walks through step by step to catch friction → All of it happening in one session — build, test, fix, done One prompt. Claude builds it, checks it, and fixes it. You just review the finished page. I put together a full playbook with the exact setup, the prompts, and 5 DTC workflows that use Claude Code + computer use. Want it for free? > Like this post > Comment "CLAUDE" And I'll send it over (must be following so I can DM)
0:20

Claude Code + computer use is f*cking cracked 🤯 Build a landing page → Claude opens Chrome, looks at it, spots every issue, and fixes it — without you describing a single thing. All inside Claude Code. Perfect for DTC brands and agencies who are still vibe-coding landing pages and advertorials in Claude Code, then manually opening them in Chrome, spotting 15 things wrong, and describing every visual issue back to Claude one at a time. If you're building pages in Claude Code and your workflow looks like this — build the page, open it in Chrome, spot broken spacing, go back to Claude, type "the CTA button is too low and the hero image is cut off," wait for the fix, open Chrome again, find 3 new issues, describe those too ... Claude Code + computer use eliminates the entire loop: → Claude writes the full landing page or advertorial → Opens Chrome and navigates to it → Spots layout issues, broken spacing, off-brand colors, missing elements → Fixes everything and re-checks until the page looks right → Tests your Shopify product pages by clicking through like a real customer → Walks through your checkout flow and flags friction before customers hit it → You only see the finished, visually verified result No describing what you see on screen. No "the CTA button needs more contrast" back-and-forth. No being the eyeballs for an AI that can't see. What you get: → Landing pages and advertorials Claude builds AND visually QAs before you ever look at them → Product pages Claude clicks through — testing layout, images, and CTAs like a real user → HTML dashboards Claude opens and verifies the charts actually render → Checkout flows Claude walks through step by step to catch friction → All of it happening in one session — build, test, fix, done One prompt. Claude builds it, checks it, and fixes it. You just review the finished page. I put together a full playbook with the exact setup, the prompts, and 5 DTC workflows that use Claude Code + computer use. Want it for free? > Like this post > Comment "CLAUDE" And I'll send it over (must be following so I can DM)

Mike Futia

19,125 Aufrufe • vor 4 Monaten

Anthropic just released a talk on building headless automation with Claude Code. Presented by Sid Bidasaria, Member of Technical Staff at Anthropic live at Code with Claude on May 22, 2025 in San Francisco. Here is what the talk covers. Headless mode lets you run Claude Code without a person actively typing prompts from inside an automated script. Instead of a live session, a script calls Claude with a pre-written instruction using the -p flag. This opens the door for Claude Code to become a piece of a much larger, automated process. In plain terms: Claude Code stops being a tool you use and starts being a service that runs on its own. What this unlocks: Scheduled tasks: Run Claude Code on a cron schedule without anyone at a keyboard. Fix linting errors across an entire codebase. Automatically. Overnight. CI/CD integration: Trigger Claude Code as a step in your build process. Open a PR. Claude reviews it, flags issues, and pushes fixes before a human ever looks at it. GitHub automation: A project manager comments "Claude fix this" on a GitHub issue. Claude reads the request, finds the code, writes the fix, and opens the PR. Multi-machine workflows: One orchestrator dispatches tasks to multiple Claude Code instances running in parallel across different repos simultaneously. When you combine headless mode, hooks, and GitHub Actions, development teams can automate tasks that usually eat up significant time freeing senior engineers to focus on architectural problems while Claude handles the repetitive ones. If you use Claude Code for anything beyond single sessions this talk is worth 20 minutes of your time.
20:58

Anthropic just released a talk on building headless automation with Claude Code. Presented by Sid Bidasaria, Member of Technical Staff at Anthropic live at Code with Claude on May 22, 2025 in San Francisco. Here is what the talk covers. Headless mode lets you run Claude Code without a person actively typing prompts from inside an automated script. Instead of a live session, a script calls Claude with a pre-written instruction using the -p flag. This opens the door for Claude Code to become a piece of a much larger, automated process. In plain terms: Claude Code stops being a tool you use and starts being a service that runs on its own. What this unlocks: Scheduled tasks: Run Claude Code on a cron schedule without anyone at a keyboard. Fix linting errors across an entire codebase. Automatically. Overnight. CI/CD integration: Trigger Claude Code as a step in your build process. Open a PR. Claude reviews it, flags issues, and pushes fixes before a human ever looks at it. GitHub automation: A project manager comments "Claude fix this" on a GitHub issue. Claude reads the request, finds the code, writes the fix, and opens the PR. Multi-machine workflows: One orchestrator dispatches tasks to multiple Claude Code instances running in parallel across different repos simultaneously. When you combine headless mode, hooks, and GitHub Actions, development teams can automate tasks that usually eat up significant time freeing senior engineers to focus on architectural problems while Claude handles the repetitive ones. If you use Claude Code for anything beyond single sessions this talk is worth 20 minutes of your time.

Elias

14,096 Aufrufe • vor 2 Monaten

Boris Cherny, the creator of Claude Code, shared his entire setup. He runs 5-10 Claudes in parallel. Half his coding happens from his phone. Here's his 3-part formula for better results: Use the smartest model available — Counterintuitive: it's actually cheaper — Smarter model = fewer tokens = lower total cost — "Once the plan is good, the code is good" Invest in your Claude MD — Plain text file. No special format. — Whole team contributes multiple times a week — Every mistake Claude makes gets added so it never happens again Give Claude a way to verify its own output — Let it run the code. Let it see the browser. — "Imagine you're a painter wearing a blindfold" — Same thing for an AI that can never check its work His morning routine: wake up, kick off 3 sessions from his phone, check in later. His workflow: start in plan mode → lock the plan → auto-accept edits → done. No fancy setup. No complex tooling. Just multiple Claudes, a good plan, and a shared knowledge base.
11:50

Boris Cherny, the creator of Claude Code, shared his entire setup. He runs 5-10 Claudes in parallel. Half his coding happens from his phone. Here's his 3-part formula for better results: Use the smartest model available — Counterintuitive: it's actually cheaper — Smarter model = fewer tokens = lower total cost — "Once the plan is good, the code is good" Invest in your Claude MD — Plain text file. No special format. — Whole team contributes multiple times a week — Every mistake Claude makes gets added so it never happens again Give Claude a way to verify its own output — Let it run the code. Let it see the browser. — "Imagine you're a painter wearing a blindfold" — Same thing for an AI that can never check its work His morning routine: wake up, kick off 3 sessions from his phone, check in later. His workflow: start in plan mode → lock the plan → auto-accept edits → done. No fancy setup. No complex tooling. Just multiple Claudes, a good plan, and a shared knowledge base.

The Startup Ideas Podcast (SIP) 🧃

558,283 Aufrufe • vor 4 Monaten

Pi was built when there were already agent harnesses around. Here’s why Mario Zechner(Mario Zechner), found them suboptimal and built Pi, a minimalist self-modifying agent: #1 - Mario initially was a believer in Claude Code: "I was a believer in Claude code because they were the first that packaged agentic search up in a really compelling package. And at the time that fit my workflow really well. Everything around the LLM was kind of nice and tidy and easy to understand. I was super happy. I was proselytising Claude code." #2 - Reverse engineering Claude Code highlighted the degradation that Mario felt as a user: "I personally like simple tools that are stable and that I can rely on. Even if they have non-deterministic parts, all the deterministic parts should be as stable as possible. That was just not the experience with Claude Code around summer 2025. They would take away your control of the context. They would inject stuff behind your back, which is bad. Then, your workflows stopped working because there's now a system reminder that you don't even see in the UI that would modify the behaviour of the model. They would also do this to the system prompt. I built a little service where I can track the progression or evolution of the system, prompt and tool definitions and, with every release, it was messing with stuff. That just messed with my workflows and I don't appreciate that." #3 - PI was built with an appreciation for simple and reliable tools: "If I commit to a development tool, I want it to be a stable, reliable thing like a hammer. I don't want my hammer to break a different spot every day. That's terrible. We need somebody who goes the full velocity kind of way. But I don't want to work with a tool like that."
2:54

Pi was built when there were already agent harnesses around. Here’s why Mario Zechner(Mario Zechner), found them suboptimal and built Pi, a minimalist self-modifying agent: #1 - Mario initially was a believer in Claude Code: "I was a believer in Claude code because they were the first that packaged agentic search up in a really compelling package. And at the time that fit my workflow really well. Everything around the LLM was kind of nice and tidy and easy to understand. I was super happy. I was proselytising Claude code." #2 - Reverse engineering Claude Code highlighted the degradation that Mario felt as a user: "I personally like simple tools that are stable and that I can rely on. Even if they have non-deterministic parts, all the deterministic parts should be as stable as possible. That was just not the experience with Claude Code around summer 2025. They would take away your control of the context. They would inject stuff behind your back, which is bad. Then, your workflows stopped working because there's now a system reminder that you don't even see in the UI that would modify the behaviour of the model. They would also do this to the system prompt. I built a little service where I can track the progression or evolution of the system, prompt and tool definitions and, with every release, it was messing with stuff. That just messed with my workflows and I don't appreciate that." #3 - PI was built with an appreciation for simple and reliable tools: "If I commit to a development tool, I want it to be a stable, reliable thing like a hammer. I don't want my hammer to break a different spot every day. That's terrible. We need somebody who goes the full velocity kind of way. But I don't want to work with a tool like that."

The Pragmatic Engineer

62,825 Aufrufe • vor 3 Monaten

I tried jack's Buzz. It's like Slack + OpenClaw + Herdr + but with some really unique features that people are sleeping on. The video below shows how it works, and some of my thoughts on the process and platform, e.g.: - Create and interact with agents on top of any harness (claude code, codex, pi, etc.) - Choose which models agents use, including local ones - Agents can delegate work and work in parallel in git worktrees - Agents are first-class citizens and work like humans (creating channels, delegating, access to chat history) - You can share AI compute within a community - It's completely open-source and decentralized Things I like: - Delegating work in chat feels natural: tag an agent, it replies in a thread with status updates as it e.g. compiles, commits, and deploys. - Shared compute: relay owners can share local compute with members, so a community could pool funds for one beefy machine running a local model and everyone uses it. - It's built on Nostr, an open protocol already tied into Bitcoin Lightning so I can imagine communities tipping each other or paying for compute/agent tasks with instant zero-fee micropayments in the future. - It ties together things like OpenClaw, an agent manager, and Slack-style chat into one tool. Things I didn't like: - You can't see what the agent is doing in a terminal. The activity view exists, but if you're used to watching a session run, this UI feels a bit abstracted. A terminal view would be great. - It feels slower than running a session in Claude Code, though no evidence to back that up. For that reason I found myself doing one-off tasks in the terminal instead. Verdict: - I really like it so far and can genuinely imagine working with a team this way. - It doesn't feel ready for big, complex tasks yet. For shallower tasks, it's perfect. - The shared compute + Nostr/Lightning angle is what really separates it from every other agent manager for me, and I think that future is coming.
5:57

I tried jack's Buzz. It's like Slack + OpenClaw + Herdr + but with some really unique features that people are sleeping on. The video below shows how it works, and some of my thoughts on the process and platform, e.g.: - Create and interact with agents on top of any harness (claude code, codex, pi, etc.) - Choose which models agents use, including local ones - Agents can delegate work and work in parallel in git worktrees - Agents are first-class citizens and work like humans (creating channels, delegating, access to chat history) - You can share AI compute within a community - It's completely open-source and decentralized Things I like: - Delegating work in chat feels natural: tag an agent, it replies in a thread with status updates as it e.g. compiles, commits, and deploys. - Shared compute: relay owners can share local compute with members, so a community could pool funds for one beefy machine running a local model and everyone uses it. - It's built on Nostr, an open protocol already tied into Bitcoin Lightning so I can imagine communities tipping each other or paying for compute/agent tasks with instant zero-fee micropayments in the future. - It ties together things like OpenClaw, an agent manager, and Slack-style chat into one tool. Things I didn't like: - You can't see what the agent is doing in a terminal. The activity view exists, but if you're used to watching a session run, this UI feels a bit abstracted. A terminal view would be great. - It feels slower than running a session in Claude Code, though no evidence to back that up. For that reason I found myself doing one-off tasks in the terminal instead. Verdict: - I really like it so far and can genuinely imagine working with a team this way. - It doesn't feel ready for big, complex tasks yet. For shallower tasks, it's perfect. - The shared compute + Nostr/Lightning angle is what really separates it from every other agent manager for me, and I think that future is coming.

Vinny

1,337,719 Aufrufe • vor 13 Tagen

ANTHROPIC JUST QUIETLY SHIPPED A FEATURE THAT LETS CLAUDE SPAWN A WHOLE TEAM OF AGENTS THAT MESSAGE EACH OTHER AND REVIEW EACH OTHER'S WORK. It's a Claude Code feature called agent teams. The team lead spawns multiple agents that share a task list and message each other directly, not subagents reporting back, actual peers. In the demo a QA agent caught three bugs, sent the work back to the front-end and back-end devs, they fixed it, app shipped in one pass. How to run it: 1. Enable it. Needs Claude Code v2.1.32+. Add to settings.json: "env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" }. Or paste that to Claude and say "add this to my settings." Restart. 2. Prompt in plain English. Start with a goal (agents wake with zero context), then "create a team of 3 using Sonnet," describe each role, its deliverable, and who it messages when done. 3. The rules: each agent owns its own files, define exact outputs, name who talks to who, keep it to 3-5 agents. Use it for complex work with separate parts running in parallel. Skip it for simple or sequential tasks, teams cost 3-4x the tokens. Bookmark this.
16:29

ANTHROPIC JUST QUIETLY SHIPPED A FEATURE THAT LETS CLAUDE SPAWN A WHOLE TEAM OF AGENTS THAT MESSAGE EACH OTHER AND REVIEW EACH OTHER'S WORK. It's a Claude Code feature called agent teams. The team lead spawns multiple agents that share a task list and message each other directly, not subagents reporting back, actual peers. In the demo a QA agent caught three bugs, sent the work back to the front-end and back-end devs, they fixed it, app shipped in one pass. How to run it: 1. Enable it. Needs Claude Code v2.1.32+. Add to settings.json: "env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" }. Or paste that to Claude and say "add this to my settings." Restart. 2. Prompt in plain English. Start with a goal (agents wake with zero context), then "create a team of 3 using Sonnet," describe each role, its deliverable, and who it messages when done. 3. The rules: each agent owns its own files, define exact outputs, name who talks to who, keep it to 3-5 agents. Use it for complex work with separate parts running in parallel. Skip it for simple or sequential tasks, teams cost 3-4x the tokens. Bookmark this.

Yarchi

460,553 Aufrufe • vor 1 Monat

I've been showing the output of my flight reconstruction tool for a while and I wanted to share something like it which wasn't a mess of hand tuned stuff that required X-Plane. So I created a completely new version in javascript that runs in an HTML page so that anyone can use it. The output is a KML file which is a tour that works in Google Earth pro with all the attitude information included. This is a long way from perfect, I messed around with multiple smoothing algorithms and none of them compares well with the python code, but they're readable and understandable for anyone.
1:37

I've been showing the output of my flight reconstruction tool for a while and I wanted to share something like it which wasn't a mess of hand tuned stuff that required X-Plane. So I created a completely new version in javascript that runs in an HTML page so that anyone can use it. The output is a KML file which is a tour that works in Google Earth pro with all the attitude information included. This is a long way from perfect, I messed around with multiple smoothing algorithms and none of them compares well with the python code, but they're readable and understandable for anyone.

Scott Manley

19,808 Aufrufe • vor 6 Monaten

🖨️🖼️ Big progress: it can now print images too I had to install a different printer driver, Claude Code recommended Epson FX-86e which supported images Then I printed an image, it helped me dump a .bin from the printer raw data output, then it decoded the .bin and figured out how to draw images on a canvas (in the printer) from that data So crazy I'd have no clue how to do this without AI ever!
1:00

🖨️🖼️ Big progress: it can now print images too I had to install a different printer driver, Claude Code recommended Epson FX-86e which supported images Then I printed an image, it helped me dump a .bin from the printer raw data output, then it decoded the .bin and figured out how to draw images on a canvas (in the printer) from that data So crazy I'd have no clue how to do this without AI ever!

@levelsio

100,862 Aufrufe • vor 2 Monaten

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.
0:31

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,148 Aufrufe • vor 13 Tagen