Claude Code for People Who Don't Code
A non-coder professional explains the Claude ecosystem hierarchy — from terminal (Claude Code) down to Claude Chat and Chrome extension — arguing that the terminal version offers the most features, stability, and control. The video covers installation, slash commands, memory management, scheduling, and workflow tips for productive use of Claude Code without needing coding skills.
Summary
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.
Key Insights
- The presenter argues that Claude Co-work, Claude Desktop, and Claude Chat are all progressively stripped-down versions built on top of the raw Claude Code terminal, meaning non-coders who use only the desktop versions are missing features that already exist in the base layer.
- The presenter distinguishes local folder access (dynamic — Claude can read and update documents across sessions) from the Projects feature (static — uploaded files are never modified by Claude), arguing that local folders are far superior for real professional work because they enable persistent, evolving memory.
- The presenter explains that the terminal version's 'plan mode' forces Claude to map out all intended steps before making any changes, allowing the user to review and approve the plan — a capability absent from Claude Co-work, which instead relies on back-end custom prompting to ask clarifying questions.
- The presenter strongly recommends disabling Claude's auto-memory feature, arguing that global memory pulled from unrelated sessions in different folders actively confuses Claude during current work, and that a manually controlled CLAUDE.md project file is more reliable and focused.
- The presenter demonstrates that named terminal sessions can be fully resumed after crashes or accidental closures using the /resume command, recovering the full conversation context — a durability advantage he presents as a key reason non-coders should not fear the terminal.
Topics
Transcript
[0:00] This is literally the video I would have wished to get when I started using Claude as a professional not as a coder as a professional who needs to get real work done in the business and that's what I will share with you. This video is split into two parts. In the beginning I will go really deep into the claw ecosystem because this is completely confusing and I think I found a way to explain this very simply. Claude co-work versus code and so on and then after this I will dive into claude [0:30] code the terminal version bear with me and show you how I use this because after going this environment you will clearly…
Full transcript available for MurmurCast members
Sign Up to AccessMore from ICOR with Tom | AI Productivity
Obsidian is the tool I teach in. Keep the one you have.
The creator addresses criticism about switching to Obsidian after previously promoting other tools, clarifying that his tool-agnostic ICOR methodology remains unchanged and that Obsidian is simply an interface layer for his folder-based system. He emphasizes that the underlying folder structure, AI automation, and productivity principles are identical regardless of which tool visualizes the content.
Claude sucks. And here is why.
This video explores why Claude and other AI models produce inconsistent results, examining how model selection (Haiku vs Sonnet vs Opus vs Claude 3.5 Fable), effort levels, prompt clarity, and system context dramatically affect output quality. The speaker demonstrates these differences through a Venn diagram creation task and advocates for using organized folder systems with documented SOPs and code-based solutions to ensure consistent AI performance.
Claude can now prompt its own SESSIONS. I built the boss.
Claude now has the ability to interact with multiple sessions, allowing a streamlined orchestration of tasks through an agent called Larry. This integration can simplify task management and enhance productivity by enabling a single main session to oversee various sub-sessions or tasks.
I switched off Claude's memory. My folder does it better.
Tom explains why he disabled Claude's native memory feature and instead built a local folder-based system (myPKM) to maintain persistent context with AI agents. He shares an audit revealing systemic issues like contradictory documentation, forgotten rules, and parallel session conflicts, then outlines how to systematically fix these problems using the ICOR productivity methodology.
I do not download invoices anymore. My folder and Claude do it.
The speaker demonstrates how he uses AI (Claude) integrated with his local folder system to automate invoice collection for his accountant, downloading 36 invoices in 5 minutes with minimal manual intervention. He explains his AI team methodology, work streams, and how persistent local knowledge bases enable AI to handle recurring tasks independently without constant re-explanation.