Claude Code
First met in aicp-c3-basecamp-02 · Coding agents & editors
Claude CodeFirst met in aicp-c3-basecamp-02 · Coding agents & editors
Anthropic's terminal coding agent — it reads your repo, writes across files, runs commands, and iterates until the thing works.
The project has outgrown a vibe-coding platform and you want depth, repo awareness and parallel sessions — vs Cursor's editor-first feel or Codex's stronger back-end bias.
Clones and takes over an existing repo — the documented graduation path out of Lovable
Runs several sessions in parallel on different workstreams (the BC2 trainer's team runs 3-4)
MCP-aware, so connectors like Supabase or a filesystem make its work conversational
Edits code across a whole repository, not one file at a time
Runs builds, tests and shell commands and reads the output to fix itself
Takes over vibe-coded projects once they're pushed to GitHub
Hosts skills (.md files) that package reusable instructions
Doesn't come free — the trainer's team runs multiple $200 subscriptions
Doesn't design well from nothing — the vibe-coding platforms still win the first-draft look
Doesn't remove the need to review; it's fast enough to make big mistakes quickly
Everything after the MVP. The course's 'serious' local stack is Claude Code + Supabase + Vercel, with the vibe-coding platform used only to get started.
Coding agents & editors
This pipeline runs on the Claude agent stack — Cowork sittings with Desktop Commander are the same family of tool.
build_site.py, the extraction protocol and the whole _pipeline directory are the working proof; the course's advice about parallel sessions and repo takeover maps directly onto how sittings are structured.
current
cursor: local peer; Cursor is editor-first with its own fast model
codex: Codex's GPT-5.5 'extra high' beat it on n8n JSON in BC3 and on back-end work in BC4
lovable: clone the Lovable repo and continue here
claude-cowork: Cowork described in BC4 as 'a UI wrapper on Claude Code'
| Session | Coverage | Moment | What happened |
|---|---|---|---|
| Session 3: Building Elegant Landing Pages | demonstrated | 0:11:41 | Shown for contrast: chat/cowork/code surfaces confusing to beginners; lacks the in-app browser; his former $200 daily driver |
| Session 11: Overview of Claude Code & Key Concepts (Installs, Modes, Context Files, Skills, Hooks & MCPs) | demonstrated | 0:12:37 | All three installs, modes, effort slider, commands, context files, skills folder, connectors — the full orientation |
| Session 12: Claude Code — Design & Building Agents (App-First: a Game, a GTM Board, and a Live Deploy) | demonstrated | 0:37:26 | Desktop app throughout — modes, plan comments, /init, /compact, context readout, plugins UI; terminal deliberately avoided |
| Session 13: Claude Code — Skills, Sub Agents & the Token Economy (posted as 'Beyond Vibe Coding — n8n & More') | demonstrated | 0:09:47 | Terminal on macOS; Opus 4.8 orchestrator, 1M context; /context, /usage, /skills; sub agents and skills created conversationally |
| Session 14: Claude Code — Advanced Workflows | demonstrated | 0:11:24 | All three interfaces shown; terminal is the session's home — plan mode, effort, sub agents, /goal, /btw, /usage |
| Session 15: Loop, Harness & Graph Engineering (posted as 'Securing Vibe-Coded Apps') | demonstrated | 0:52:19 | The session's engine: /goal runs, hidden-test loop, auto mode + /remote-control from the phone, /agents view, plugins (his Forge, superpowers, NEM), custom /run-lab command pattern |
| Session 24: Building a Marketing OS — Sector-Agnostic Command Center on an Open-Source Stack | demonstrated | Opus 5 attempt — rogue Playwright, bad output, retired via handover document; enterprise-adoption color kept | |
| AI Sprint: Claude Code with Antigravity — Day 1 (Taste as the Moat, the Muscle-and-Mirror Setup, and the Model Council Build) | demonstrated | Terminal-first agent; /login /usage /model drilled; Opus-for-planning rationing; the mid-session outage and recovery | |
| AI Sprint: Claude Code with Antigravity — Day 2 (CLAUDE.md, the 50% Context Rule, and the Sketch-to-App Build) | demonstrated | The full advanced setup: CLAUDE.md/memory.md, superpowers + UI UX Pro Max orchestration, sub-agents, --dangerously-skip-permissions, live token metering | |
| AI Masterclass: Exploring Antigravity 2 — Four Products, Four Slash Commands, and Two Live Builds | demonstrated | The constant comparison object — opened live in terminal; 'plan with Claude, build with Antigravity' | |
| AI Sprint: OpenClaw — Session 2 (Token Anatomy, Claude Code Inside the Server, Skills, and Multi-Agent Workspaces) | demonstrated | Installed INSIDE the server as the configuration translator — skills, fallbacks, gateway restarts by conversation; his Max subscription | |
| AI Sprint: Windsurf & Devin — Day 2 (Building Superplexity: Plan with Opus, Execute with Cascade, Review with Devin) | demonstrated | The planner: Opus + superpowers brainstorming/writing-plans; the four-usage-limit war story motivates the split | |
| Basecamp 2: Vibe Coding | explained | 2:38:04 | The post-MVP tool: trainer's team runs three $200 subscriptions, 3-4 parallel sessions (business/content/dev); can clone repos and take over Lovable projects |
| Session 2: How to Plan, Scope and Sell your AI Projects | explained | 2:19:07 | His heavy daily pair (via cmux terminal); Claude for proposals/websites/diagrams; Codex recommended as the cheaper rate-limit relief; 'Claude Code is going to be the best thing ever' for most learners |
| AI Sprint: The Hermes Agent — Day 1 (Always-On Agents, the Employee-on-Day-One System, and the Self-Improving Ghostwriter) | explained | Declared interchangeable throughout; the supervised lane alongside Codex; md-file handoffs relieve token exhaustion | |
| Basecamp 6: Voice Agents | mentioned | 0:43:33 | His agency's homegrown call-transcript analysis pipeline, pre-dating Retell's AI quality assurance feature |
| Session 9: Introduction to Cursor & its principles | mentioned | 0:37:46 | This month's fallback to Codex; sandboxed architecture explained; 'use terminal Claude Code, not Claude chat' |
| Session 17: Facebook Ads Competitor Research & Replication | mentioned | 0:50:47 | The CLI alternative discussed in the why-a-workflow Q&A (ASR renders it 'cloud code'); prior sessions' tool, contrasted with n8n's product shape |
| Session 19: Content Strategy Pipeline — the YouTube Growth Stack, Built by an Agent Team of Chats | mentioned | 'Everything can be done on Claude Code as well — nothing here is unique to a vendor' | |
| Session 20: Complete LinkedIn Agency Automation — Carousels + Newsletter from One Content System | mentioned | 'I really wish Claude Code had an interface like this' + the portability promise: swap it in tomorrow via the folder | |
| Session 22: Automate Admin Tasks — Advanced RAG (Enterprise 'Internal Perplexity' Built Live) | mentioned | 'The model is amazing... it's just the UI' — his Codex preference explained to Paul as ergonomics, not capability | |
| Session 23: Automating AEO/GEO — Audits, the File Layer, and Evidence-Led AI Search | mentioned | 'Codex or Claude — you can use any of these tools'; Rajesh's GEO skill targets it | |
| Beginner Glossary (30 terms) + I'm Stuck Guides (23) | mentioned | Same guide's coding-agent side: deeper control, more responsibility | |
| Learning Topics: Sessions 1–5 — Foundations to AI Director | mentioned | Tier-three agentic builder, with Codex — version control and permission discipline as prerequisites | |
| AI Sprint: The Hermes Agent — Day 2 (Loop Engineering: the Scheduling Loop, the Delegation Loop, and the Skill Auditor) | mentioned | The goal-style command with a separate evaluator model (as-heard 'GOLD') — the loop-native industry signal | |
| AI Sprint: OpenClaw — Session 1 (Infrastructure, Not Agent: the Seven Documents, 1-Click VPS, and Model Routing) | mentioned | His editing surface for live server changes — always prefixed 'don't touch soul.md' | |
| AI Sprint: The Open Source Playbook — Day 2 (Weights 101, OpenCode, and the Subsidy Math) | mentioned | The comparison baseline throughout — cleaner harness, better sub-agent visibility; 50% of his daily work | |
| AI Sprint: AI Evals & Reliability — Day 2 (Testing Systems That Never Answer Twice) | mentioned | One of two tools used to build the new certificate generator | |
| AI Sprint: Windsurf & Devin — Day 1 (Vibe to Agentic: GitHub as Pizza, the Four Spec Concerns, and the IDE Lineage) | mentioned | Prior sprint referenced; Opus available in Windsurf only via BYO API key |