正在加载视频...

视频加载失败

加载此视频时出现问题。这可能是由于临时网络问题，或视频可能不可用。

Claude Code just shipped three updates. None of them need installing (they're already on your machine). 1. Sessions can talk to each other ↳ @ a session by name, same as tagging a person 2. /design ↳ editable artboards on a canvas, inside Claude Code 3. Concise output style... show more

Charlie Hills

13,325 subscribers

20,022 次观看 • 1 天前 •via X (Twitter)

科学技术教育

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Maximizing your token throughput is one of the biggest productivity unlocks in Claude Code. So here's my guide to use multiple Claude Codes at the same time, effectively: - Run multiple Claude Code sessions at the same time, each on a different feature (Ghostty is great for this) - Use Claude Code's built in git worktrees to keep each instance isolated on its own branch (-w or --worktree flag) - Let Claude handle creating PRs or merging the worktree branches when you're done - Use the Claude Code Desktop app as your multi-agent control center Full guide below:

Maximizing your token throughput is one of the biggest productivity unlocks in Claude Code. So here's my guide to use multiple Claude Codes at the same time, effectively: - Run multiple Claude Code sessions at the same time, each on a different feature (Ghostty is great for this) - Use Claude Code's built in git worktrees to keep each instance isolated on its own branch (-w or --worktree flag) - Let Claude handle creating PRs or merging the worktree branches when you're done - Use the Claude Code Desktop app as your multi-agent control center Full guide below:

Avthar

10,723 次观看 • 4 个月前

Share Claude Code sessions with this command 👇 Just shipped v1.26.1 of claude-code-templates because I kept needing to hand off work mid-session. Run: npx claude-code-templates@latest --chats - All your sessions grouped by chat - Download any conversation To share a session: - Share the file, and add it to your project - Then run: claude "read @ chat-file .md and continue" Or if you are in the same account click on "Resume" and you will see the command: claude --resume session_id Built this to keep context flowing across the team without losing momentum.

Share Claude Code sessions with this command 👇 Just shipped v1.26.1 of claude-code-templates because I kept needing to hand off work mid-session. Run: npx claude-code-templates@latest --chats - All your sessions grouped by chat - Download any conversation To share a session: - Share the file, and add it to your project - Then run: claude "read @ chat-file .md and continue" Or if you are in the same account click on "Resume" and you will see the command: claude --resume session_id Built this to keep context flowing across the team without losing momentum.

Daniel San

10,787 次观看 • 9 个月前

Motion graphics used to take me an hour per scene (or more) Now I'm creating them in 3-5 minutes — without After Effects, without Premiere, without writing a single line of code. I'm a former LA filmmaker (still PGA). My entire video stack is now 3 tools: Claude Code + HyperFrames (from HeyGen) + Descript Here's how the workflow runs: 1. Drop my brand style guide into a folder (colors, fonts, components Claude reuses forever) 2. Paste a line from my Descript transcript into Claude Code: "Create a scene for this part of the video" 3. Claude Code reads my brand, generates the HyperFrames scene, renders it to MP4 4. Drag the MP4 into Descript, drop it on the matching line of the transcript 5. Done. 3-5 minutes per scene. The unlock is the brand style guide. Once Claude has your colors, fonts, and reusable components, every scene inherits your look automatically. Bonus — you can take a Claude Design export (.zip), hand it to Claude Code, and it'll convert the HTML into a HyperFrames video you can render and edit. I built a GitHub repo with all the skills pre-loaded. Non-developers can clone it, open Claude Code, and be rendering scenes in under 10 minutes. Full walkthrough (20 min video) below Repo (skills + brand template + music-from-transcript plugin): Bookmark this if you make videos. The brand-style-guide pattern alone will save you hours every week. If you're a creator or operator using AI for content — share this with someone who's still living in After Effects.

JJ Englert

103,543 次观看 • 4 个月前

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.

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 次观看 • 2 个月前

THIS GUY MADE CLAUDE CODE AND CODEX TALK TO EACH OTHER not by switching between them, they literally talk to each other about your code in real time you give it a task. it spawns a Claude agent and a Codex agent in separate sessions. they share findings, challenge each other, and produce a combined result. he pointed them at an Express API with intentional security issues. within minutes they found SQL injection, hardcoded secrets, missing auth, and weak JWT config. one catches something and the other confirms it and adds context. they divide the work on their own for faster speed one command: /collab "review auth.js for security issues" that's it. you watch the conversation happen in real time. AND its open source with new models being integrated crazy to think that this was entirely vibe coded

THIS GUY MADE CLAUDE CODE AND CODEX TALK TO EACH OTHER not by switching between them, they literally talk to each other about your code in real time you give it a task. it spawns a Claude agent and a Codex agent in separate sessions. they share findings, challenge each other, and produce a combined result. he pointed them at an Express API with intentional security issues. within minutes they found SQL injection, hardcoded secrets, missing auth, and weak JWT config. one catches something and the other confirms it and adds context. they divide the work on their own for faster speed one command: /collab "review auth.js for security issues" that's it. you watch the conversation happen in real time. AND its open source with new models being integrated crazy to think that this was entirely vibe coded

Om Patel

25,318 次观看 • 4 个月前

A designer who can ship code is one of the most valuable hires in tech today. Here's my new episode with Felix Lee (CEO of ADPList) where he showed me how to use Claude Code and Figma MCP to go from: ✅ Figma → Code: Design to website in 15 min ✅ Code → Figma: App back to editable design Felix also demoed a few apps he's designed and built in Claude Code, including a 3D globe website and a landing page analyzer. Some takeaways from Felix: 1. Stop pasting screenshots into Claude Code. Instead, use Figma MCP to pull in all your assets, icons, and images automatically. 2. You can use the same MCP to convert code back into editable Figma layers to explore more variations. 3. An underrated way to build: Use FigJam to plan a flowchart of your app first, then paste the link into Claude Code with the MCP. 📌 Watch now: Thanks to our sponsors: Replit ⠕: Plan, design, and build with AI agents Linear: The AI agent platform for modern teams

A designer who can ship code is one of the most valuable hires in tech today. Here's my new episode with Felix Lee (CEO of ADPList) where he showed me how to use Claude Code and Figma MCP to go from: ✅ Figma → Code: Design to website in 15 min ✅ Code → Figma: App back to editable design Felix also demoed a few apps he's designed and built in Claude Code, including a 3D globe website and a landing page analyzer. Some takeaways from Felix: 1. Stop pasting screenshots into Claude Code. Instead, use Figma MCP to pull in all your assets, icons, and images automatically. 2. You can use the same MCP to convert code back into editable Figma layers to explore more variations. 3. An underrated way to build: Use FigJam to plan a flowchart of your app first, then paste the link into Claude Code with the MCP. 📌 Watch now: Thanks to our sponsors: Replit ⠕: Plan, design, and build with AI agents Linear: The AI agent platform for modern teams

Peter Yang

77,115 次观看 • 5 个月前

The person who built Claude Code just explained how he is using it "Now I just have an army of agents that are doing stuff" Only 18 minutes, the best Claude guide on the internet right now. Boris Cherny covered: > how Claude Code is moving beyond just engineers > routines for CI, code review, and daily workflows > why the loop is the next big leap > working with hundreds of agents at once everything is already running through agents, ignoring this is not an option that's exactly why I wrote a full guide on how to build one yourself with Claude Code article below

The person who built Claude Code just explained how he is using it "Now I just have an army of agents that are doing stuff" Only 18 minutes, the best Claude guide on the internet right now. Boris Cherny covered: > how Claude Code is moving beyond just engineers > routines for CI, code review, and daily workflows > why the loop is the next big leap > working with hundreds of agents at once everything is already running through agents, ignoring this is not an option that's exactly why I wrote a full guide on how to build one yourself with Claude Code article below

Anatoli Kopadze

16,858 次观看 • 2 个月前

I ran the same task on Claude Code and DeepSeek's new agent harness. One cost $150. The other cost $2. Today we're launching (AgentSky), the "OpenRouter for Agents" — one API → Claude Code, Codex, DeepSeek, Kimi, OpenCode, and every major agent in the cloud. And Agent Playground on top: race them on your own task, with your real tools (GitHub, Gmail, more), side by side in a browser: time, cost, tokens burnt. Guess which one was $2.

I ran the same task on Claude Code and DeepSeek's new agent harness. One cost $150. The other cost $2. Today we're launching (AgentSky), the "OpenRouter for Agents" — one API → Claude Code, Codex, DeepSeek, Kimi, OpenCode, and every major agent in the cloud. And Agent Playground on top: race them on your own task, with your real tools (GitHub, Gmail, more), side by side in a browser: time, cost, tokens burnt. Guess which one was $2.

Xiaoyin Qu

1,327,320 次观看 • 7 小时前

$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.$

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

461,640 次观看 • 2 个月前

Boris Cherny (Claude Code's creator): I deleted my IDE in November and hasn't opened it since. I writes more code than ever. his actual words on stage: I don't prompt Claude anymore. I have loops that are running. They're the ones prompting Claude. My job is to write loops. the progression he described: → a year ago: writing code by hand with autocomplete → then: running 5-10 Claudes in parallel, prompting each one → now: he doesn't prompt at all - he writes the loops that prompt Claude what it's already done inside Anthropic: • ~3x more code shipped per engineer (he says that number is already outdated and higher) • Cowork - a full product - built in ~8 days, 100% with Claude Code • designers, the finance guy, even the chief of staff now ship code his advice to founders: give everyone as many tokens as possible, and underfund every project on purpose - 2 engineers + a pile of tokens instead of 4. the roles are melting into one "builder." Watch this, than read the article below

Boris Cherny (Claude Code's creator): I deleted my IDE in November and hasn't opened it since. I writes more code than ever. his actual words on stage: I don't prompt Claude anymore. I have loops that are running. They're the ones prompting Claude. My job is to write loops. the progression he described: → a year ago: writing code by hand with autocomplete → then: running 5-10 Claudes in parallel, prompting each one → now: he doesn't prompt at all - he writes the loops that prompt Claude what it's already done inside Anthropic: • ~3x more code shipped per engineer (he says that number is already outdated and higher) • Cowork - a full product - built in ~8 days, 100% with Claude Code • designers, the finance guy, even the chief of staff now ship code his advice to founders: give everyone as many tokens as possible, and underfund every project on purpose - 2 engineers + a pile of tokens instead of 4. the roles are melting into one "builder." Watch this, than read the article below

Morty

136,663 次观看 • 2 个月前

Claude Code Templates now has a web interface for browsing and contributing templates 🙌 What it does: Install templates for different languages/frameworks to get started with Claude Code faster. How to use: - Go to - Run: npm install -g claude-code-templates - Pick a template from the site - Copy and run the template command - Start coding with Claude Code The whole thing runs on GitHub - no fancy backend, no hidden stuff. Everything you're installing is right there in the repo for you to inspect. Contributing: Want to add your own template? Just follow the contribution guide and send a PR. Once merged, it automatically shows up on the site. That's it... nothing fancy, just something to save a few minutes when starting new projects with Claude Code Repo:

Claude Code Templates now has a web interface for browsing and contributing templates 🙌 What it does: Install templates for different languages/frameworks to get started with Claude Code faster. How to use: - Go to - Run: npm install -g claude-code-templates - Pick a template from the site - Copy and run the template command - Start coding with Claude Code The whole thing runs on GitHub - no fancy backend, no hidden stuff. Everything you're installing is right there in the repo for you to inspect. Contributing: Want to add your own template? Just follow the contribution guide and send a PR. Once merged, it automatically shows up on the site. That's it... nothing fancy, just something to save a few minutes when starting new projects with Claude Code Repo:

Daniel San

60,766 次观看 • 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,177 次观看 • 2 个月前

A 14-year-old from China built three separate AI brains connected to Claude Code - and each one grows every day on its own. One brain for code, one for projects, one for everything else in his life. 600+ conversations on one topic in a single node - everything linked, everything accessible in one request without copying between tabs. But the main thing isn't storage. If Claude Code made a mistake and he corrected it once - the system remembered. That same mistake never happened again. No re-explaining context, no starting from zero - Claude already knows how he thinks. Instead of one giant messy file- a stack of smaller brains passing context to each other. Brain to brain to brain - just stacking intelligence while his classmates do homework by hand.

A 14-year-old from China built three separate AI brains connected to Claude Code - and each one grows every day on its own. One brain for code, one for projects, one for everything else in his life. 600+ conversations on one topic in a single node - everything linked, everything accessible in one request without copying between tabs. But the main thing isn't storage. If Claude Code made a mistake and he corrected it once - the system remembered. That same mistake never happened again. No re-explaining context, no starting from zero - Claude already knows how he thinks. Instead of one giant messy file- a stack of smaller brains passing context to each other. Brain to brain to brain - just stacking intelligence while his classmates do homework by hand.

Noisy

22,622 次观看 • 3 个月前

$Everyone's sleeping on MiniMax. Again. They just shipped M3. The first open-weights model to combine frontier coding, 1M context, and native multimodality in one drop. I plugged it into Claude Code this morning. Pasted a design from Dribbble. Watched M3 write production-ready React code in one session. At the agency, I just replaced Opus 4.8 with M3 for 80% of our coding tasks. The output is the same and we are running everything at a fraction of the cost. Open infrastructure is the future.$

Everyone's sleeping on MiniMax. Again. They just shipped M3. The first open-weights model to combine frontier coding, 1M context, and native multimodality in one drop. I plugged it into Claude Code this morning. Pasted a design from Dribbble. Watched M3 write production-ready React code in one session. At the agency, I just replaced Opus 4.8 with M3 for 80% of our coding tasks. The output is the same and we are running everything at a fraction of the cost. Open infrastructure is the future.

Prajwal Tomar

12,904 次观看 • 2 个月前

THE CEO OF OBSIDIAN JUST SHIPPED THE PATCH THAT LETS CLAUDE CODE DRIVE YOUR VAULT INSTEAD OF JUST READING IT. THE REPO PASSED 12,000 STARS BEFORE THE OFFICIAL ANNOUNCEMENT WENT UP 5 SKILL.md files. 1 MIT license. 0 lines of glue code drop .claude/skills/ into any vault. Claude Code registers Markdown, Bases, Canvas, CLI, and Webclipper on next session boot from that moment Claude opens the app, writes a Base view with the correct YAML, drops nodes on a Canvas, follows wikilinks correctly, clips URLs the way a power-user would. every action is a native Obsidian operation, not a text munge three formats that used to require a plugin developer or a paid template. now they get emitted by the same agent that writes your notes no MCP server. no vector db. no plugin store. no daemon in the background three years since kepano wrote "File over app". now the file has an agent that respects it you're reading this on a device that could clone the repo into your vault's .claude/skills/ folder and have Claude Code writing your first Base by lunch

THE CEO OF OBSIDIAN JUST SHIPPED THE PATCH THAT LETS CLAUDE CODE DRIVE YOUR VAULT INSTEAD OF JUST READING IT. THE REPO PASSED 12,000 STARS BEFORE THE OFFICIAL ANNOUNCEMENT WENT UP 5 SKILL.md files. 1 MIT license. 0 lines of glue code drop .claude/skills/ into any vault. Claude Code registers Markdown, Bases, Canvas, CLI, and Webclipper on next session boot from that moment Claude opens the app, writes a Base view with the correct YAML, drops nodes on a Canvas, follows wikilinks correctly, clips URLs the way a power-user would. every action is a native Obsidian operation, not a text munge three formats that used to require a plugin developer or a paid template. now they get emitted by the same agent that writes your notes no MCP server. no vector db. no plugin store. no daemon in the background three years since kepano wrote "File over app". now the file has an agent that respects it you're reading this on a device that could clone the repo into your vault's .claude/skills/ folder and have Claude Code writing your first Base by lunch

chewa.

13,367 次观看 • 1 个月前

CLAUDE CODE JUST GOT EYES Claude Code on desktop can now open and use a real browser, right inside the app. No screenshots, no copy pasting, no separate tools. - It opens docs, designs, or any site next to your code - It clicks, types, and fills forms exactly like a human would - It takes its own screenshots to check if the code actually works - It runs in a clean separate profile, none of your logins touched Your AI coding assistant just stopped being blind.

BuBBliK

49,154 次观看 • 1 个月前

Claude Code is the OpenClaw alternative you already had. I've been telling people this in person for three months. Now it's a piece on Every 📧. When OpenClaw was at peak hype a few months ago, everyone was going crazy over it — for good reasons. But almost nobody made the obvious comparison: Claude Code already does the thing you love about OpenClaw. In a lot of cases, better. Here's why people missed it. You have to understand the difference between a model and a harness. OpenClaw, at the end of the day, is just a harness on top of AI models. And Claude Code is too — it just got marketed as a coding tool, an alternative to Cursor. Until Cowork launched, almost nobody looked at it as a tool for non-programmers. Dan Shipper 📧 was one of the earliest to make that claim, and he was damn right. Let Claude Code run from the home folder of your computer with free access, and you get exactly what made OpenClaw exciting. Instead of just arguing it, here's a video walkthrough of a couple of my AI employees i built on the Claude Code harness. And here's the full article:

Claude Code is the OpenClaw alternative you already had. I've been telling people this in person for three months. Now it's a piece on Every 📧. When OpenClaw was at peak hype a few months ago, everyone was going crazy over it — for good reasons. But almost nobody made the obvious comparison: Claude Code already does the thing you love about OpenClaw. In a lot of cases, better. Here's why people missed it. You have to understand the difference between a model and a harness. OpenClaw, at the end of the day, is just a harness on top of AI models. And Claude Code is too — it just got marketed as a coding tool, an alternative to Cursor. Until Cowork launched, almost nobody looked at it as a tool for non-programmers. Dan Shipper 📧 was one of the earliest to make that claim, and he was damn right. Let Claude Code run from the home folder of your computer with free access, and you get exactly what made OpenClaw exciting. Instead of just arguing it, here's a video walkthrough of a couple of my AI employees i built on the Claude Code harness. And here's the full article:

Nityesh

22,895 次观看 • 1 个月前

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) 🧃

18,942 次观看 • 4 天前

I replaced Claude Code’s default --worktree command with a custom one built around Ghostty, Lazygit, and Yazi. By default, Claude Code creates worktrees inside the .claude/worktrees folder within the same project. That means if you spin up 3 worktrees, you end up with 3 complete copies of your project nested inside your main project. It makes the project structure messy and difficult to manage. So I built a hook that: - Overrides the default --worktree command - Creates each branch in a sibling directory: ../worktrees/branch-name - Automatically opens Ghostty panes - Launches Lazygit and Yazi already positioned in the correct branch directory Install it with: npx claude-code-templates@latest --hook=development-tools/worktree-ghostty --yes Now each branch lives where it should, outside the main project, and your terminal environment is ready instantly.

I replaced Claude Code’s default --worktree command with a custom one built around Ghostty, Lazygit, and Yazi. By default, Claude Code creates worktrees inside the .claude/worktrees folder within the same project. That means if you spin up 3 worktrees, you end up with 3 complete copies of your project nested inside your main project. It makes the project structure messy and difficult to manage. So I built a hook that: - Overrides the default --worktree command - Creates each branch in a sibling directory: ../worktrees/branch-name - Automatically opens Ghostty panes - Launches Lazygit and Yazi already positioned in the correct branch directory Install it with: npx claude-code-templates@latest --hook=development-tools/worktree-ghostty --yes Now each branch lives where it should, outside the main project, and your terminal environment is ready instantly.

Daniel San

66,869 次观看 • 6 个月前

Jenny Wen, head of design for Claude at Anthropic: "the design process is dead." what replaces it runs on machine-readable design systems In a 1-hour conversation, Jenny Wen breaks down why the discovery -> mock -> iterate loop is dying and what designers do instead. design system -> Claude Code -> every screen fixed at once, not one at a time i rebuilt the same 10-screen dashboard twice: ~6 hours of restyling by hand vs ~40 minutes when the fix lived in the system. how to build that system and hand it to Claude Code is in the article below.

Jenny Wen, head of design for Claude at Anthropic: "the design process is dead." what replaces it runs on machine-readable design systems In a 1-hour conversation, Jenny Wen breaks down why the discovery -> mock -> iterate loop is dying and what designers do instead. design system -> Claude Code -> every screen fixed at once, not one at a time i rebuilt the same 10-screen dashboard twice: ~6 hours of restyling by hand vs ~40 minutes when the fix lived in the system. how to build that system and hand it to Claude Code is in the article below.

Mnimiy

180,572 次观看 • 2 个月前