Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

wow... I just cut my claude code per-call cost to almost nothing with a 30-second config swap. Step 3.5 from StepFun plugs into your existing ~/.claude/settings.json by swapping three env vars. same workflow, different backend underneath. my agents have not stalled once since the switch. full setup below 🧵

mhdfaran's profile picture

Farhan

79,088 subscribers

17,871 Aufrufe • vor 4 Monaten •via X (Twitter)

BildungNachrichten & PolitikWissenschaft & Technologie
LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

last week I talked about claude code being my video editor, but it was only a small 30 second clip - here is my FULL workflow on how i have claude code edit ~30 minutes of raw video into a tight 10 minutes it uses STT for captions, then uses remotion to add the captions & cut!
7:28

last week I talked about claude code being my video editor, but it was only a small 30 second clip - here is my FULL workflow on how i have claude code edit ~30 minutes of raw video into a tight 10 minutes it uses STT for captions, then uses remotion to add the captions & cut!

BOOTOSHI 👑

14,107 Aufrufe • vor 8 Monaten

Claude Code creator: "Loops are as big a step as move from source code to agents. Loops - step from agents to the next thing. 30% of my code is fully written by loops right now." in a 40-minute fireside chat, Boris Cherny reveals his actual working setup. Loops + dynamic workflows + routines, and more. Watch the full episode, then read the article on loop engineering below.
41:12

Claude Code creator: "Loops are as big a step as move from source code to agents. Loops - step from agents to the next thing. 30% of my code is fully written by loops right now." in a 40-minute fireside chat, Boris Cherny reveals his actual working setup. Loops + dynamic workflows + routines, and more. Watch the full episode, then read the article on loop engineering below.

Movez

379,160 Aufrufe • vor 3 Monaten

Claude Code creator: "I don't prompt Claude anymore. I have loops that figure out what to do. My job is to create loops." in 30 minutes Boris breaks down his daily Claude Code setup, step by step the person who built the tool doesn't use it the way most people think no prompts, no chat box, just loops running on their own I broke down 17 Claude features most people have never found full guide in the post below
29:49

Claude Code creator: "I don't prompt Claude anymore. I have loops that figure out what to do. My job is to create loops." in 30 minutes Boris breaks down his daily Claude Code setup, step by step the person who built the tool doesn't use it the way most people think no prompts, no chat box, just loops running on their own I broke down 17 Claude features most people have never found full guide in the post below

Anatoli Kopadze

412,931 Aufrufe • vor 3 Monaten

Boris Cherny (Claude Code creator): "I don't prompt Claude anymore... my job is to write loops." In his latest interview, he breaks down the setup step by step. He runs /loops + a dynamic workflow + a couple hundred agents that read his GitHub, Slack, and Twitter and decide what to build next. His only job now is writing the loops that orchestrate them. That's a multi-agent workflow. I broke down how to build your own below ↓
4:07

Boris Cherny (Claude Code creator): "I don't prompt Claude anymore... my job is to write loops." In his latest interview, he breaks down the setup step by step. He runs /loops + a dynamic workflow + a couple hundred agents that read his GitHub, Slack, and Twitter and decide what to build next. His only job now is writing the loops that orchestrate them. That's a multi-agent workflow. I broke down how to build your own below ↓

Avid

26,996 Aufrufe • vor 3 Monaten

Claude Code creator: “100% of my code has been written by Claude since Opus 4.5. most of my coding routine is automated by loops & dynamic workflows" In this 40-minute video, Boris shares how to build a self-improving agentic setup from scratch. Loops + dynamic workflows + auto mode + routines - that’s the secret. Worth more than a $500 vibe-coding course. Watch today, then read below to learn how to build the same workflow.
40:41

Claude Code creator: “100% of my code has been written by Claude since Opus 4.5. most of my coding routine is automated by loops & dynamic workflows" In this 40-minute video, Boris shares how to build a self-improving agentic setup from scratch. Loops + dynamic workflows + auto mode + routines - that’s the secret. Worth more than a $500 vibe-coding course. Watch today, then read below to learn how to build the same workflow.

Codez

119,345 Aufrufe • vor 3 Monaten

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
17:28

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 Aufrufe • vor 3 Monaten

MOST PEOPLE USING CLAUDE CODE ARE LEAVING 90% OF ITS DESIGN SKILLS ON THE TABLE Same Claude. Same model. Completely different results. Out of the box, Claude Code builds websites that look… fine. Clean. Functional. Forgettable. But give it the right web-design skills and suddenly it starts building pages that look like a $5,000 agency made them. And here’s the crazy part: Those skills are completely FREE. They’re sitting on GitHub right now, and almost nobody is using them. I found the exact setup that turns Claude Code from an average website builder into a serious design machine. The skills + workflow are in the article below. Once you install them, going back to default Claude feels broken.
0:24

MOST PEOPLE USING CLAUDE CODE ARE LEAVING 90% OF ITS DESIGN SKILLS ON THE TABLE Same Claude. Same model. Completely different results. Out of the box, Claude Code builds websites that look… fine. Clean. Functional. Forgettable. But give it the right web-design skills and suddenly it starts building pages that look like a $5,000 agency made them. And here’s the crazy part: Those skills are completely FREE. They’re sitting on GitHub right now, and almost nobody is using them. I found the exact setup that turns Claude Code from an average website builder into a serious design machine. The skills + workflow are in the article below. Once you install them, going back to default Claude feels broken.

Romario

65,986 Aufrufe • vor 1 Monat

Anthropic is starting to ban Pro/Max accounts for using OpenClaw. Don’t risk your main account. 🛑 I’ve been running OpenClaw + Claude Code through the MiniMax M2.5 provider for $20/month. It’s "unlimited" for dev work and completely bypasses the ban wave since you’re using a dedicated API gateway. The setup: - Get the $10/$20 Coding Plan at - Grab the API key from the "Direct Account" sidebar. - Update your settings.json (Windows) or .zshrc (Mac) with the MiniMax endpoint. Claude Code (Windows): Go to ~/username/.claude/settings.json Paste your API key into this JSON: { "env": { "ANTHROPIC_BASE_URL": " "ANTHROPIC_AUTH_TOKEN": " ", "API_TIMEOUT_MS": "3000000", "CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC": 1, "ANTHROPIC_MODEL": "MiniMax-M2.5", "ANTHROPIC_SMALL_FAST_MODEL": "MiniMax-M2.5", "ANTHROPIC_DEFAULT_SONNET_MODEL": "MiniMax-M2.5", "ANTHROPIC_DEFAULT_OPUS_MODEL": "MiniMax-M2.5", "ANTHROPIC_DEFAULT_HAIKU_MODEL": "MiniMax-M2.5" } } Claude Code (macOS): In ~/.zshrc add: export MINIMAX_API_KEY="your_minimax_api_key_here" export ANTHROPIC_BASE_URL=" export ANTHROPIC_AUTH_TOKEN="$MINIMAX_API_KEY" export ANTHROPIC_MODEL="MiniMax-M2.5" Config details in the video. 👇
1:28

Anthropic is starting to ban Pro/Max accounts for using OpenClaw. Don’t risk your main account. 🛑 I’ve been running OpenClaw + Claude Code through the MiniMax M2.5 provider for $20/month. It’s "unlimited" for dev work and completely bypasses the ban wave since you’re using a dedicated API gateway. The setup: - Get the $10/$20 Coding Plan at - Grab the API key from the "Direct Account" sidebar. - Update your settings.json (Windows) or .zshrc (Mac) with the MiniMax endpoint. Claude Code (Windows): Go to ~/username/.claude/settings.json Paste your API key into this JSON: { "env": { "ANTHROPIC_BASE_URL": " "ANTHROPIC_AUTH_TOKEN": " ", "API_TIMEOUT_MS": "3000000", "CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC": 1, "ANTHROPIC_MODEL": "MiniMax-M2.5", "ANTHROPIC_SMALL_FAST_MODEL": "MiniMax-M2.5", "ANTHROPIC_DEFAULT_SONNET_MODEL": "MiniMax-M2.5", "ANTHROPIC_DEFAULT_OPUS_MODEL": "MiniMax-M2.5", "ANTHROPIC_DEFAULT_HAIKU_MODEL": "MiniMax-M2.5" } } Claude Code (macOS): In ~/.zshrc add: export MINIMAX_API_KEY="your_minimax_api_key_here" export ANTHROPIC_BASE_URL=" export ANTHROPIC_AUTH_TOKEN="$MINIMAX_API_KEY" export ANTHROPIC_MODEL="MiniMax-M2.5" Config details in the video. 👇

Ziwen

108,639 Aufrufe • vor 7 Monaten

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 ↓
16:33

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 Aufrufe • vor 4 Monaten

WHAT?!? 🤯 I asked Claude to build me an all in one AI Operating System for working with Claude Code. An hour later here we are... → Full ability to chat with Claude Code → Markdown file browser/editor built right in I've been using VS Code but there is a lot that I just don't need. I'm a knowledge worker, not a developer. So I guess I just built an IDE for knowledge workers? Now we're building: → Voice Mode (ability to switch to voice conversations) → Cron Job Management - so I can manage all the automated processes we have running → Ability to switch to different agents (currently I just have one... my AI Cos, Chad)
0:22

WHAT?!? 🤯 I asked Claude to build me an all in one AI Operating System for working with Claude Code. An hour later here we are... → Full ability to chat with Claude Code → Markdown file browser/editor built right in I've been using VS Code but there is a lot that I just don't need. I'm a knowledge worker, not a developer. So I guess I just built an IDE for knowledge workers? Now we're building: → Voice Mode (ability to switch to voice conversations) → Cron Job Management - so I can manage all the automated processes we have running → Ability to switch to different agents (currently I just have one... my AI Cos, Chad)

⚡️ Ev Chapman 🚢 | Creative Entrepreneur

38,577 Aufrufe • vor 6 Monaten

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 ↳ /config, output style, concise I ran one real job through all three, four terminals arguing with each other, and filmed the whole thing. My free Claude Code guide, 10 minutes and you'll know 80% of it → Repost ♻️ to help someone in your network.
11:22

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 ↳ /config, output style, concise I ran one real job through all three, four terminals arguing with each other, and filmed the whole thing. My free Claude Code guide, 10 minutes and you'll know 80% of it → Repost ♻️ to help someone in your network.

Charlie Hills

23,395 Aufrufe • vor 1 Monat

A 26-YEAR-OLD AI ENGINEER WHOSE BIRMINGHAM THESIS OUTPERFORMED GOOGLE SCHOLAR BY 50% JUST SHIPPED GRAPHIFY: ONE COMMAND TURNS ANY FOLDER INTO A CLAUDE CODE SECOND BRAIN Safi Shamsi built Graphify 48 hours after Karpathy posted his LLM wiki idea. It turns any folder, codebase, docs, PDFs, into a knowledge graph Claude reads instead of grepping. Up to 43x fewer tokens per query. The trick almost nobody is using yet: one flag exports the entire graph as a fully-linked Obsidian vault. Repo: /safishamsi/graphify Setup, end to end: 1. Install: uv tool install graphifyy (or pipx install graphifyy). Verify with graphify --version. 2. Install the skill in Claude Code: graphify claude install. This wires Graphify into Claude Code so you can call it as a skill. 3. Open the folder you want mapped in Claude Code. In the terminal: graphify . It extracts every concept and builds the graph in graphify-out/. 4. Export to Obsidian: graphify . --obsidian. Writes one note per concept, every relationship as a wikilink, every node linked back to its source. 5. Open the new vault in Obsidian (Manage vaults → Open folder as a vault), or drag it as a subfolder into your existing one. That's it. Your Claude Code instance now has a navigable map of the codebase that loads instantly instead of re-reading files every session. Full step-by-step build of the Claude + Obsidian second brain in the article below. Bookmark this
16:36

A 26-YEAR-OLD AI ENGINEER WHOSE BIRMINGHAM THESIS OUTPERFORMED GOOGLE SCHOLAR BY 50% JUST SHIPPED GRAPHIFY: ONE COMMAND TURNS ANY FOLDER INTO A CLAUDE CODE SECOND BRAIN Safi Shamsi built Graphify 48 hours after Karpathy posted his LLM wiki idea. It turns any folder, codebase, docs, PDFs, into a knowledge graph Claude reads instead of grepping. Up to 43x fewer tokens per query. The trick almost nobody is using yet: one flag exports the entire graph as a fully-linked Obsidian vault. Repo: /safishamsi/graphify Setup, end to end: 1. Install: uv tool install graphifyy (or pipx install graphifyy). Verify with graphify --version. 2. Install the skill in Claude Code: graphify claude install. This wires Graphify into Claude Code so you can call it as a skill. 3. Open the folder you want mapped in Claude Code. In the terminal: graphify . It extracts every concept and builds the graph in graphify-out/. 4. Export to Obsidian: graphify . --obsidian. Writes one note per concept, every relationship as a wikilink, every node linked back to its source. 5. Open the new vault in Obsidian (Manage vaults → Open folder as a vault), or drag it as a subfolder into your existing one. That's it. Your Claude Code instance now has a navigable map of the codebase that loads instantly instead of re-reading files every session. Full step-by-step build of the Claude + Obsidian second brain in the article below. Bookmark this

Yarchi

141,580 Aufrufe • vor 3 Monaten

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.
55:30

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,199 Aufrufe • vor 2 Monaten

Most AI brainstorming sessions end the exact same way: You have 2,000 words of brilliant ideas trapped in a chat window. Then you spend the next two hours turning those raw notes into a deck your team can actually look at. I cut that entire second half out of my workflow using Claude + Gamma. 🧵
0:25

Most AI brainstorming sessions end the exact same way: You have 2,000 words of brilliant ideas trapped in a chat window. Then you spend the next two hours turning those raw notes into a deck your team can actually look at. I cut that entire second half out of my workflow using Claude + Gamma. 🧵

Hannah Brooks

129,685 Aufrufe • vor 1 Monat

Claude Code creator: "100% of our pull requests at Anrtopic are run by Claude Code. 80–90% of code review too. The feature I’m using the most today is /loops. I’m not prompting Claude anymore - I’m building loops" in this interview he breaks down exactly how a system changes everything: - the memory and context features that turn Claude into a second brain - the knowledge architecture most users don't know Claude can build - the integration layer that connects Claude to your actual workflow - why typing one question at a time is the most expensive way to use Claude if you've been using Claude for months and still start every conversation from scratch with zero context, you don't have a Claude problem. you have a system problem instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed full guide in the article below
50:12

Claude Code creator: "100% of our pull requests at Anrtopic are run by Claude Code. 80–90% of code review too. The feature I’m using the most today is /loops. I’m not prompting Claude anymore - I’m building loops" in this interview he breaks down exactly how a system changes everything: - the memory and context features that turn Claude into a second brain - the knowledge architecture most users don't know Claude can build - the integration layer that connects Claude to your actual workflow - why typing one question at a time is the most expensive way to use Claude if you've been using Claude for months and still start every conversation from scratch with zero context, you don't have a Claude problem. you have a system problem instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed full guide in the article below

Khairallah AL-Awady

39,292 Aufrufe • vor 3 Monaten

I sat down with matt van horn (Matt Van Horn) and watched him turn claude code into a real-time research engine with his /last30days claude code skill he "fixes" claude code in 30 seconds. this skill pulls what’s actually working right now from x, reddit, and the web, then feeds that context straight into your prompts so you stop building off stale advice. we went from trending rap songs → cold email frameworks → researching clawdbot → planning and building a competitor live, with almost zero hand-written code. pretty nifty little claude code skill share this with a friend / full ep available on The Startup Ideas Podcast (SIP) 🧃 where i will give you ideas/tools/tutorials to make your dreams a reality i will not hold back any alpha and this claude skill is alpha forsure you can install this claude code skill in 30 seconds dream big my friends
25:21

I sat down with matt van horn (Matt Van Horn) and watched him turn claude code into a real-time research engine with his /last30days claude code skill he "fixes" claude code in 30 seconds. this skill pulls what’s actually working right now from x, reddit, and the web, then feeds that context straight into your prompts so you stop building off stale advice. we went from trending rap songs → cold email frameworks → researching clawdbot → planning and building a competitor live, with almost zero hand-written code. pretty nifty little claude code skill share this with a friend / full ep available on The Startup Ideas Podcast (SIP) 🧃 where i will give you ideas/tools/tutorials to make your dreams a reality i will not hold back any alpha and this claude skill is alpha forsure you can install this claude code skill in 30 seconds dream big my friends

GREG ISENBERG

177,179 Aufrufe • vor 7 Monaten

everyone's talking about building a second brain with claude code + obsidian right now. so i made a full video walkthrough showing exactly how to set it up from scratch. drop an article into a folder. claude code reads it, creates wiki pages, builds relationships between concepts, and links everything automatically. by 20 sources your wiki knows more about your domain than you can hold in your head. here's the full setup:
13:22

everyone's talking about building a second brain with claude code + obsidian right now. so i made a full video walkthrough showing exactly how to set it up from scratch. drop an article into a folder. claude code reads it, creates wiki pages, builds relationships between concepts, and links everything automatically. by 20 sources your wiki knows more about your domain than you can hold in your head. here's the full setup:

J.B.

55,133 Aufrufe • vor 5 Monaten

Claude Code tip: once Opus 5.5 is your main model, stop leaving Fable 5.1 sitting idle put it on call with /advisor run /advisor fable Opus 5.5 keeps writing the code Fable 5.1 reads the full session, every tool call included, and only speaks up at three points: → before a plan: is this the right approach? → when the same error comes back: am I digging in the wrong place? → before "done": what did I miss? Fable 5.1 reviews. Opus 5.5 ships Jev engineering is the same move one layer down: the forks that need no thinker (which file, which tool, retry or stop) go to Jev in under half a second, and the big model only sees the ones that split - the full tree > Opus 5.5 on high runs the main session > explorer reads the code > worker edits and runs tests > researcher pulls the docs > all three on medium > Fable 5.1 on call as the advisor paste the tree and this prompt into Claude Code ↓ "Rebuild my Claude Code setup around this tree: 1. Check ~/.claude/agents and .claude/agents for subagents that already fit explorer, worker and researcher. > Draft new ones only for missing roles > Give each model: opus, effort: medium > Skip any that pin a different model and list them 2. Set the main session to high via effortLevel in ~/.claude/settings.json, and set advisorModel to fable 3. Find anything that keeps the advisor off (CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY, any variable that stops feature-flag fetching) plus CLAUDE_CODE_EFFORT_LEVEL, which overrides subagent effort. Report them, change nothing 4. Add one rule to ~/.claude/CLAUDE.md: consult the advisor before a large plan, when an error repeats, and before calling a long task done Show me every change as a diff first. No edits until I say go." ↳
0:31

Claude Code tip: once Opus 5.5 is your main model, stop leaving Fable 5.1 sitting idle put it on call with /advisor run /advisor fable Opus 5.5 keeps writing the code Fable 5.1 reads the full session, every tool call included, and only speaks up at three points: → before a plan: is this the right approach? → when the same error comes back: am I digging in the wrong place? → before "done": what did I miss? Fable 5.1 reviews. Opus 5.5 ships Jev engineering is the same move one layer down: the forks that need no thinker (which file, which tool, retry or stop) go to Jev in under half a second, and the big model only sees the ones that split - the full tree > Opus 5.5 on high runs the main session > explorer reads the code > worker edits and runs tests > researcher pulls the docs > all three on medium > Fable 5.1 on call as the advisor paste the tree and this prompt into Claude Code ↓ "Rebuild my Claude Code setup around this tree: 1. Check ~/.claude/agents and .claude/agents for subagents that already fit explorer, worker and researcher. > Draft new ones only for missing roles > Give each model: opus, effort: medium > Skip any that pin a different model and list them 2. Set the main session to high via effortLevel in ~/.claude/settings.json, and set advisorModel to fable 3. Find anything that keeps the advisor off (CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY, any variable that stops feature-flag fetching) plus CLAUDE_CODE_EFFORT_LEVEL, which overrides subagent effort. Report them, change nothing 4. Add one rule to ~/.claude/CLAUDE.md: consult the advisor before a large plan, when an error repeats, and before calling a long task done Show me every change as a diff first. No edits until I say go." ↳

delost

677,973 Aufrufe • vor 2 Tagen

A Google Cloud engineer just showed how to build a full app with Claude from scratch he spent 26 minutes live on stage doing what most teams take weeks to do worth more than any $500 vibe-coding course here's what he covers: > zero to deployed app in a single session > handling five engineering roles alone with Claude > the exact workflow Google uses internally > no team, no setup, just Claude and a goal the people who figure out what Claude can actually do are building things everyone else thinks requires a team that's exactly why I wrote a step by step guide on how to build your first AI agent the guide is in the article below
26:23

A Google Cloud engineer just showed how to build a full app with Claude from scratch he spent 26 minutes live on stage doing what most teams take weeks to do worth more than any $500 vibe-coding course here's what he covers: > zero to deployed app in a single session > handling five engineering roles alone with Claude > the exact workflow Google uses internally > no team, no setup, just Claude and a goal the people who figure out what Claude can actually do are building things everyone else thinks requires a team that's exactly why I wrote a step by step guide on how to build your first AI agent the guide is in the article below

Anatoli Kopadze

464,328 Aufrufe • vor 3 Monaten

i merged all my AI agents into one brain Claude Code, Codex, Gemini: one team, one memory, zero re-briefing result: 8+ hours a week back, and every agent already knows my projects, my clients and how i think here's the setup with Jarvix: 1. dump your context once: projects, clients, writing style, how you make decisions.. it builds your personal model from your actual AI interactions 2. switch agents mid-task with zero re-briefing: Claude Code builds, Codex reviews, Gemini researches, all reading the same context 3. it carries what YOU choose across sessions.. never start a chat from zero again 4. when it's time to act, it pulls the right agents together as one team instead of five separate assistants the unlock isn't another agent. it's that your context finally travels agents without shared memory are five interns on their first day, forever. agents with it are a team that's worked with you for years not more agents. one shared context that's the right bet P.S. thanks to the Jarvix team for the early access
2:15

i merged all my AI agents into one brain Claude Code, Codex, Gemini: one team, one memory, zero re-briefing result: 8+ hours a week back, and every agent already knows my projects, my clients and how i think here's the setup with Jarvix: 1. dump your context once: projects, clients, writing style, how you make decisions.. it builds your personal model from your actual AI interactions 2. switch agents mid-task with zero re-briefing: Claude Code builds, Codex reviews, Gemini researches, all reading the same context 3. it carries what YOU choose across sessions.. never start a chat from zero again 4. when it's time to act, it pulls the right agents together as one team instead of five separate assistants the unlock isn't another agent. it's that your context finally travels agents without shared memory are five interns on their first day, forever. agents with it are a team that's worked with you for years not more agents. one shared context that's the right bet P.S. thanks to the Jarvix team for the early access

Ronin

15,071 Aufrufe • vor 1 Monat