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.

I used to dread heavy testing days because every API call felt like watching money disappear in real time. Found a backend built to run flat instead of per call, made specifically for agent work. Pointed my Claude Code setup at it and had it running in under 5... show more

Z-Coder

22,986 subscribers

60,855 views • 4 months ago •via X (Twitter)

Science & Technology

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Want to reduce your Claude Code bill? Claude Code uses smaller models like Haiku for simple tasks. Instead of sending every small request to a paid API, run those tasks locally with Jan and keep heavier work in the cloud. One setup. Lower API usage. More control. Get the latest version at

Want to reduce your Claude Code bill? Claude Code uses smaller models like Haiku for simple tasks. Instead of sending every small request to a paid API, run those tasks locally with Jan and keep heavier work in the cloud. One setup. Lower API usage. More control. Get the latest version at

👋 Jan

13,169 views • 8 months ago

THIS ENGINEER RUNS CLAUDE CODE WITHOUT PAYING ANTHROPIC A SINGLE DOLLAR RTX 5090 under the desk, Qwen 3.5 35B, 140 tokens per second Claude Code pointed at localhost instead of Anthropic’s servers override two environment variables and your API bill drops to zero he built a full-stack Next.js app from scratch to prove it works then showed every bug and limitation other YouTubers hide same setup I run with two GPUs and Qwen 3.6 27B full breakdown ↓

THIS ENGINEER RUNS CLAUDE CODE WITHOUT PAYING ANTHROPIC A SINGLE DOLLAR RTX 5090 under the desk, Qwen 3.5 35B, 140 tokens per second Claude Code pointed at localhost instead of Anthropic’s servers override two environment variables and your API bill drops to zero he built a full-stack Next.js app from scratch to prove it works then showed every bug and limitation other YouTubers hide same setup I run with two GPUs and Qwen 3.6 27B full breakdown ↓

leopardracer

29,756 views • 5 months ago

I pointed the new Claude Managed Agents dynamic workflows at 18k lines of code. > 21 proven bugs. > 5 minutes. > $8.36, on my Claude Max API credits. A lead agent writes a plan, runs it across many agents in phases, then merges the results. Try it in Claude Code: /claude-api managed-agents-onboard bug-hunter It burns tokens fast. It's worth it.

I pointed the new Claude Managed Agents dynamic workflows at 18k lines of code. > 21 proven bugs. > 5 minutes. > $8.36, on my Claude Max API credits. A lead agent writes a plan, runs it across many agents in phases, then merges the results. Try it in Claude Code: /claude-api managed-agents-onboard bug-hunter It burns tokens fast. It's worth it.

Dan McAteer

11,404 views • 25 days ago

claude code does indeed run a call to haiku every single time it uses Bash() patched version normal claude

claude code does indeed run a call to haiku every single time it uses Bash() patched version normal claude

f1shy-dev

68,929 views • 9 months ago

Ex-Google engineer built a graph-based workflow that made Claude Code do nearly 10 days of work in about an hour. Here's the exact setup he uses. step 1. create a separate Git worktree for every task. run: git worktree add ../task-1 -b task-1 open a new terminal, cd into it, and launch Claude Code. repeat this for every agent. each one gets its own branch, so nothing conflicts. step 2. give every Claude agent a different task. same repository. different branches. they all work in parallel. step 3. once they're done, review the pull requests. keep the good ones. merge what works. step 4. add a review agent. paste each PR into Claude and ask: "does this implementation match the original specification" every agent now has another agent reviewing its work before it gets merged. step 5. scale it up. 48GB of RAM can comfortably run around 20 Claude Code agents. 128GB can handle roughly 50. most engineers run Claude Code once and wait. he runs dozens of Claude Code agents in parallel, then merges the best results. this 60-minute lecture is one of the best free resources on graph engineering and multi-agent workflows. bookmark it and watch it below.

Ex-Google engineer built a graph-based workflow that made Claude Code do nearly 10 days of work in about an hour. Here's the exact setup he uses. step 1. create a separate Git worktree for every task. run: git worktree add ../task-1 -b task-1 open a new terminal, cd into it, and launch Claude Code. repeat this for every agent. each one gets its own branch, so nothing conflicts. step 2. give every Claude agent a different task. same repository. different branches. they all work in parallel. step 3. once they're done, review the pull requests. keep the good ones. merge what works. step 4. add a review agent. paste each PR into Claude and ask: "does this implementation match the original specification" every agent now has another agent reviewing its work before it gets merged. step 5. scale it up. 48GB of RAM can comfortably run around 20 Claude Code agents. 128GB can handle roughly 50. most engineers run Claude Code once and wait. he runs dozens of Claude Code agents in parallel, then merges the best results. this 60-minute lecture is one of the best free resources on graph engineering and multi-agent workflows. bookmark it and watch it below.

MIKE

32,313 views • 3 months ago

Boris Cherny, the creator of Claude Code: "Most people use Claude Code as a chatbot. It was built to run an entire engineering team." In 30 minutes on stage, he explains how he now works by directing agents instead of writing code by hand. Watch full video, then save the exact setup below👇

Boris Cherny, the creator of Claude Code: "Most people use Claude Code as a chatbot. It was built to run an entire engineering team." In 30 minutes on stage, he explains how he now works by directing agents instead of writing code by hand. Watch full video, then save the exact setup below👇

darkzodchi

35,506 views • 5 months ago

$It is becoming f*cking dangerous: a model that never writes a single word now judges every move your Claude AI agent makes -> Create a folder named JEV LAB on your PC and launch Claude Code inside it -> Install the Jev CLI: npm install -g jev-axi -> Grab a key at and run: jev-axi config set apiKey YOUR_KEY -> Run jev-axi setup safety so every command Claude runs gets checked first. Dangerous downloads get denied, routine tests pass for free -> Run jev-axi setup git-hooks to stop any commit that sneaks in a password or API key -> Feed it anything your agent reads: jev-axi guard Run jev-axi setup supervise --project to catch the moment your agent quits early or gets stuck in a loop The whole setup takes around 5 minutes Turn Claude into an agent with a second opinion: every command screened, every page checked for prompt injection, every commit scanned for secrets. For a fraction of a cent per check Bonus: pipe a broken build into jev-axi triage and it finds the root cause for you Bookmark this article and check repo below:$

It is becoming f*cking dangerous: a model that never writes a single word now judges every move your Claude AI agent makes -> Create a folder named JEV LAB on your PC and launch Claude Code inside it -> Install the Jev CLI: npm install -g jev-axi -> Grab a key at and run: jev-axi config set apiKey YOUR_KEY -> Run jev-axi setup safety so every command Claude runs gets checked first. Dangerous downloads get denied, routine tests pass for free -> Run jev-axi setup git-hooks to stop any commit that sneaks in a password or API key -> Feed it anything your agent reads: jev-axi guard Run jev-axi setup supervise --project to catch the moment your agent quits early or gets stuck in a loop The whole setup takes around 5 minutes Turn Claude into an agent with a second opinion: every command screened, every page checked for prompt injection, every commit scanned for secrets. For a fraction of a cent per check Bonus: pipe a broken build into jev-axi triage and it finds the root cause for you Bookmark this article and check repo below:

kiosa

29,602 views • 18 days ago

ex engineer who spent 4 years at Anthropic put the entire $4.2M Claude Code playbook into one book no need to drop $2000 on a course to understand how cheap agents are built, the first 4 pages cover it: > page 1: where exactly 80% of your tokens disappear > page 2: the 4 blocks of a working agent, and 90% don't even know the first one > page 3: 12 cheap agents from the engineer himself, 2 minutes instead of an hour > page 4: the one line that keeps an agent running 24/7 for free every page is a ready setup you paste in and run in 5 minutes, no theory book in the comments ↓

ex engineer who spent 4 years at Anthropic put the entire $4.2M Claude Code playbook into one book no need to drop $2000 on a course to understand how cheap agents are built, the first 4 pages cover it: > page 1: where exactly 80% of your tokens disappear > page 2: the 4 blocks of a working agent, and 90% don't even know the first one > page 3: 12 cheap agents from the engineer himself, 2 minutes instead of an hour > page 4: the one line that keeps an agent running 24/7 for free every page is a ready setup you paste in and run in 5 minutes, no theory book in the comments ↓

Noisy

23,057 views • 12 days ago

🌟 Deploy and Automate in Minutes — No Code Required! John decided to test it for himself, and within minutes, he had a fully functional AI Agent live and running. Built with Agent Forge, no code, no barriers. Real logic. Real outcomes. Seamless deployment. 🔗 Try it:

🌟 Deploy and Automate in Minutes — No Code Required! John decided to test it for himself, and within minutes, he had a fully functional AI Agent live and running. Built with Agent Forge, no code, no barriers. Real logic. Real outcomes. Seamless deployment. 🔗 Try it:

AITECH CLOUD NETWORK

50,027 views • 1 year ago

Anthropic pays $750K/ year per senior engineer. The creator of Claude Code just revealed his coding setup at the Sequoia AI session. Boris Cherny: "100% of my code is written by Claude Code. I run around 100 agents at one time." free. 24 minutes. watch it then read article below

Anthropic pays $750K/ year per senior engineer. The creator of Claude Code just revealed his coding setup at the Sequoia AI session. Boris Cherny: "100% of my code is written by Claude Code. I run around 100 agents at one time." free. 24 minutes. watch it then read article below

Movez

425,935 views • 6 months ago

OpenClaw released v2026.4.26, and it just killed every AI voice tool. It can now answer your phone, make call and talk back in real time. AND import your entire Claude Code setup in one command. Which outreach campaign to business should I try? The AI agent era is crazy and beautiful.

OpenClaw released v2026.4.26, and it just killed every AI voice tool. It can now answer your phone, make call and talk back in real time. AND import your entire Claude Code setup in one command. Which outreach campaign to business should I try? The AI agent era is crazy and beautiful.

Antoine Rousseaux

47,906 views • 6 months ago

You can now run Claude Code locally for FREE. → Using open-source models → Locally and fully private → Full agent + tool workflows Here's the FULL step-by-step tutorial to get it all set up in less than 10 minutes:

You can now run Claude Code locally for FREE. → Using open-source models → Locally and fully private → Full agent + tool workflows Here's the FULL step-by-step tutorial to get it all set up in less than 10 minutes:

Alvaro Cintas

1,322,094 views • 9 months ago

Okay, this is the first AI content setup I've seen that actually closes the loop. Sabrina Ramonov (founder of Blotato) runs all her content solo, and her Claude agent is pulling 41M cross-platform views in 30 days. She went 0 to 3M followers in 2 years on $0 ads. Most AI content tools stop at "here's your draft." You still grade it, schedule it, and publish it by hand. Here's her full setup: → connect Claude to Blotato → install 7 free Claude skills (open sourced, no email gate) → write, grade, and schedule your first post from the same agent The skills do the real work: content-coach, post-writer, post-grader, viral-hooks, repurpose, brand-brief, post-scheduler. What sold me: it's built for agents. Blotato ships an LLM-readable API spec, so Claude Code, Codex, or Hermes can run the whole thing end to end. She breaks down the exact system in the piece. Worth the full read. (clip attached is a Claude Code agent-workflow talk worth watching alongside this.)

Prajwal Tomar

142,718 views • 3 months ago

Introducing the Ahrefs MCP killer - 85% cheaper than Ahrefs - Keywords, SERPs, backlinks and AI answers in one MCP - Free to start, pay per call - Run SEO directly in Claude Code or Codex Try it at

Introducing the Ahrefs MCP killer - 85% cheaper than Ahrefs - Keywords, SERPs, backlinks and AI answers in one MCP - Free to start, pay per call - Run SEO directly in Claude Code or Codex Try it at

Jesse Sibley

21,267 views • 28 days ago

Spent the day testing Claude Opus 4.7. Last month I built a design director agent for OpenClaw and now it cooks. 15 minutes in, Paper Design MCP + Claude Code had made me a rough draft. In under an hour, a Framer worthy site. My workflow: 1. Feed my agent references so it can extract design systems and lock in on my taste 2. Claude Code calls Paper Design MCP to generate the visual system (just keep the Paper app open) 3. Paper exports the assets and Claude Code then preps the build docs 4. Agent loops back, critiques, iterates Got no clue why anyone is paying $10K for a website anymore. It’s easy now.

Spent the day testing Claude Opus 4.7. Last month I built a design director agent for OpenClaw and now it cooks. 15 minutes in, Paper Design MCP + Claude Code had made me a rough draft. In under an hour, a Framer worthy site. My workflow: 1. Feed my agent references so it can extract design systems and lock in on my taste 2. Claude Code calls Paper Design MCP to generate the visual system (just keep the Paper app open) 3. Paper exports the assets and Claude Code then preps the build docs 4. Agent loops back, critiques, iterates Got no clue why anyone is paying $10K for a website anymore. It’s easy now.

klöss

14,650 views • 6 months ago

Before #Khakee (2017), while watching movies, I used to feel scared because of the jump scares, the loud sounds, the atmosphere, and the tension of not knowing what would happen next. But while watching this particular scene in Khakee, for the first time in my life, I genuinely felt fear running down my spine while watching a film. It felt terrifying because it seemed so real — something that could happen to anyone in real life.

Before #Khakee (2017), while watching movies, I used to feel scared because of the jump scares, the loud sounds, the atmosphere, and the tension of not knowing what would happen next. But while watching this particular scene in Khakee, for the first time in my life, I genuinely felt fear running down my spine while watching a film. It felt terrifying because it seemed so real — something that could happen to anyone in real life.

CineManiac

24,858 views • 5 months ago

I can't f*cking believe people still use Claude Code like a chat bot. the ones getting real work out of it gave it a folder, tools and a map of everything it knows. that map is graphify. you point it at a folder and it builds a knowledge graph of everything inside. code, docs, PDFs, images, even video. then your agent searches the graph instead of opening files one by one. 134k stars on GitHub. backed by Y Combinator. and most people still haven't tried it. what makes it different: -> the code part runs fully on your machine. nothing gets uploaded -> no vector database, no embeddings. it's a real graph your agent walks through -> every connection is labeled: read straight from the source, or figured out by graphify. you always know which -> you get 3 files: a clickable map you open in your browser, a report with the key ideas and surprising links, and the full graph your agent queries anytime on a public memory benchmark it found the right answer in its top 10 results about half the time. mem0 managed under 5%. and building the graph cost 0 model credits. here's the full setup around it: > create a folder called AGENT, open Claude Code inside it, and add a CLAUDE.md with one line: "save every decision, person and project to memory/" > run uv tool install graphifyy, then graphify install, then type /graphify . and the whole folder becomes a map Claude can search in seconds > run npm install -g @googleworkspace/cli, then gws auth setup and gws auth login. Claude can now read your Gmail, Calendar and Drive > run claude mcp add playwright npx @playwright/mcp@latest. it gets its own browser for sites, forms and data > run npm i -g jev-guard, then jev-guard key "...", then jev-guard install claude. Jev checks every action before it runs. rm -rf gets blocked, emails with hidden instructions get flagged, about 4 cents per 1,000 checks > type /schedule and say "every morning at 7:30, send me what came in, what you drafted and what needs my yes" one folder. 15 minutes. and Claude finally knows where everything is. all the repos: -> -> -> -> bookmark this and try graphify first. it's the piece everyone skips.

I can't f*cking believe people still use Claude Code like a chat bot. the ones getting real work out of it gave it a folder, tools and a map of everything it knows. that map is graphify. you point it at a folder and it builds a knowledge graph of everything inside. code, docs, PDFs, images, even video. then your agent searches the graph instead of opening files one by one. 134k stars on GitHub. backed by Y Combinator. and most people still haven't tried it. what makes it different: -> the code part runs fully on your machine. nothing gets uploaded -> no vector database, no embeddings. it's a real graph your agent walks through -> every connection is labeled: read straight from the source, or figured out by graphify. you always know which -> you get 3 files: a clickable map you open in your browser, a report with the key ideas and surprising links, and the full graph your agent queries anytime on a public memory benchmark it found the right answer in its top 10 results about half the time. mem0 managed under 5%. and building the graph cost 0 model credits. here's the full setup around it: > create a folder called AGENT, open Claude Code inside it, and add a CLAUDE.md with one line: "save every decision, person and project to memory/" > run uv tool install graphifyy, then graphify install, then type /graphify . and the whole folder becomes a map Claude can search in seconds > run npm install -g @googleworkspace/cli, then gws auth setup and gws auth login. Claude can now read your Gmail, Calendar and Drive > run claude mcp add playwright npx @playwright/mcp@latest. it gets its own browser for sites, forms and data > run npm i -g jev-guard, then jev-guard key "...", then jev-guard install claude. Jev checks every action before it runs. rm -rf gets blocked, emails with hidden instructions get flagged, about 4 cents per 1,000 checks > type /schedule and say "every morning at 7:30, send me what came in, what you drafted and what needs my yes" one folder. 15 minutes. and Claude finally knows where everything is. all the repos: -> -> -> -> bookmark this and try graphify first. it's the piece everyone skips.

kiosa

29,075 views • 10 days ago

They built an AI agent in 20 minutes and sold it to Anthropic for $100k - and at Stanford showed how to repeat it from scratch: 02:00 - how to build your first agent with Opus 5 in 20 minutes 22:34 - one agent replaces an Anthropic engineering team worth $200k a year 49:47 - how to make $1.2M a year selling agents to Anthropic and Google after watching I spent 20 minutes in Claude Code - the agent replaced 10 Anthropic engineers and they paid $100k and asked for more. save & watch - the article below shows how to build an agent in Claude Code in 20 minutes and reach $1.2M a year.

They built an AI agent in 20 minutes and sold it to Anthropic for $100k - and at Stanford showed how to repeat it from scratch: 02:00 - how to build your first agent with Opus 5 in 20 minutes 22:34 - one agent replaces an Anthropic engineering team worth $200k a year 49:47 - how to make $1.2M a year selling agents to Anthropic and Google after watching I spent 20 minutes in Claude Code - the agent replaced 10 Anthropic engineers and they paid $100k and asked for more. save & watch - the article below shows how to build an agent in Claude Code in 20 minutes and reach $1.2M a year.

Noisy

135,446 views • 2 months ago

They built an AI agent in 20 minutes and sold it to Anthropic for $100k - and at Stanford showed how to repeat it from scratch: 02:00 - how to build your first agent with Opus 5 in 20 minutes 22:34 - one agent replaces an Anthropic engineering team worth $200k a year 49:47 - how to make $1.2M a year selling agents to Anthropic and Google after watching I spent 20 minutes in Claude Code - the agent replaced 10 Anthropic engineers and they paid $100k and asked for more. save & watch - the article below shows how to build an agent in Claude Code in 20 minutes and reach $1.2M a year.

They built an AI agent in 20 minutes and sold it to Anthropic for $100k - and at Stanford showed how to repeat it from scratch: 02:00 - how to build your first agent with Opus 5 in 20 minutes 22:34 - one agent replaces an Anthropic engineering team worth $200k a year 49:47 - how to make $1.2M a year selling agents to Anthropic and Google after watching I spent 20 minutes in Claude Code - the agent replaced 10 Anthropic engineers and they paid $100k and asked for more. save & watch - the article below shows how to build an agent in Claude Code in 20 minutes and reach $1.2M a year.

shobhanai

82,627 views • 1 month ago

Boris Cherny, Head of Claude Code at Anthropic: "I do not prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops." The person who built the most used AI coding tool stopped prompting entirely. Most people using it every day are still typing one request at a time. This Github repo changes that. ↳ Seven production loop patterns with real token cost estimates ↳ CLI that scaffolds your entire loop in five minutes ↳ Starters for Grok, Claude Code, Codex, and Opencode The repo gives you the framework. My article covers the mental shift that makes it actually work.

Boris Cherny, Head of Claude Code at Anthropic: "I do not prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops." The person who built the most used AI coding tool stopped prompting entirely. Most people using it every day are still typing one request at a time. This Github repo changes that. ↳ Seven production loop patterns with real token cost estimates ↳ CLI that scaffolds your entire loop in five minutes ↳ Starters for Grok, Claude Code, Codex, and Opencode The repo gives you the framework. My article covers the mental shift that makes it actually work.

Kanika

20,693 views • 3 months ago