Claude Code New Features, Explained
Get Claude Code: https://startup-ideas-pod.link/claude-greg In this solo episode I lay out the exact system I use to turn Claude Code into what I call an AI employee. My premise is simple: give Claude the same things you would give a person joining your company (a workspace, memory, a brief, a clear ticket, eyes, review, a schedule, and permissions). I build the whole setup live around a real idea I found on ideabrowser.com, a missed-lead responder for med spas, and I share the specific prompts I use at each step. By the end, the product, the customer feedback, the docs, the demos, the reviews, and the recurring work all live inside one operating loop. I close with a seven-day plan you can run at your own pace. And a special thank you to Claude and Anthropic for supporting the podcast. Setup Claude Code to be your 24/7 employee: https://startup-ideas-pod.link/Claude-code Timestamps 00:00 – Intro: The AI Employee Map 05:47 – Step 1: Creating The Workspace In Claude Desktop 14:53 – Step 2: The Brief And Plan Mode 18:08 – Step 3: The Ticket And Defining Done 22:15 – Step 4: The Eyes And Desktop Preview 26:13 – Step 5: Review In Layers And The Diff View 29:34 – Step 6: The Schedule And Routines 34:32 – Step 7: Parallel Agents And Worktree Isolation 39:14 – Step 8: Permissions: Safe, Ask First, Human-Owned 41:15 – Step 9: Skills, Connectors, And Hooks 44:28 – The Seven-Day Plan 47:42 – Closing Thoughts Key Points • I treat Claude Code like a new hire: workspace, memory, brief, ticket, eyes, review, schedule, permissions. • The repo brain teaches Claude how I work and what good looks like. • Plan mode comes first: Claude reads the context, proposes an approach, and waits for my approval. • One ticket at a time means one task, one finish line, and one reviewable change. • The eyes matter: Claude opens the app in desktop preview, clicks the flow, checks the console, and reports what a buyer experiences. • Routines and permissions turn a chat tool into a 24/7 operator with clear boundaries. The #1 tool to find startup ideas/trends - https://www.ideabrowser.com LCA helps Fortune 500s and fast-growing startups build their future - from Warner Music to Fortnite to Dropbox. We turn 'what if' into reality with AI, apps, and next-gen products https://latecheckout.agency/ The Vibe Marketer - Resources for people into vibe marketing/marketing with AI: https://www.thevibemarketer.com/ FIND ME ON SOCIAL X/Twitter: https://twitter.com/gregisenberg Instagram: https://instagram.com/gregisenberg/ LinkedIn: https://www.linkedin.com/in/gisenberg/
Read Video · Transkript & Insights
Diese Folge hat ein vollständiges Transkript + KI-Insights
Kostenloses Konto · keine Karte nötig · 150 Credits nach Registrierung, genug für diese Episode
- 📄 Vollständiges Transkript mit Zeitstempeln
- ✨ KI-Zusammenfassung, Keywords & Mindmap
- 💡 Kernaussagen & Zitate
Episoden-Zeitlinie
Introduction: most people use Claude Code wrong, and the fix is setting it up like an AI employee.
- Claude Code is described as one of the most powerful pieces of technology ever created, but most people misuse it because they never set it up properly.
- The host promises to reveal nine areas to master so Claude Code can spin up AI employees that work 24/7 and build AI-native companies.
- All prompts and 'sauce' are given away free in the episode, sponsored by Anthropic.
The map of an AI employee: workspace, memory, brief, ticket, eyes, review, schedule, and permissions.
- An AI employee needs the same basics as a human hire: a workspace (repo), memory (project context), a brief (plan mode), and a clear ticket.
- Vague prompts like 'make the app better' fail; specific tickets like 'add a waitlist form with a success state and check it in desktop preview' work far better.
- Claude Code now has 'eyes' — it can open the app, click through flows, and report what a customer would actually experience.
- Review, schedule (routines), and permissions complete the map, with humans owning trust decisions like dependencies, migrations, and payments.
Step one: creating the workspace and repo structure for a med spa missed-lead responder idea.
- The demo idea from ideabrows.com is a missed-lead responder for med spas, where inbound leads go cold because the business replies too late.
- The recommended repo structure is /app, /context, /customers, /spec, /demo, /routines plus three root markdown files: claude.md, roadmap.md, and review.md.
- A single setup prompt tells Claude the product, buyer, pain, promise, and goal, and asks it to request any missing context before writing.
- Claude asks high-leverage questions first, then scaffolds the entire optimized workspace automatically.
Schlüsselkonzepte
- Claude Code— The core tool being taught throughout the episode as a platform for building AI employees.
- AI employee— The central metaphor and goal — configuring Claude Code to work like a full-time staff member.
- workspace repo— The first pillar: a structured repository where the product and context live.
Bemerkenswerte Zitate
I think there's a lot of people using claude code wrong. And they're using claude code wrong because it is one of the most powerful pieces of technology that have ever existed.
🔥— It asserts that most users are misusing a tool they think they already understand, setting up the entire reframe of the episode.
The mistake a lot of people make is they'll say, "Make the app better. Make this pop." These very vague prompts uh that are assigned to it.
💡— It names the exact habit most users have and shows why it forces Claude to guess instead of execute.
Konkrete Handlungen
🗂️Workspace Setup
Claude becomes far more useful when the project explains itself through structured files and folders.
This week, create CLAUDE.md, roadmap.md, and review.md in your project root and populate each with business context, current goals, and quality standards.
A repo organized into /context, /customers, /spec, /demo, and /routines gives Claude a place to work and a brain to think with.
Create those five folders today and drop at least one real customer note and one demo script into them.
📋Planning and Execution
Plan mode forces Claude to inspect context and propose an approach before touching any files.
On your next task, prompt Claude to use plan mode, list files to change, risks, and verification steps, then wait for your approval before editing.
Vague tickets like 'make the app better' force Claude to guess, which turns you into a cleanup crew instead of a manager.
Rewrite your next three prompts to include one task, one finish line, and one reviewable change.
Transkript und Insights werden KI-generiert und können Fehler enthalten. Die Genauigkeit hängt von der Audioqualität und der Deutlichkeit der Sprecher ab — bei Unklarheiten ist das Originalaudio die maßgebliche Quelle.
Episoden und Videos zum Lesen
Podcast-Episoden
The missing half of music history | Gabriella Di Laccio
TED Talks Daily
3. Sept. 202610:29EN
(Preview) Microsoft’s Plan for Platform Survival, Meta and the Market’s Permission, A Lack of Situational Awareness
Sharp Tech with Ben Thompson
6. Aug. 202628:47EN
The Multidisciplinary Approach to Thinking | Peter D. Kaufman [Outliers]
The Knowledge Project
13. Jan. 202626:04EN
#8 Die Völkerwanderung - Völker...? Wanderung...?
Wer wir sind und warum das nicht klappte ...
28. Mai 202539:45DE
商业小样45 | 厄尔尼诺越大，鱼越贵
商业就是这样
12. Juli 202611:34ZH
Paradigma Sosiologi (Versi George Ritzer) (Anchor: @Syaifudinsosio)
SOSIOLOGI KOPI
16. Sept. 202056:42ID
Videos
Staphylococcus: Aureus, Epidermidis, Saprophyticus
Ninja Nerd
21. Okt. 20211:01:18EN
AI Insider: Things Are About to Get Much Worse
The Jordan Harbinger Show
1. Sept. 20261:10:13EN
Give Me 12 Minutes and I’ll Give You 30 Years of Productivity Advice
Daniel Pink
14. Sept. 202511:59EN
#32 Die Schlacht von Worringen - Der Freiheitskampf der Kölner
99 mal Geschichte
12. Nov. 202553:29DE
COMO SER GENTIL ESTÁ ACABANDO COM A SUA AUTORIDADE? | Fabiana Bertotti #152
Como Você Fez Isso?
30. Juli 20261:19:47PT