Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Ghostty + Claude Code + Vercel statusline + Neon statusline + Lazygit How are you handling multitasking when running multiple agents? Right now it’s just two across different projects, but sometimes it’s three per project using separate worktrees.

81,166 Aufrufe • vor 5 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Claude Code + Google Stitch 2.0 is f*cking cracked 🤯 Google just dropped a free AI design agent that solves Claude Code's biggest weakness: frontend design. One screenshot of a high-converting landing page → a production-ready site for your brand in minutes. All inside Google Stitch + Claude Code. Perfect for DTC brands and agencies who are building advertorial pages and product launch pages for Meta but burning days on designer back-and-forth. If you're running Meta ads and need 5-10 different landing pages testing different hooks, angles, and offers — each one targeting a different audience and pain point — you know the bottleneck isn't the ads. It's the pages. Briefing designers, waiting for revisions, paying $2-5K per page. Stitch eliminates the design bottleneck: → Find a high-converting advertorial that's scaling on Meta → Screenshot it and drop it into Stitch (powered by Gemini 3.1) → Stitch redesigns it with your brand's colors, fonts, and imagery using Nano Banana 2 → Edit sections visually — headlines, CTAs, layouts — without touching code → Export the code and paste it into Claude Code → Claude builds the full production site and deploys to Vercel or Netlify in 60 seconds No designer. No $3K per landing page. No Claude Code frontend that looks like a template from 2019. What you get: → Designer-quality landing pages and advertorials built in minutes, not weeks → Visual editing so you actually see the design before you code it → Nano Banana 2 generating on-brand product imagery and hero shots → A repeatable system — new angle, new page, same pipeline Built 100% with Google Stitch 2.0 + Claude Code. I put together a full playbook showing the exact workflow: how to find winning pages, redesign them in Stitch, and deploy with Claude Code. Want it for free? > Like this post > Comment "STITCH" And I'll send it over (must be following so I can DM)

Mike Futia

125,639 Aufrufe • vor 3 Monaten

Claude Code Agent Teams are f*cking ridiculous 🤯 One prompt → a team lead breaks your project into pieces, spins up multiple AI agents, and they all work on different parts simultaneously. Research, builds, reviews, and debugging: all happening at the same time. All inside Claude Code. If you're running complex projects where every step waits on the last one... Agent teams eliminate the entire bottleneck: → Tell Claude what you need and describe the team structure in plain English → A lead agent breaks the work into a shared task list → It spawns 3-5 teammates — each with their own context and workspace → Teammates research, build, test, and review in parallel → They message each other, share findings, and challenge each other's work → The lead synthesizes everything into a finished deliverable No managing agents yourself. No waiting for step 1 to finish before step 2 starts. No single-lens reviews that miss half the issues. What you get: → Competitive research across 5 brands done in minutes instead of hours → Multi-component builds where frontend, backend, and data layers happen simultaneously → Creative reviews from 3 different angles at once — brand voice, conversion, differentiation → Funnel debugging where 4 agents investigate 4 theories and debate until they find the real answer Built 100% in Claude Code with one settings change. I put together a full DTC playbook: 5 workflows with copy-paste prompts, the exact setup process, token management tips, and honest guidance on when agent teams are worth it vs. when a simpler approach is the better move. Want it for free? > Like this post > Comment "AGENTS" And I'll send it over (must be following so I can DM)

Mike Futia

46,389 Aufrufe • vor 4 Monaten

What would you have done? Merge right and let it play out? Hold your ground? Exactly what a Preventable Crash Really Looks Like. You’re driving a semi. Three-lane highway. You're in the center lane. Left lane is ending. Right lane is completely empty. Convex mirror shows no one beside you on the right. Three cars are pacing you in the left lane… and they’re about to run out of road. So Why are you still in the center lane? You’re not boxed in. You’re not blind. And you’ve already seen the sign telling you the left lane ends. You could’ve merged right a half-mile ago and cruised on. Instead, you’re now stuck in the lane of most resistance. That car flying up on your left? It’s doing what 80% of cars do when the lane end, they punch it. They try to get ahead. Not smart. Not courteous. But absolutely predictable. And that’s the point. You’re the professional. They're not. You know how this goes. You should know exactly what to expect. Textbook behavior. So when that car forces a merge in front of your bumper with 20 feet left of asphalt, are they wrong? Yep. But when you don’t lift off the gas, don’t merge right, and don’t anticipate what’s clearly unfolding, that’s no longer just their problem. Now it’s yours. And it’s preventable. What happens next👇 ✅ You plow into the car. ✅ You get to sit roadside for 3 hours explaining it to law enforcement and doing paperwork. ✅ You spend another 3 months Data Q’ing it, defending it in court, or arguing it with claims adjusters. ✅ It’s on your CSA now. ✅ Your insurance premium goes up. ✅ The carrier eats the deductible. ✅ And you get labeled as someone who “could’ve avoided it but didn’t.” Being a truck driver isn’t just turning a wheel. It’s a chess match. It’s anticipating the next three moves. When you choose not to play defense, you’re the one who loses, even when you’re “not at fault.” Some stats to chew on👇 👉Lane change/merge crashes account for nearly 10% of all large truck crashes. 👉FMCSA's Large Truck Crash Causation Study consistently shows "decision error" and "recognition error" as top contributing factors in preventable crashes. 👉The average post-crash litigation process? 3–6 months minimum, and that’s before settlements, audits, or nuclear verdicts.

Rob Carpenter

16,777 Aufrufe • vor 5 Monaten

Introducing a new tool called "SideChannel". A secure alternative to OpenClaw. Utilizes signal for communication and has Claude integration. I built SideChannel, an open-source Signal bot that connects Claude AI to your entire development workflow. End-to-end encrypted. From your pocket. The real power is autonomous development. Send one message like "Build a REST API with auth, pagination, and tests" and SideChannel will: - Generate a full PRD with stories and atomic tasks. - Dispatch up to 10 parallel workers (each running Claude). - Independently verify every task with a separate Claude context. - Run quality gates to catch regressions - Auto-fix failures. - Send you progress updates via Signal as work completes. Every piece of code is reviewed by a separate AI context using a fail-closed security model. If it detects security issues, backdoors, or logic errors — the code gets rejected automatically. No rubber stamps. It also has memory that actually works. Conversations are stored with vector embeddings for semantic search. Claude remembers your project conventions, past decisions, and what's been tried before. It gets smarter about your codebase over time. Other things I'm proud of: - Plugin framework for extending with custom commands. - Multi-project support with per-user scoping. - Rate limiting, path validation, phone allowlist. - Git checkpoints before every task, atomic commits after. - Stale task recovery, circular dependency detection. - Works on Linux and macOS, one-command install. It also integrates into OpenAI or Grok (optional) for more Generative AI response for simple things like "Whats the weather in New York City right now?".

Dave Kennedy

49,427 Aufrufe • vor 4 Monaten