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

Introducing: auto-maintainer 🔥 Your repo hits the front page. 147 issues, 38 PRs pile up overnight. You triage, review, fix, merge -- and wake up to more. auto-maintainer handles it. Write your rules in a Markdown file, and it triages issues, reviews code, ships fixes, merges PRs, and cuts... show more

yazin

8,100 subscribers

18,402 görüntüleme • 6 ay önce •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

23 Yorum

yazin profil fotoğrafı

yazin6 ay önce

How it works: - One command setup: "npx auto-maintainer" init analyzes your codebase and generates rules for you - Rules are plain Markdown in .github/repo-policy[.]md — edit anytime, no YAML - Uses your existing Claude Pro/Max/Team plan; no separate API costs - Secure by default — triage bot can't touch code, actions pinned to commit SHAs Free, MIT licensed.

FileCity profil fotoğrafı

FileCity6 ay önce

Great work! @yazins Made you a full narrated FileCity tour + visual map of auto-maintainer

yazin profil fotoğrafı

yazin6 ay önce

Thank you! This is really cool

Saeed Anwar profil fotoğrafı

Saeed Anwar6 ay önce

writing your triage rules in a markdown file and letting an agent handle 147 issues overnight is exactly how open source maintenance should scale. the bottleneck was never code quality, it was human bandwidth to review it all.

Todd Rawlings profil fotoğrafı

Todd Rawlings6 ay önce

This is brilliant. Let’s talk about this and OpenOats.

cCross profil fotoğrafı

cCross6 ay önce

Solid approach, curious how you handle the 5% high risk cases?

yazin profil fotoğrafı

yazin6 ay önce

You fly through them. It's like solving a multip answer quiz

Morgan profil fotoğrafı

Morgan6 ay önce

Such an awesome idea Yazin 🔥

yazin profil fotoğrafı

yazin6 ay önce

thanks morgan!

B.ع ♟️ 🇵🇸🇸🇩 profil fotoğrafı

B.ع ♟️ 🇵🇸🇸🇩6 ay önce

اللهم بارك

yazin profil fotoğrafı

yazin6 ay önce

🙏 أجمعين

Kamran profil fotoğrafı

Kamran6 ay önce

Wow quite nice stuff, I'll say add some sandboxing and security if there's not any since people can do prompt injection.

yazin profil fotoğrafı

yazin6 ay önce

It runs inside an isolated environment in a GitHub actions. Runner

Khalid Shamiyah, MD profil fotoğrafı

Khalid Shamiyah, MD6 ay önce

Love the video! How did you make it?

yazin profil fotoğrafı

yazin6 ay önce

thanks, used remotion!

Khalid Shamiyah, MD profil fotoğrafı

Khalid Shamiyah, MD6 ay önce

Thanks that’s very helpful!

michael froehlich profil fotoğrafı

michael froehlich6 ay önce

@nimarblu

Misbah Syed profil fotoğrafı

Misbah Syed6 ay önce

Amazing!

HaMah profil fotoğrafı

HaMah6 ay önce

Dang slopsource bout to go vrooommmm

regardo911 profil fotoğrafı

regardo9116 ay önce

writing your maintenance rules in a markdown file and letting the agent triage is the right abstraction. the problem with most repo automation is it tries to be smart. this just follows YOUR rules. 147 issues overnight is the exact scenario where human triage breaks down and agents shine

Mahmoud Darwish profil fotoğrafı

Mahmoud Darwish6 ay önce

Would like to collaborate, please dm

0x_Vivek profil fotoğrafı

0x_Vivek6 ay önce

yazin's daemon swallows 95% of the triage queue. for the 5% touching critical state, you retain the merge keys. run npx auto-maintainer init. zero platform toll.

Chat Data profil fotoğrafı

Chat Data6 ay önce

The 95 percent number is the provocative part here. The interesting question is how you decide what falls into the 5 percent bucket. If the escalation rules and review trace are clear, this starts looking a lot more trustworthy for busy repos.

Benzer Videolar

New on Claude Code Desktop We’re shipping new features for Claude Code on desktop that let you preview running apps, auto-review code, and auto-fix and merge PRs to help close the development loop. - Server previews: Claude starts dev servers and previews your running app in the desktop interface. It reads console logs, catches errors, and keeps iterating on its own. - Local code review: Claude examines your local diffs and leaves inline comments before you push — an immediate second set of eyes on every change. - PR monitoring: Claude tracks CI status after you open a PR. With auto-fix, it attempts to resolve failures automatically. With auto-merge, PRs land as soon as checks pass. You can move on to your next task while Claude handles the last one. - Session mobility: Move sessions from CLI to desktop, and from desktop to the cloud. Start work at your desk, pick it up from the web or your phone.

New on Claude Code Desktop We’re shipping new features for Claude Code on desktop that let you preview running apps, auto-review code, and auto-fix and merge PRs to help close the development loop. - Server previews: Claude starts dev servers and previews your running app in the desktop interface. It reads console logs, catches errors, and keeps iterating on its own. - Local code review: Claude examines your local diffs and leaves inline comments before you push — an immediate second set of eyes on every change. - PR monitoring: Claude tracks CI status after you open a PR. With auto-fix, it attempts to resolve failures automatically. With auto-merge, PRs land as soon as checks pass. You can move on to your next task while Claude handles the last one. - Session mobility: Move sessions from CLI to desktop, and from desktop to the cloud. Start work at your desk, pick it up from the web or your phone.

Ado

71,910 görüntüleme • 7 ay önce

AI can write your code. But who’s making sure it’s actually good? CodeRabbit now gives you free, high-quality AI code reviews, right inside your IDE. Supports and integrates with top AI agents like GitHub Copilot, Claude, Codex, Cursor AI, and more. What makes it different: • No subscription needed • Context-aware reviews • “Fix with AI” feature sends feedback directly to your AI coding agent • One-click commit suggestions • 10M+ PRs reviewed, 50K+ installs on GitHub Marketplace CodeRabbit doesn’t just point out issues. It helps you fix them fast.

AI can write your code. But who’s making sure it’s actually good? CodeRabbit now gives you free, high-quality AI code reviews, right inside your IDE. Supports and integrates with top AI agents like GitHub Copilot, Claude, Codex, Cursor AI, and more. What makes it different: • No subscription needed • Context-aware reviews • “Fix with AI” feature sends feedback directly to your AI coding agent • One-click commit suggestions • 10M+ PRs reviewed, 50K+ installs on GitHub Marketplace CodeRabbit doesn’t just point out issues. It helps you fix them fast.

Rohit Ghumare

32,176 görüntüleme • 1 yıl önce

Boris Cherny: "My job is to write loops." 5-day version you can copy for Claude Code Day 1: repo memory - write CLAUDE.md - include stack, test commands, code style, release rules, gotchas - add .claude/settings.json with the shell commands Claude can run Day 2: verification skill - pick 1 flow Claude keeps breaking - put the browser/API test in .claude/skills/ /scripts/ - make it return: pass/fail, failing step, screenshot/log path Day 3: commands Add these files: .claude/commands/babysit.md - checks your PRs - reads CI - handles obvious review nits - surfaces design questions .claude/commands/triage-issues.md - labels new issues - dedupes against existing ones - assigns owners .claude/commands/deploy-watch.md - checks the live app - reports regressions - avoids touching production Day 4: loops > /loop 5m /babysit > /loop 15m /triage-issues > /loop 5m /deploy-watch Day 5: overnight work - schedule /morning-report - schedule /deep-audit - write results to .claude/inbox/ - let your morning loop read from that folder The rule: every code-writing loop gets a separate verifier. Builder makes the change. Verifier runs the real app. You read the diff. Skip that and you wake up to 14 broken PRs with very confident summaries. Video: "Reflecting on a year of Claude Code" with Boris Cherny & Cat Wu

Boris Cherny: "My job is to write loops." 5-day version you can copy for Claude Code Day 1: repo memory - write CLAUDE.md - include stack, test commands, code style, release rules, gotchas - add .claude/settings.json with the shell commands Claude can run Day 2: verification skill - pick 1 flow Claude keeps breaking - put the browser/API test in .claude/skills/ /scripts/ - make it return: pass/fail, failing step, screenshot/log path Day 3: commands Add these files: .claude/commands/babysit.md - checks your PRs - reads CI - handles obvious review nits - surfaces design questions .claude/commands/triage-issues.md - labels new issues - dedupes against existing ones - assigns owners .claude/commands/deploy-watch.md - checks the live app - reports regressions - avoids touching production Day 4: loops > /loop 5m /babysit > /loop 15m /triage-issues > /loop 5m /deploy-watch Day 5: overnight work - schedule /morning-report - schedule /deep-audit - write results to .claude/inbox/ - let your morning loop read from that folder The rule: every code-writing loop gets a separate verifier. Builder makes the change. Verifier runs the real app. You read the diff. Skip that and you wake up to 14 broken PRs with very confident summaries. Video: "Reflecting on a year of Claude Code" with Boris Cherny & Cat Wu

Alpha Batcher

141,110 görüntüleme • 3 ay önce

Ledn co-founder Mauricio on how auto top-up saves you from liquidation "Auto top-up is a tool that lets clients park or keep extra Bitcoin with Ledn in custody. That Bitcoin sits in cold storage, it doesn't move, it doesn't do anything. It's just there to help you service your loan when you need it." "From within the Ledn platform, transfers are automatic. If you have an open loan you can turn auto top-up on." "What that does is it pre-authorizes Ledn to draw from your custody account to top up your loan if and when your loan ever needs it, automatically."

Ledn co-founder Mauricio on how auto top-up saves you from liquidation "Auto top-up is a tool that lets clients park or keep extra Bitcoin with Ledn in custody. That Bitcoin sits in cold storage, it doesn't move, it doesn't do anything. It's just there to help you service your loan when you need it." "From within the Ledn platform, transfers are automatic. If you have an open loan you can turn auto top-up on." "What that does is it pre-authorizes Ledn to draw from your custody account to top up your loan if and when your loan ever needs it, automatically."

The Wolf Of All Streets

27,950 görüntüleme • 1 ay önce

Claude Fable 5 is back! GPT- 5.6 is coming soon! But how much do you trust your Al Agent or chatbot? Are you sure its performance aligns with your intentions? As of today iFixAi is available in Claude Code, Open AI Codex, Cursor and many more! And it is open-source! iFixAi is where Al red teaming meets Operational Assurance. It runs in auto, and in under 5 mins you can have a good idea if you can trust your Agent/chatbot. Key Features: 🕵️‍♂️ Setup Discovery Reads your agent's real configuration, its tools, rules, and permissions. 👷 Fixture Builder Turns that setup into a complete test. No YAML, no flags, no config to write. 🌐 Any Model, Any Provider Runs the 45 inspections on the model you actually ship. ⚖️ A Independent Grading Your agent is judged by a different vendor's model, never itself. No Al grading its own homework. 📊 Interactive Scorecard An A to F grade in minutes, with exactly what failed and why. Repo in the comments below 👇👇👇

Claude Fable 5 is back! GPT- 5.6 is coming soon! But how much do you trust your Al Agent or chatbot? Are you sure its performance aligns with your intentions? As of today iFixAi is available in Claude Code, Open AI Codex, Cursor and many more! And it is open-source! iFixAi is where Al red teaming meets Operational Assurance. It runs in auto, and in under 5 mins you can have a good idea if you can trust your Agent/chatbot. Key Features: 🕵️‍♂️ Setup Discovery Reads your agent's real configuration, its tools, rules, and permissions. 👷 Fixture Builder Turns that setup into a complete test. No YAML, no flags, no config to write. 🌐 Any Model, Any Provider Runs the 45 inspections on the model you actually ship. ⚖️ A Independent Grading Your agent is judged by a different vendor's model, never itself. No Al grading its own homework. 📊 Interactive Scorecard An A to F grade in minutes, with exactly what failed and why. Repo in the comments below 👇👇👇

Dimitris Neocleous

5,801,215 görüntüleme • 2 ay önce

grok-bot just got open-sourced and it run locally completely FREE. 3.8k stars in 2 weeks. MIT licensed. it gives every AI agent its own computer. own browser, own files, own container. every action is approved against a policy before it runs, and written to an audit log after. here's how to set it up: 1️⃣prerequisites Docker + Bun 1.3+ 2️⃣clone and create your env git clone cd OpenBot cp .env.example .env 3️⃣get intelligence credentials (free plan works) npx --yes copilotkit@latest login npx --yes copilotkit@latest project select npx --yes copilotkit@latest license --write drop the cpk-... key into .env as INTELLIGENCE_API_KEY 4️⃣ add your model key "OPENAI_API_KEY=sk-..." 5️⃣ run it bun install bash scripts/start.sh open localhost:3010. that's it. the underrated part: the repo ships a prompt.txt you paste into claude code or cursor and it walks the whole setup for you. every claim in it is verified against the actual repo. what it actually costs: the code is MIT, free forever. you pay your own model tokens. intelligence has a free tier and can be fully self-hosted if you want zero external dependency. works with any AG-UI agent. langgraph, mastra, crewai, pydantic ai. repo in in the CS.

grok-bot just got open-sourced and it run locally completely FREE. 3.8k stars in 2 weeks. MIT licensed. it gives every AI agent its own computer. own browser, own files, own container. every action is approved against a policy before it runs, and written to an audit log after. here's how to set it up: 1️⃣prerequisites Docker + Bun 1.3+ 2️⃣clone and create your env git clone cd OpenBot cp .env.example .env 3️⃣get intelligence credentials (free plan works) npx --yes copilotkit@latest login npx --yes copilotkit@latest project select npx --yes copilotkit@latest license --write drop the cpk-... key into .env as INTELLIGENCE_API_KEY 4️⃣ add your model key "OPENAI_API_KEY=sk-..." 5️⃣ run it bun install bash scripts/start.sh open localhost:3010. that's it. the underrated part: the repo ships a prompt.txt you paste into claude code or cursor and it walks the whole setup for you. every claim in it is verified against the actual repo. what it actually costs: the code is MIT, free forever. you pay your own model tokens. intelligence has a free tier and can be fully self-hosted if you want zero external dependency. works with any AG-UI agent. langgraph, mastra, crewai, pydantic ai. repo in in the CS.

m0h

59,144 görüntüleme • 28 gün önce

Problem: After working for a few months in open source, I noticed that understanding issues is often very tough, and random OS files make it a nightmare for newbies. Solution: So here we go I created It explains any open-source repo file line by line with flowcharts, explains open-source issues, and provides a dedicated step-by-step solution plan. It also helps you write PR content in multiple languages. Built for the Apify × Lingo.dev Multilingual Actors Hackathon You can start using it by adding a Gemini or Groq API key. For more detailed explanations and better data fetching, you can add an Apify API key. For in-app translations, it uses Lingo. Even if you don’t believe in the app, you can check the repo code or fork it and deploy it yourself (SQL query provided) and use it unlimited times. Enjoy. Your Problem solved.

Problem: After working for a few months in open source, I noticed that understanding issues is often very tough, and random OS files make it a nightmare for newbies. Solution: So here we go I created It explains any open-source repo file line by line with flowcharts, explains open-source issues, and provides a dedicated step-by-step solution plan. It also helps you write PR content in multiple languages. Built for the Apify × Lingo.dev Multilingual Actors Hackathon You can start using it by adding a Gemini or Groq API key. For more detailed explanations and better data fetching, you can add an Apify API key. For in-app translations, it uses Lingo. Even if you don’t believe in the app, you can check the repo code or fork it and deploy it yourself (SQL query provided) and use it unlimited times. Enjoy. Your Problem solved.

Sk Akram

30,264 görüntüleme • 9 ay önce

ANTHROPIC LEAKED 6 RULES THAT RUN 8 LOOPS AT ONCE - AND ONE ENGINEER DOES THE WORK OF A TEAM one engineer with this system replaces an entire team - and costs the company 8 times less You → Opus 5 plan → Fable 5 ×8 execute → Fable 5 review → you: 5 min Opus 5 takes your intent and breaks it into subtasks - a bad plan multiplied across every loop gives the same number of disasters - the plan is the only thing you read carefully one repo - isolated worktrees for each loop - nobody stands on anyone's file - parallel PRs ship while you do nothing the agent runs the tests and fixes until green PR - a red build never reaches your eyes one CLAUDE.md for the whole fleet - without it you get different opinions from every loop and one merge hell the average engineer closes 3-4 tasks a day - this system closes a full sprint overnight with zero working hours Fable 5 pre-reviews every PR before it reaches you - you spend 5 minutes - your throughput is now measured in diffs read per hour bookmark and paste into Claude Code - your first fleet can start tonight

ANTHROPIC LEAKED 6 RULES THAT RUN 8 LOOPS AT ONCE - AND ONE ENGINEER DOES THE WORK OF A TEAM one engineer with this system replaces an entire team - and costs the company 8 times less You → Opus 5 plan → Fable 5 ×8 execute → Fable 5 review → you: 5 min Opus 5 takes your intent and breaks it into subtasks - a bad plan multiplied across every loop gives the same number of disasters - the plan is the only thing you read carefully one repo - isolated worktrees for each loop - nobody stands on anyone's file - parallel PRs ship while you do nothing the agent runs the tests and fixes until green PR - a red build never reaches your eyes one CLAUDE.md for the whole fleet - without it you get different opinions from every loop and one merge hell the average engineer closes 3-4 tasks a day - this system closes a full sprint overnight with zero working hours Fable 5 pre-reviews every PR before it reaches you - you spend 5 minutes - your throughput is now measured in diffs read per hour bookmark and paste into Claude Code - your first fleet can start tonight

Sprytix

37,904 görüntüleme • 2 ay önce

Alibaba just dropped a free AI that codes like a $150/hr developer. And it runs on your laptop. Qwen 3 Coder Next has 80 billion parameters but only uses 3 billion at a time. So you get massive model power with tiny model speed. The real kicker? It handles 256,000 tokens of context. That's your entire codebase. Every file. All at once. People are building 2D games in seconds. Full IDE integrations that write, test, and fix code automatically. Custom business tools without hiring devs. It works with OpenClaw, Claude Code, and every major coding tool. No complicated setup. Just download and go. Completely open source. Zero API queues. You own it. Your competitors are using this right now.

Alibaba just dropped a free AI that codes like a $150/hr developer. And it runs on your laptop. Qwen 3 Coder Next has 80 billion parameters but only uses 3 billion at a time. So you get massive model power with tiny model speed. The real kicker? It handles 256,000 tokens of context. That's your entire codebase. Every file. All at once. People are building 2D games in seconds. Full IDE integrations that write, test, and fix code automatically. Custom business tools without hiring devs. It works with OpenClaw, Claude Code, and every major coding tool. No complicated setup. Just download and go. Completely open source. Zero API queues. You own it. Your competitors are using this right now.

Julian Goldie SEO

30,284 görüntüleme • 7 ay önce

$THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this$

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this

Yarchi

56,502 görüntüleme • 3 ay önce

Weave is launching the number 1 prompt router in the world. It enables you to get 70% more efficient use of your tokens. We analyzed millions of prompts and found that the vast majority don't need a frontier model. Weave Router fixes that. It analyzes your prompt and routes it to the highest quality model with the lowest cost (across open and closed source models). This all happens in your current workflow on Claude, Cursor or Codex so you don't have to change a thing. Early customers have seen an ~70% reduction in costs without any slowdowns. Source code available.

Weave is launching the number 1 prompt router in the world. It enables you to get 70% more efficient use of your tokens. We analyzed millions of prompts and found that the vast majority don't need a frontier model. Weave Router fixes that. It analyzes your prompt and routes it to the highest quality model with the lowest cost (across open and closed source models). This all happens in your current workflow on Claude, Cursor or Codex so you don't have to change a thing. Early customers have seen an ~70% reduction in costs without any slowdowns. Source code available.

Adam Cohen

28,237 görüntüleme • 4 ay önce

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,143 görüntüleme • 6 ay önce

Announcing OpenWorker! An open-source agent that doesn't just chat with you, but delivers finished work -- like hand you a polished document, send a slack message, or update a calendar entry. Ask it to prepare a customer brief, untangle your calendar, draft a report, or triage a Slack alert. It works across your files and everyday tools, produces the deliverable, and checks in before doing anything consequential. OpenWorker runs on your Mac, with Windows support coming soon. It does not lock you into any one model. Bring your own API key and run it with GPT 5.6 Sol, Claude Fable, Gemini 3.6, an open weight model (like Kimi, GLM, DeepSeek, Inkling), or Ollama to keep your data local. Your data does not leave your machine except through an LLM provider and integrations that you choose. rohit and I are building OpenWorker because AI coworkers are an important way to get work done, and we want there to be an open, privacy-preserving, model-independent option. Check it out and let us know what you think! Try it out: (requires your own API key) Source code:

Announcing OpenWorker! An open-source agent that doesn't just chat with you, but delivers finished work -- like hand you a polished document, send a slack message, or update a calendar entry. Ask it to prepare a customer brief, untangle your calendar, draft a report, or triage a Slack alert. It works across your files and everyday tools, produces the deliverable, and checks in before doing anything consequential. OpenWorker runs on your Mac, with Windows support coming soon. It does not lock you into any one model. Bring your own API key and run it with GPT 5.6 Sol, Claude Fable, Gemini 3.6, an open weight model (like Kimi, GLM, DeepSeek, Inkling), or Ollama to keep your data local. Your data does not leave your machine except through an LLM provider and integrations that you choose. rohit and I are building OpenWorker because AI coworkers are an important way to get work done, and we want there to be an open, privacy-preserving, model-independent option. Check it out and let us know what you think! Try it out: (requires your own API key) Source code:

Andrew Ng

1,165,949 görüntüleme • 2 ay önce

Claude Code: Auto mode Auto mode lets Claude safely complete long-running tasks without asking permission for every action. But how does it work? 4 key terms: • Classifier: a separate model that approves or denies each action based on your intent and scope • Filtering: the classifier only sees your messages and Claude's tool calls, not Claude’s reasoning or tool outputs, so it isn't influenced when making decisions • Tier check: read-only and easily-undone actions (like edits inside your repo) skip the classifier; everything else goes through it • Probe: a server-side check that scans incoming content, like web pages, for prompt injection and flags it to Claude I'm working on a longer video that explains how auto mode works and how to configure it. What questions do you have about it?

Claude Code: Auto mode Auto mode lets Claude safely complete long-running tasks without asking permission for every action. But how does it work? 4 key terms: • Classifier: a separate model that approves or denies each action based on your intent and scope • Filtering: the classifier only sees your messages and Claude's tool calls, not Claude’s reasoning or tool outputs, so it isn't influenced when making decisions • Tier check: read-only and easily-undone actions (like edits inside your repo) skip the classifier; everything else goes through it • Probe: a server-side check that scans incoming content, like web pages, for prompt injection and flags it to Claude I'm working on a longer video that explains how auto mode works and how to configure it. What questions do you have about it?

Delba

43,073 görüntüleme • 3 ay önce

8 rules to improve your AI coding agent. All of these rules work with Claude Code, Cursor, VS Code, and with most programming languages. Automating these rules will 10x the code quality and security produced by your AI coding agents. 1. Dependency checks - Prevent your agent from suggesting insecure libraries based on outdated training data. 2. Secret exposure - Auto-fix the use of hardcoded credentials introduced by your coding agent. 3. File and function size - Automatically refactor any files or functions that exceed a reasonable length. 4. Complexity and parameter limits - Simplify overly complex code written by the agent. 5. SQL Injection - Auto-fix all database interactions with unsanitized user input. 6. Unused variables and imports - Detect and remove dead code. 7. Detect invisible unicode characters in AI rules files - Remove zero-width spaces, direction overrides, and other invisible characters that can hide malicious behavior. 8. Insecure OpenAI API usage - Enforce use of secure OpenAI endpoints, proper authentication, and context isolation Here is how you can automate this: Install the Codacy extension. This will give you access to a CLI for local scanning and an MCP server for agent communication. From here on out, every time you need to generate some code: 1. Your agent will write the code 2. It will then call Codacy's CLI to check it 3. It will find any issues in real time 4. Your coding agent will fix the issues 5. When the code passes all checks, you are done Level of effort on your side: literally zero! Code quality and security because of this: 100x better! Here is the link to download the extension for your IDE: Thanks to the Codacy team for collaborating with me on this post.

8 rules to improve your AI coding agent. All of these rules work with Claude Code, Cursor, VS Code, and with most programming languages. Automating these rules will 10x the code quality and security produced by your AI coding agents. 1. Dependency checks - Prevent your agent from suggesting insecure libraries based on outdated training data. 2. Secret exposure - Auto-fix the use of hardcoded credentials introduced by your coding agent. 3. File and function size - Automatically refactor any files or functions that exceed a reasonable length. 4. Complexity and parameter limits - Simplify overly complex code written by the agent. 5. SQL Injection - Auto-fix all database interactions with unsanitized user input. 6. Unused variables and imports - Detect and remove dead code. 7. Detect invisible unicode characters in AI rules files - Remove zero-width spaces, direction overrides, and other invisible characters that can hide malicious behavior. 8. Insecure OpenAI API usage - Enforce use of secure OpenAI endpoints, proper authentication, and context isolation Here is how you can automate this: Install the Codacy extension. This will give you access to a CLI for local scanning and an MCP server for agent communication. From here on out, every time you need to generate some code: 1. Your agent will write the code 2. It will then call Codacy's CLI to check it 3. It will find any issues in real time 4. Your coding agent will fix the issues 5. When the code passes all checks, you are done Level of effort on your side: literally zero! Code quality and security because of this: 100x better! Here is the link to download the extension for your IDE: Thanks to the Codacy team for collaborating with me on this post.

Santiago

49,331 görüntüleme • 11 ay önce

I'm excited to introduce Polymath Society. Your resume and LinkedIn do not know who you really are. But your AI tools do. Polymath helps you analyze your Claude Code/Codex/Cursor, ChatGPT, Claude, and Notion logs. It does all this locally without anything touching our servers, using your own Claude Code or Codex subscription. If Polymath thinks you're good, you can share a condensed, privacy-safe report with us and we will get you opportunities directly in your inbox. Early members in the community are quants and researchers with multiple physics olympiad medals. Join us : npm install -g polymath-society

I'm excited to introduce Polymath Society. Your resume and LinkedIn do not know who you really are. But your AI tools do. Polymath helps you analyze your Claude Code/Codex/Cursor, ChatGPT, Claude, and Notion logs. It does all this locally without anything touching our servers, using your own Claude Code or Codex subscription. If Polymath thinks you're good, you can share a condensed, privacy-safe report with us and we will get you opportunities directly in your inbox. Early members in the community are quants and researchers with multiple physics olympiad medals. Join us : npm install -g polymath-society

Akshay Iyer

28,548 görüntüleme • 2 ay önce

Today, I'm excited to launch Entelligence AI DeepReviews, the next generation AI-powered code reviews. Vibe coded PRs are not production ready often creating more subtle bugs throughout the codebase than before. Entelligence fixes this by understanding the entire codebase and flags bugs, regressions, and breakages across files before you ship. But it goes beyond review comments: ✅ Auto-generated docs with architecture diagrams ✅ Team Insights to improve process, not just code ✅ Real time code reviews within your editor If you're building or leading a dev team, this is what smarter, context-aware reviews look like. Try it out in the link below 👇

Today, I'm excited to launch Entelligence AI DeepReviews, the next generation AI-powered code reviews. Vibe coded PRs are not production ready often creating more subtle bugs throughout the codebase than before. Entelligence fixes this by understanding the entire codebase and flags bugs, regressions, and breakages across files before you ship. But it goes beyond review comments: ✅ Auto-generated docs with architecture diagrams ✅ Team Insights to improve process, not just code ✅ Real time code reviews within your editor If you're building or leading a dev team, this is what smarter, context-aware reviews look like. Try it out in the link below 👇

Aiswarya Sankar

96,309 görüntüleme • 1 yıl önce

THE BLUE DOT IS NOW That glowing dot? That’s your present moment. The only one you actually own. When you speak inside it, your vagus nerve lights up - the hidden wire running your heartbeat, your breath, your digestion. The systems you don’t control suddenly listening. That’s why meditation works. Why breathwork works. Why words matter more than vibes. Every sound you make rewrites the code running your body - and maybe more. Call it prayer, call it hacking, call it creation. You’re not “like” a god. You are one. Source: seca_llc on IG

THE BLUE DOT IS NOW That glowing dot? That’s your present moment. The only one you actually own. When you speak inside it, your vagus nerve lights up - the hidden wire running your heartbeat, your breath, your digestion. The systems you don’t control suddenly listening. That’s why meditation works. Why breathwork works. Why words matter more than vibes. Every sound you make rewrites the code running your body - and maybe more. Call it prayer, call it hacking, call it creation. You’re not “like” a god. You are one. Source: seca_llc on IG

Mario Nawfal

547,101 görüntüleme • 1 yıl önce

Introducing... MERGE MOMMY my eve PR review + auto approve bot Like all of you, I was drowning in pull requests, so I built a little agent to risk score PRs and auto approve low risk ones, inspired by previous How I AI guest Brian Scanlan and the work of the Intercom team In this mini ep, I teach you 02:35 why you shouldn't approve every PR by hand 06:10 how the eve agent framework works 11:36 designing your PR review agent 13:07 setting up + deploying eve w codex browser use 17:23 Merge Mommy in action I recommend this to every eng team out there -- if you haven't built one yet, today is your day. As always, huge thanks to our amazing sponsor WorkOS - Make your app Enterprise Ready today

Introducing... MERGE MOMMY my eve PR review + auto approve bot Like all of you, I was drowning in pull requests, so I built a little agent to risk score PRs and auto approve low risk ones, inspired by previous How I AI guest Brian Scanlan and the work of the Intercom team In this mini ep, I teach you 02:35 why you shouldn't approve every PR by hand 06:10 how the eve agent framework works 11:36 designing your PR review agent 13:07 setting up + deploying eve w codex browser use 17:23 Merge Mommy in action I recommend this to every eng team out there -- if you haven't built one yet, today is your day. As always, huge thanks to our amazing sponsor WorkOS - Make your app Enterprise Ready today

claire vo 🖤

25,632 görüntüleme • 1 ay önce

ANTHROPIC LEAKED A TRADING DESK FILE THAT TAKES YOU FROM $10 TO $10,000 AND COSTS $1.50 A DAY Anthropic spent 5 years building this file on closed tech, it costs $1.50 a day and it can return $1.2M a year rules → reading → code → critic → journal → back to rules $10 to $10,000 is 1000×, which is ten doublings in a row at a coin flip that is 1 chance in 1,024, and a single loss anywhere sends you to zero instead of back one step by week four the balance reads $5,400 and only 0.8% are still alive on that rung the 1,024 who tried are not visible in the feed, only the one who arrived is you write the rules yourself: size, max loss, and what you never touch Haiku 4.5 reads the market and summarises it, and never once passes judgement Opus 5 works as the critic and attacks your own backtest instead of praising it the journal logs every trade and why, and it is what rewrites the rules for tomorrow the desk does not raise your odds on any single flip, it lowers how many flips you have to take save this and paste it into Claude Code - let it build your DESK.md ↓

ANTHROPIC LEAKED A TRADING DESK FILE THAT TAKES YOU FROM $10 TO $10,000 AND COSTS $1.50 A DAY Anthropic spent 5 years building this file on closed tech, it costs $1.50 a day and it can return $1.2M a year rules → reading → code → critic → journal → back to rules $10 to $10,000 is 1000×, which is ten doublings in a row at a coin flip that is 1 chance in 1,024, and a single loss anywhere sends you to zero instead of back one step by week four the balance reads $5,400 and only 0.8% are still alive on that rung the 1,024 who tried are not visible in the feed, only the one who arrived is you write the rules yourself: size, max loss, and what you never touch Haiku 4.5 reads the market and summarises it, and never once passes judgement Opus 5 works as the critic and attacks your own backtest instead of praising it the journal logs every trade and why, and it is what rewrites the rules for tomorrow the desk does not raise your odds on any single flip, it lowers how many flips you have to take save this and paste it into Claude Code - let it build your DESK.md ↓

Sprytix

22,861 görüntüleme • 27 gün önce