Загрузка видео...

Не удалось загрузить видео

Возникла проблема при загрузке этого видео. Это может быть связано с временными проблемами сети или видео может быть недоступно.

На главную

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?show more

Delba

132,946 subscribers

43,073 просмотров • 5 месяцев назад •via X (Twitter)

Наука и технологии

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

Claude Code used to interrupt you constantly. Approve this. Approve that. Approve everything. Auto Mode just fixed it. Now Claude keeps working while a safety classifier blocks dangerous actions automatically ⚡

Claude Code used to interrupt you constantly. Approve this. Approve that. Approve everything. Auto Mode just fixed it. Now Claude keeps working while a safety classifier blocks dangerous actions automatically ⚡

Julian Goldie SEO

16,606 просмотров • 7 месяцев назад

We recently made auto mode the default in Claude Code, which means you no longer have to approve every action. But what determines if something is safe to run? Watch how it works:

We recently made auto mode the default in Claude Code, which means you no longer have to approve every action. But what determines if something is safe to run? Watch how it works:

ClaudeDevs

400,614 просмотров • 3 месяцев назад

You can now schedule recurring cloud-based tasks on Claude Code. Set a repo (or repos), a schedule, and a prompt. Claude runs it via cloud infra on your schedule, so you don’t need to keep Claude Code running on your local machine.

You can now schedule recurring cloud-based tasks on Claude Code. Set a repo (or repos), a schedule, and a prompt. Claude runs it via cloud infra on your schedule, so you don’t need to keep Claude Code running on your local machine.

Noah Zweben

2,039,450 просмотров • 7 месяцев назад

How to make Claude Code 10x better: Connect it with a tool that reviews your code and generates prompts for Claude to fix any issues with it automatically. Here is what this looks like:

How to make Claude Code 10x better: Connect it with a tool that reviews your code and generates prompts for Claude to fix any issues with it automatically. Here is what this looks like:

Santiago

98,993 просмотров • 1 год назад

$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,568 просмотров • 5 месяцев назад

What is a software factory? It is your workflow, your skills, and your domain knowledge, saved in files that the agent reads so the whole process is productized Think about the last app you built. You typed what you wanted, and the agent built it. You did not like it, so you made changes. You shipped it to Vercel, or you kept going. A factory puts structure on each of those steps. At each step you ask how to get the most from the model, and how to move faster. That is the conveyor belt. You ship quickly, and the quality stays the same. Mine is 5 md files. It works in Codex, Claude Code, and Cursor, because it does not depend on the model or the tool. Build your own.

What is a software factory? It is your workflow, your skills, and your domain knowledge, saved in files that the agent reads so the whole process is productized Think about the last app you built. You typed what you wanted, and the agent built it. You did not like it, so you made changes. You shipped it to Vercel, or you kept going. A factory puts structure on each of those steps. At each step you ask how to get the most from the model, and how to move faster. That is the conveyor belt. You ship quickly, and the quality stays the same. Mine is 5 md files. It works in Codex, Claude Code, and Cursor, because it does not depend on the model or the tool. Build your own.

The Startup Ideas Podcast (SIP) 🧃

17,326 просмотров • 1 месяц назад

A guy on Reddit got so fed up with scrolling LinkedIn for internships that he built his own job search engine with Claude Code. The tool is called Pinloop. It's an open-source CLI, and he built it with Claude Code too. Here's how it works: → It pulls millions of postings a month, worldwide, straight from hiring systems like Greenhouse and Workday (50+ of them) plus job boards like LinkedIn, refreshed hourly → It stores your resume and preferences → Every day, Claude Code pulls the new postings, reads each one against your profile, and writes a verdict with its reasoning → The good fits land in a shortlist you check in the morning His reasoning: every application already gets screened by AI on the employer's side, so he built a screener for his own side. You don't even have to set it up yourself. Paste this into Claude Code, Codex, or Cursor: "Run npm install -g pinloop, then run pinloop welcome and follow the instructions"

Vaibhav Sisinty

19,615 просмотров • 1 месяц назад

$Today, we are launching OpenRouter Armor in beta. Tool calls allow agents to interact with the world, and regex-based filtering often isn't enough to detect unwanted tool calls. Armor uses TypeSafe AI's Jev model to guard against out of policy tool calls before your agent executes them, with better performance than Claude Code's auto classifier at a fraction of the cost.$

Today, we are launching OpenRouter Armor in beta. Tool calls allow agents to interact with the world, and regex-based filtering often isn't enough to detect unwanted tool calls. Armor uses TypeSafe AI's Jev model to guard against out of policy tool calls before your agent executes them, with better performance than Claude Code's auto classifier at a fraction of the cost.

OpenRouter

158,155 просмотров • 24 дней назад

install these before your next long Claude Code session if your Opus 5.5 bill hurts and you don’t know where to start, copy this: claude-code-router: sits in front of Claude Code and sends each request to the cheapest model that can do it. Haiku does the grep, Opus only gets the hard part. 37k stars rtk: shrinks test, build and git output before the model sees it. one binary, up to 90% less bash output in your context. 83k stars claude-mem: remembers what happened in your past sessions and feeds back only the relevant part, so you stop paying to re-explain your project every morning. 100k stars context-mode: a huge tool output goes into a local database instead of your context window, and Claude pulls out only the lines it needs. 18k stars caveman: makes Claude answer in short telegraphic sentences. code stays identical, and output is the expensive side on Opus 5.5 ($20 per million). 51k stars token-optimizer: a local dashboard that shows where your tokens actually went, and keeps your work alive across compactions. 1.9k stars token-savior: replaces whole-file reads with symbol lookups, so Claude reads the function and not the 2,000 lines around it code-review-graph: maps your repo as a graph and gives Claude only the code connected to the change you’re reviewing jev-ultrafast: a browser agent where Jev picks every click, and a text model wakes up only when something has to be typed. 16,758 stars none of them makes Opus smarter. every one stops it from paying for work it never needed to do the full setup with scripts is in the article. do the measuring step first, so you know what you actually saved

install these before your next long Claude Code session if your Opus 5.5 bill hurts and you don’t know where to start, copy this: claude-code-router: sits in front of Claude Code and sends each request to the cheapest model that can do it. Haiku does the grep, Opus only gets the hard part. 37k stars rtk: shrinks test, build and git output before the model sees it. one binary, up to 90% less bash output in your context. 83k stars claude-mem: remembers what happened in your past sessions and feeds back only the relevant part, so you stop paying to re-explain your project every morning. 100k stars context-mode: a huge tool output goes into a local database instead of your context window, and Claude pulls out only the lines it needs. 18k stars caveman: makes Claude answer in short telegraphic sentences. code stays identical, and output is the expensive side on Opus 5.5 ($20 per million). 51k stars token-optimizer: a local dashboard that shows where your tokens actually went, and keeps your work alive across compactions. 1.9k stars token-savior: replaces whole-file reads with symbol lookups, so Claude reads the function and not the 2,000 lines around it code-review-graph: maps your repo as a graph and gives Claude only the code connected to the change you’re reviewing jev-ultrafast: a browser agent where Jev picks every click, and a text model wakes up only when something has to be typed. 16,758 stars none of them makes Opus smarter. every one stops it from paying for work it never needed to do the full setup with scripts is in the article. do the measuring step first, so you know what you actually saved

rvaniaaa

24,787 просмотров • 26 дней назад

AI agents are already everywhere -- but most devtools weren't built for them. So we decided to do something about it. We ran Claude through each tool's getting-started guide and measured: → How fast it completed → How many tool calls it took → How many errors it hit → How much it cost ... that led to a final grade for how agent ready each tool is. See where your favorite tools landed →

AI agents are already everywhere -- but most devtools weren't built for them. So we decided to do something about it. We ran Claude through each tool's getting-started guide and measured: → How fast it completed → How many tool calls it took → How many errors it hit → How much it cost ... that led to a final grade for how agent ready each tool is. See where your favorite tools landed →

Mika Sagindyk

18,124 просмотров • 8 месяцев назад

This is getting f*cking useful: Claude can build your app while JEV spots easy jobs that don’t need an expensive AI. Someone packed that setup into an open-source repo called jev-kit. The idea is simple: > Claude writes code and solves the hard problems. JEV checks whether the agent picked for a job is more powerful than it needs to be. > Sending an expensive worker to find a file? The kit can flag it and suggest a cheaper one. > In enforce mode, it can block dispatches that are 2 or more tiers above what JEV judges necessary. > It also checks tool calls and sends agents back when they claim they’re done without verifying their work. There’s an optional browser agent too: > JEV picks the clicks > Claude writes text into fields > Sonnet planner can help with tasks where the steps aren’t clear That’s the useful part: fewer small decisions left to the big model, with checks around the work it produces. Start in shadow mode. See what gets flagged before letting it block anything. JEV calls need a TypeSafe API key. paste this into Claude Code: “Inspect jonathanavis96/jev-kit. Read docs/install.md and run install/install.sh –check-only. Show how the tier guard and verification check fit my setup. Keep shadow mode on and show all proposed changes before installing.” Let Claude solve the hard part. Check who you’re paying to do the easy part.

This is getting f*cking useful: Claude can build your app while JEV spots easy jobs that don’t need an expensive AI. Someone packed that setup into an open-source repo called jev-kit. The idea is simple: > Claude writes code and solves the hard problems. JEV checks whether the agent picked for a job is more powerful than it needs to be. > Sending an expensive worker to find a file? The kit can flag it and suggest a cheaper one. > In enforce mode, it can block dispatches that are 2 or more tiers above what JEV judges necessary. > It also checks tool calls and sends agents back when they claim they’re done without verifying their work. There’s an optional browser agent too: > JEV picks the clicks > Claude writes text into fields > Sonnet planner can help with tasks where the steps aren’t clear That’s the useful part: fewer small decisions left to the big model, with checks around the work it produces. Start in shadow mode. See what gets flagged before letting it block anything. JEV calls need a TypeSafe API key. paste this into Claude Code: “Inspect jonathanavis96/jev-kit. Read docs/install.md and run install/install.sh –check-only. Show how the tier guard and verification check fit my setup. Keep shadow mode on and show all proposed changes before installing.” Let Claude solve the hard part. Check who you’re paying to do the easy part.

kiosa

14,772 просмотров • 26 дней назад

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

72,340 просмотров • 8 месяцев назад

My whole company runs on skills I bundled into a GitHub repo. Here's how to build the same thing for your team: - Put your skills in a GitHub repo - Get Claude to write the couple of JSON files that make it readable as a plugin - In Claude Code, type /plugin, go to marketplaces, add marketplace, paste your repo URL - Split the plugins by department, so your copywriter isn't installing the finance skills It works in Codex too. I've got the same team skills installed there and I use them the same way. Now when I build something like my Notion formatting skill, I add it to the repo and it lands on everyone's Claude and Codex. If someone wrecks a skill, we roll it back to an older version. The key is enabling auto-update, so when someone improves a skill everyone benefits. I don't have a clue how the JSON works. I got Claude to set the whole thing up for me. Start with one skill and before you know it your whole team will be AI pilled.

My whole company runs on skills I bundled into a GitHub repo. Here's how to build the same thing for your team: - Put your skills in a GitHub repo - Get Claude to write the couple of JSON files that make it readable as a plugin - In Claude Code, type /plugin, go to marketplaces, add marketplace, paste your repo URL - Split the plugins by department, so your copywriter isn't installing the finance skills It works in Codex too. I've got the same team skills installed there and I use them the same way. Now when I build something like my Notion formatting skill, I add it to the repo and it lands on everyone's Claude and Codex. If someone wrecks a skill, we roll it back to an older version. The key is enabling auto-update, so when someone improves a skill everyone benefits. I don't have a clue how the JSON works. I got Claude to set the whole thing up for me. Start with one skill and before you know it your whole team will be AI pilled.

The Startup Ideas Podcast (SIP) 🧃

19,962 просмотров • 2 месяцев назад

Anthropic is furious: this secret tool can replicate any existing app x10 faster for free there's an open-source tool with 352k stars on GitHub that lets an AI agent take apart any app you have on your machine and explain exactly how a feature works. no source code needed. it's called REA. Reverse Engineer Anything. one line: npx rea-agents setup then you just ask Claude Code: "Understand how search works in the Notes app, show me the evidence, and build a similar feature for my project." and it does it. -> native binaries, through Ghidra, Hopper or IDA -> JavaScript and Electron apps -> .NET apps -> websites it runs locally. it shows its evidence. then it writes the code. that feature your team spent 8 months on? someone's agent can read how it works over lunch. so let's be honest about what this means: your moat was never the code. it was that copying you took effort. that effort just went to zero. the only things left that can't be cloned: your users, your speed, and your taste. and if your product dies because someone could see how it works, it was already dead. the repo is below. founders, you're going to hate this one save, share, and try later

Anthropic is furious: this secret tool can replicate any existing app x10 faster for free there's an open-source tool with 352k stars on GitHub that lets an AI agent take apart any app you have on your machine and explain exactly how a feature works. no source code needed. it's called REA. Reverse Engineer Anything. one line: npx rea-agents setup then you just ask Claude Code: "Understand how search works in the Notes app, show me the evidence, and build a similar feature for my project." and it does it. -> native binaries, through Ghidra, Hopper or IDA -> JavaScript and Electron apps -> .NET apps -> websites it runs locally. it shows its evidence. then it writes the code. that feature your team spent 8 months on? someone's agent can read how it works over lunch. so let's be honest about what this means: your moat was never the code. it was that copying you took effort. that effort just went to zero. the only things left that can't be cloned: your users, your speed, and your taste. and if your product dies because someone could see how it works, it was already dead. the repo is below. founders, you're going to hate this one save, share, and try later

kiosa

52,433 просмотров • 19 дней назад

In Claude Code, Opus 4.8 makes calls like an experienced engineer without needing constant check-ins. It stays on track across long-running sessions and follows work through in your repo, so you can hand off a feature or a bug sweep while you focus on what's next.

In Claude Code, Opus 4.8 makes calls like an experienced engineer without needing constant check-ins. It stays on track across long-running sessions and follows work through in your repo, so you can hand off a feature or a bug sweep while you focus on what's next.

Claude

490,101 просмотров • 5 месяцев назад

Someone built peer, a small tool that lets Claude Code and Codex message each other without typing into each other's terminals. → it routes messages by name through each agent's input path → it gives delivery feedback → it aims to keep those messages from colliding with your typing or approval prompts Compatibility and reliability weren't independently checked. This is messaging, not sandboxing or permission enforcement.

Someone built peer, a small tool that lets Claude Code and Codex message each other without typing into each other's terminals. → it routes messages by name through each agent's input path → it gives delivery feedback → it aims to keep those messages from colliding with your typing or approval prompts Compatibility and reliability weren't independently checked. This is messaging, not sandboxing or permission enforcement.

0xMarioNawfal

55,463 просмотров • 1 день назад

🚨 SOMEONE LEAKED THE PROMPT THAT MAKES CLAUDE CODE CREATE ITS OWN SKILLS AND WORK BETTER EVERY DAY WITHOUT YOU TOUCHING ANYTHING No programming. Just paste. A single prompt does it all: Time needed: 2 minutes Actions: copy and paste into Claude Code The mistake 90% of people make with Claude: explaining the same thing to it every day. The same tone, the same steps, the same corrections. And the next day it starts from scratch again. → Detects what you repeat: reviews your project and asks you what tasks you do every week → Creates a skill for each one: instructions, templates, and examples that Claude loads only when it needs them → Tests them before giving them to you: runs each skill with a real case and fixes it if it fails → Learns from your corrections: every time you correct something, it updates the skill so it doesn't repeat the error → Zero code: you tell it what you do and Claude builds its own library of skills Before, this meant writing manuals, templates, and processes for weeks. Now it's just Ctrl+V. Save it before they delete it 🔖 Follow Tomcruise AI for more...

🚨 SOMEONE LEAKED THE PROMPT THAT MAKES CLAUDE CODE CREATE ITS OWN SKILLS AND WORK BETTER EVERY DAY WITHOUT YOU TOUCHING ANYTHING No programming. Just paste. A single prompt does it all: Time needed: 2 minutes Actions: copy and paste into Claude Code The mistake 90% of people make with Claude: explaining the same thing to it every day. The same tone, the same steps, the same corrections. And the next day it starts from scratch again. → Detects what you repeat: reviews your project and asks you what tasks you do every week → Creates a skill for each one: instructions, templates, and examples that Claude loads only when it needs them → Tests them before giving them to you: runs each skill with a real case and fixes it if it fails → Learns from your corrections: every time you correct something, it updates the skill so it doesn't repeat the error → Zero code: you tell it what you do and Claude builds its own library of skills Before, this meant writing manuals, templates, and processes for weeks. Now it's just Ctrl+V. Save it before they delete it 🔖 Follow Tomcruise AI for more...

Tomcruise AI

38,809 просмотров • 2 дней назад

Here's what the Founder of Claude Code does before he starts ANY project: 1. Plans first, codes never, he goes back and forth with Claude on the plan until it's perfect. No code gets written yet 2. Creates a CLAUDE.md file (a simple doc that Claude reads every session so it knows your project, your rules, your style) 3. Gives Claude a way to verify its own work - For backend: write and run tests - For UI: take screenshots, check in browser Claude should never finish a task without proving it works 4. Sets up project-level permission rules in settings.json instead of skipping permissions entirely. Shared with the whole team 5. Five more preparation steps in VIDEO BELOW 6. Only then switches to auto-accept mode and lets Claude build The part most people miss: he doesn't treat Claude as a magic box that gets things right first try he treats it like a junior dev that needs clear instructions, feedback loops, and guardrails at scale he runs multiple sessions in parallel, uses Opus with thinking enabled because it makes fewer mistakes even though it's slower and relies on background agents that push code for later review his setup is surprisingly simple. no crazy custom tools. just slash commands, subagents, and a clean CLAUDE.md the difference isn't the tool. it's how you set it up before you start ❤️ P.S. for sure 99.5% of readers will scroll down this tweet, but I send it to 0.5% who loves to learn how to improve your workflow daily and control 99.5% in 2 years Hard skills literally mean nothing in our world The most important skills which you can have are: building architectures and orchestrations If you master it and use a creative approach, CONGRATS

Here's what the Founder of Claude Code does before he starts ANY project: 1. Plans first, codes never, he goes back and forth with Claude on the plan until it's perfect. No code gets written yet 2. Creates a CLAUDE.md file (a simple doc that Claude reads every session so it knows your project, your rules, your style) 3. Gives Claude a way to verify its own work - For backend: write and run tests - For UI: take screenshots, check in browser Claude should never finish a task without proving it works 4. Sets up project-level permission rules in settings.json instead of skipping permissions entirely. Shared with the whole team 5. Five more preparation steps in VIDEO BELOW 6. Only then switches to auto-accept mode and lets Claude build The part most people miss: he doesn't treat Claude as a magic box that gets things right first try he treats it like a junior dev that needs clear instructions, feedback loops, and guardrails at scale he runs multiple sessions in parallel, uses Opus with thinking enabled because it makes fewer mistakes even though it's slower and relies on background agents that push code for later review his setup is surprisingly simple. no crazy custom tools. just slash commands, subagents, and a clean CLAUDE.md the difference isn't the tool. it's how you set it up before you start ❤️ P.S. for sure 99.5% of readers will scroll down this tweet, but I send it to 0.5% who loves to learn how to improve your workflow daily and control 99.5% in 2 years Hard skills literally mean nothing in our world The most important skills which you can have are: building architectures and orchestrations If you master it and use a creative approach, CONGRATS

Ronin

148,303 просмотров • 6 месяцев назад

How I have Claude automate anything I do on my computer just by showing it: I use the free Clips app and hit record to start recording. Then I just do the action - like navigating to Rippling and approving any unapproved time off - and I’ll often just talk out loud as I do it explaining any add’l details like I would when showing a human. The Clips app captures everything on your screen and everything you say, and transforms it into a format Claude can “see and hear”. You'll then get a link that you can easily share with Claude (or humans too). I’ll paste it to Claude and say something like, "automate this for me every day at 8:00 AM." The link has special metadata that agents like Claude can discover. It exposes APIs to see the full transcript with timestamps and grab screenshots of what was on your screen at any of those timestamps. Once it's created the routine, you can go to the Routines tab in Claude Code desktop app. This also works with the CLI, Claude Cowork, Codex etc. You’ll see your new routine there, and you can just hit Run Now to have it start running it. Video attached shows this step by step. The Clips apps is free and open source - I’ll link to it and the source code in the thread.

How I have Claude automate anything I do on my computer just by showing it: I use the free Clips app and hit record to start recording. Then I just do the action - like navigating to Rippling and approving any unapproved time off - and I’ll often just talk out loud as I do it explaining any add’l details like I would when showing a human. The Clips app captures everything on your screen and everything you say, and transforms it into a format Claude can “see and hear”. You'll then get a link that you can easily share with Claude (or humans too). I’ll paste it to Claude and say something like, "automate this for me every day at 8:00 AM." The link has special metadata that agents like Claude can discover. It exposes APIs to see the full transcript with timestamps and grab screenshots of what was on your screen at any of those timestamps. Once it's created the routine, you can go to the Routines tab in Claude Code desktop app. This also works with the CLI, Claude Cowork, Codex etc. You’ll see your new routine there, and you can just hit Run Now to have it start running it. Video attached shows this step by step. The Clips apps is free and open source - I’ll link to it and the source code in the thread.

Steve (Builder.io)

25,473 просмотров • 4 месяцев назад