Claude Code for People Who Don't Code

The presenter opens by positioning this video as the resource he wished he had when starting with Claude as a non-coder professional. The content is split into two conceptual parts: first, demystifying the Claude ecosystem, and second, demonstrating practical Claude Code terminal usage.

On the ecosystem, the presenter maps out a hierarchy where Claude Code in the terminal is the most feature-rich base layer, with Claude Desktop, Claude Co-work, Claude Chat, and the Chrome extension each being progressively stripped-down versions. He argues that the further you move from the terminal, the fewer features you have access to — particularly around local folder access, which he considers the most important capability. Projects (static uploads) are available in Co-work and Chat, but local folder access — which enables dynamic, updatable context — is only available in Claude Code and Co-work. He strongly advocates for local folder context over static projects because Claude can read and update documents in real time, enabling persistent memory across sessions.

The presenter also covers GitHub repo integration for versioning, the Chrome extension (which can be invoked by Claude rather than used directly), mobile access via remote session linking, and the distinction between artifacts (ephemeral outputs in Claude Chat) versus files stored in a local folder (persistent and reusable). He notes that the terminal version has been stable for nearly a year while desktop/Co-work interfaces constantly break and change.

On scheduling and automation, he explains that Claude Co-work uses 'schedules,' Claude Desktop uses 'routines,' and the terminal uses both 'schedule' and 'loop' commands — all functionally similar but confusingly named. He warns against over-automating with Claude as it risks account bans, and suggests using Claude itself to create local cron jobs instead.

The second half dives into specific terminal slash commands and flags. Key ones covered include: /clear (clears context window without restarting), --dangerously-skip-permissions (bypass approval prompts for agentic workflows), plan mode (Claude plans before acting, allowing review), /compact (compresses conversation history while retaining key context), /resume (returns to a previous named session after crash or closure), /rename (names sessions for easier management across multiple terminals), /memory (controls and disables auto-memory to avoid cross-session contamination), the 'by the way' command (allows parallel side questions without interrupting active tasks), effort and model selectors (for token cost control on Pro plans), and custom /commands (markdown files that inject reusable prompts). The presenter also demonstrates how to set up loop and schedule tasks, and explains how the CLAUDE.md file and .claude/commands folder provide persistent project context and custom shortcuts.