Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

Advent of Claude Day 7 - Headless Mode Want to use Claude Code in scripts, CI/CD, or automation? Just add -p: * claude -p "Fix the lint errors" * claude -p "List all the functions " | grep "async" * git diff | claude -p "Explain these changes" AI... show more

Ado

31,164 subscribers

82,124 views • 7 months ago •via X (Twitter)

Comedy Education Science & Technology

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

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,028 views • 1 month ago

Advent of Claude Day 9 - Claude Code Remote & your prompt ↳ Sends the task to Claude Code on the web (runs in background) claude --teleport session_abc123 ↳ Pulls and resumes the session in your local terminal to continue working Claude at home and on the go.

Advent of Claude Day 9 - Claude Code Remote & your prompt ↳ Sends the task to Claude Code on the web (runs in background) claude --teleport session_abc123 ↳ Pulls and resumes the session in your local terminal to continue working Claude at home and on the go.

Ado

38,702 views • 7 months ago

Advent of Claude Day 19 - Claude Code + Chrome Claude can now directly interact with your browser. Navigating pages, clicking buttons, reading console errors, inspecting the DOM, and more. "Fix the bug and verify it works" is now one prompt. /chrome to start.

Advent of Claude Day 19 - Claude Code + Chrome Claude can now directly interact with your browser. Navigating pages, clicking buttons, reading console errors, inspecting the DOM, and more. "Fix the bug and verify it works" is now one prompt. /chrome to start.

Ado

137,552 views • 6 months ago

Advent of Claude Day 17 - @ Mentions @ mentions in Claude Code may be overpowered: * Add one or many files into context instantly * Quickly list directories * Enable/disable/invoke MCP servers and subagents @ is the fastest path from "I need context" to "Claude has context."

Advent of Claude Day 17 - @ Mentions @ mentions in Claude Code may be overpowered: * Add one or many files into context instantly * Quickly list directories * Enable/disable/invoke MCP servers and subagents @ is the fastest path from "I need context" to "Claude has context."

Ado

27,634 views • 6 months ago

There's a built-in agent inside Claude Code you can invoke just by telling Claude to use the claude-code-guide agent Save this... you'll need it It's not a local file in your project. It's a built-in subagent defined in Claude Code's system itself. It answers questions about Claude Code CLI, the Agent SDK, and the Claude API. It uses Glob, Grep, Read, WebFetch, and WebSearch, but can't edit or write files. Its only job is to answer questions.

There's a built-in agent inside Claude Code you can invoke just by telling Claude to use the claude-code-guide agent Save this... you'll need it It's not a local file in your project. It's a built-in subagent defined in Claude Code's system itself. It answers questions about Claude Code CLI, the Agent SDK, and the Claude API. It uses Glob, Grep, Read, WebFetch, and WebSearch, but can't edit or write files. Its only job is to answer questions.

Daniel San

57,240 views • 4 months ago

Advent of Claude Day 30 - LSP Language Server Protocol in Claude Code provides - Instant diagnostics to see errors and warnings - Navigation with go to definition, find references, and more - Type info and docs for code symbols Claude Code now has IDE-level code intelligence

Advent of Claude Day 30 - LSP Language Server Protocol in Claude Code provides - Instant diagnostics to see errors and warnings - Navigation with go to definition, find references, and more - Type info and docs for code symbols Claude Code now has IDE-level code intelligence

Ado

100,603 views • 6 months ago

ICYMI - Claude Code in the Claude Desktop app! Benefits: → Visual session management instead of terminal tabs → Parallel sessions via git worktrees → Run locally or in the cloud → One-click to open in VS Code or CLI Same Claude Code. Better ergonomics.

ICYMI - Claude Code in the Claude Desktop app! Benefits: → Visual session management instead of terminal tabs → Parallel sessions via git worktrees → Run locally or in the cloud → One-click to open in VS Code or CLI Same Claude Code. Better ergonomics.

Ado

171,819 views • 5 months ago

Claude Code now runs in GitLab CI/CD pipelines 🚀 Tag @ Claude in issues or merge requests to run automated coding tasks in secure containers, with all changes following your branch protection and review workflows. ✅ Available via the Anthropic API, Amazon Bedrock, and Google Vertex AI ✅ Customize Claude Code for your codebase by adding a file to your repository root ✅ Delegate code reviews, bug fixes, and implementation plans to complete routine tasks asynchronously Get started with Claude Code in GitLab:

Claude Code now runs in GitLab CI/CD pipelines 🚀 Tag @ Claude in issues or merge requests to run automated coding tasks in secure containers, with all changes following your branch protection and review workflows. ✅ Available via the Anthropic API, Amazon Bedrock, and Google Vertex AI ✅ Customize Claude Code for your codebase by adding a file to your repository root ✅ Delegate code reviews, bug fixes, and implementation plans to complete routine tasks asynchronously Get started with Claude Code in GitLab:

🦊 GitLab

33,622 views • 10 months ago

Claude Code: "npm add ..." You: "Use pnpm, you idiot!" *adds it to CLAUDE.md* Claude: "npm add ..." There's a better way:

Claude Code: "npm add ..." You: "Use pnpm, you idiot!" adds it to CLAUDE.md Claude: "npm add ..." There's a better way:

Matt Pocock

149,886 views • 4 months ago

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 views • 3 months ago

Anthropic just gave OpenClaw the green light Anthropic staff confirmed that CLI-based usage is sanctioned. We’ve successfully bridged the Claude Code CLI directly into the OpenClaw gateway, letting you run your entire agent fleet on your Pro/Max plan and no additional API tokens required. The Implementation: - Auth: Log in to Claude Code locally: claude auth login - Path: Grab your binary location: which claude - Bridge: Drop the path into your openclaw.json under agents.defaults: "cliBackends": { "claude-cli": { "args": [ "-p", "--output-format", "json" ], "command": " ", "input": "arg", "output": "json", "serialize": true, "sessionArg": "--session-id", "sessionMode": "existing" } }, "model": { "primary": "claude-cli/claude-opus-4-6" }, "models": { "claude-cli/claude-opus-4-6": {}, "claude-cli/claude-opus-4-7": {}, "claude-cli/claude-sonnet-4-6": {} }, The Result: OpenClaw reuses your local session IDs and subscription limits. You get the full power of Opus and Sonnet without the restricted OAuth endpoints or the API tax. They sanctioned the path. We built the bridge. Here is a video how I done it step by step:

Anthropic just gave OpenClaw the green light Anthropic staff confirmed that CLI-based usage is sanctioned. We’ve successfully bridged the Claude Code CLI directly into the OpenClaw gateway, letting you run your entire agent fleet on your Pro/Max plan and no additional API tokens required. The Implementation: - Auth: Log in to Claude Code locally: claude auth login - Path: Grab your binary location: which claude - Bridge: Drop the path into your openclaw.json under agents.defaults: "cliBackends": { "claude-cli": { "args": [ "-p", "--output-format", "json" ], "command": " ", "input": "arg", "output": "json", "serialize": true, "sessionArg": "--session-id", "sessionMode": "existing" } }, "model": { "primary": "claude-cli/claude-opus-4-6" }, "models": { "claude-cli/claude-opus-4-6": {}, "claude-cli/claude-opus-4-7": {}, "claude-cli/claude-sonnet-4-6": {} }, The Result: OpenClaw reuses your local session IDs and subscription limits. You get the full power of Opus and Sonnet without the restricted OAuth endpoints or the API tax. They sanctioned the path. We built the bridge. Here is a video how I done it step by step:

Ziwen

182,975 views • 2 months ago

Using the extension, Claude Code can test code directly in the browser to validate its work. Claude can also see client-side errors via console logs. Try it out by running /chrome in the latest version of Claude Code.

Using the extension, Claude Code can test code directly in the browser to validate its work. Claude can also see client-side errors via console logs. Try it out by running /chrome in the latest version of Claude Code.

Claude

783,556 views • 6 months ago

Claude Code on your Phone is OFFICIAL (it changes everything) ----> introducing claude-remote Claude Anthropic

Claude Code on your Phone is OFFICIAL (it changes everything) ----> introducing claude-remote Claude Anthropic

NetworkChuck

50,678 views • 4 months ago

Claude is now available in Slack. Chat with Claude through DMs, tag @.Claude in threads, or use the AI assistant panel—with access to web search, document analysis, and your connected tools.

Claude is now available in Slack. Chat with Claude through DMs, tag @.Claude in threads, or use the AI assistant panel—with access to web search, document analysis, and your connected tools.

Claude

515,846 views • 9 months ago

Claude Code is now included in the Claude Pro plan which means Pro plan subscribers can use their rate limits for Claude apps and Claude Code! To celebrate, here's a conversation with Claude Code's founding engineer, Boris Cherny, on: - how we use Claude Code at Anthropic - underrated tips for using it effectively - the future of coding tools - and more!

Claude Code is now included in the Claude Pro plan which means Pro plan subscribers can use their rate limits for Claude apps and Claude Code! To celebrate, here's a conversation with Claude Code's founding engineer, Boris Cherny, on: - how we use Claude Code at Anthropic - underrated tips for using it effectively - the future of coding tools - and more!

Alex Albert

123,686 views • 1 year ago

We’ve been building this in secret for a while. We love Claude Code, and we’ve reimplemented “Claude Code” in Genspark. Introducing Genspark AI Developer - “Claude Code” in the browser - “Claude Code” on mobile - Everyone can build, no coding experience required - Supports multiple frontier models: Claude Sonnet 4, Claude Opus 4.1, GPT‑5, Kimi + Groq 1/4

We’ve been building this in secret for a while. We love Claude Code, and we’ve reimplemented “Claude Code” in Genspark. Introducing Genspark AI Developer - “Claude Code” in the browser - “Claude Code” on mobile - Everyone can build, no coding experience required - Supports multiple frontier models: Claude Sonnet 4, Claude Opus 4.1, GPT‑5, Kimi + Groq 1/4

Eric Jing

23,245,701 views • 10 months ago

Claude Code isn't just for Anthropic subscriptions anymore. How to use Claude Code with Venice:

Claude Code isn't just for Anthropic subscriptions anymore. How to use Claude Code with Venice:

Venice

25,146 views • 5 months ago

Claude Code just got a memory upgrade. And it’s kind of insane. A free tool called Claude Mem lets Claude remember everything across sessions. The result? Up to 95% fewer tokens used. Which means faster workflows and way cheaper AI automation. This fixes Claude Code’s biggest weakness.

Claude Code just got a memory upgrade. And it’s kind of insane. A free tool called Claude Mem lets Claude remember everything across sessions. The result? Up to 95% fewer tokens used. Which means faster workflows and way cheaper AI automation. This fixes Claude Code’s biggest weakness.

Julian Goldie SEO

11,989 views • 4 months ago

Just shipped two cool updates for Claude Code in the Desktop app. 1. Plan mode is now available on Desktop. Have Claude map out its approach before making any changes

Just shipped two cool updates for Claude Code in the Desktop app. 1. Plan mode is now available on Desktop. Have Claude map out its approach before making any changes

Boris Cherny

362,290 views • 5 months ago

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 views • 27 days ago