OCDevel Claude Code

OCDevel Claude Code

By OCDevelTechnology
Download on the App Store

OCDevel Claude Code episodes

  • Permissions, settings.json, and plan mode: making one Claude Code session safe

    You can't automate a tool you don't trust. This episode is the control surface: where settings live and which file wins, how to write tight allow/ask/deny permission rules (the real fence, not CLAUDE.md), the permission modes and the Shift+Tab plan-to-act toggle, and the slash commands a power user reaches for first, including the /rewind safety net. Plus the one pitfall everyone hits: the overly broad Bash(*) allow rule.

    Episode page & show notes

    Visit website

    Episode 1 got a session running. This one makes it safe to leave running. We cover the control surfaces that turn Claude Code from a sharp tool you babysit into one you actually trust.

    Settings files and precedence. The four scopes you touch (~/.claude/settings.json, .claude/settings.json, .claude/settings.local.json, and enterprise-managed settings), which file wins when they collide, and the catch that permission rules merge across layers instead of overriding, with deny always winning. See the settings reference.

    The permission grammar. Why rules are enforced by Claude Code, not the model, so CLAUDE.md is advice and permission rules are the fence. The allow/ask/deny lists and their deny-first evaluation order. Bash glob patterns and the space-before-star word boundary, compound-command parsing, wrapper stripping (and the devbox run footgun), and gitignore-style path anchors for Read/Edit/Write. From the permissions reference.

    Modes and the plan-to-act toggle. default, acceptEdits, plan, plus auto, dontAsk, and the genuinely dangerous bypassPermissions (--dangerously-skip-permissions). The Shift+Tab cycle, the plan-mode workflow, and editing a proposed plan with Ctrl+G. See the permission modes reference.

    Slash commands a power user hits early. /clear vs /compact, /context, /config (where the removed /vim moved), /model, /permissions, /cost (now an alias for /usage), /review and /code-review, and the safety net of the episode: /rewind and double-Esc, plus the checkpointing gotcha that bash-modified files aren't tracked.

    The pitfall: the overly broad Bash(*) allow rule, why argument-constraining Bash patterns are fragile, and the deny-curl-use-WebFetch pattern instead. If you've stopped seeing prompts but never wrote specific allow rules, that's your cue to open /permissions and find what's too wide.

    26 min
  • Your first Claude Code session: the core loop, CLAUDE.md, /init, and resuming work

    How the gather-act-verify loop actually works and how to steer it without starting over. What belongs in your CLAUDE.md project memory and what to keep out, generating a first draft with /init, and resuming yesterday's session instead of re-explaining everything. Plus the pitfall every beginner hits, context going stale, and the habits that fix it.

    Episode page & show notes

    Visit website

    The first episode of the OCDevel Claude Code arc, the show that climbs from driving one session by hand all the way to a pipeline that ships to production while you're on the beach. This one is the on-ramp: everything you need to be genuinely productive in your first session, with no single primitive over-explained.

    What we cover:

    • The core agentic loop — gather context, take action, verify, repeat — and the part most people miss: you're inside the loop. How to steer mid-run with the escape key and with typed corrections, how the tiered permission prompts gate shell commands and file edits, and how checkpoints let you rewind a bad edit by tapping escape twice. See How Claude Code works and Configure permissions.
    • CLAUDE.md, your project memory — what it is, where the user / project / local files live, what to put in (specific build and test commands, conventions, "always/never" rules) and what to leave out, why you keep it under ~200 lines, and the newer auto-memory system Claude maintains alongside it. Reference: Memory.
    • /init — generate a starter memory file from your codebase, why it's safe to re-run, the opt-in guided flow, and why the draft is a starting point you refine, not a finished file.
    • Sessions and resume — work is saved continuously; pick up exactly where you left off with claude --continue or the --resume picker, and the difference between resuming, forking, and starting fresh. Reference: Manage sessions.
    • The day-one pitfall — context degradation, in both forms (the never-ending session and the bloated CLAUDE.md), how to recognize it, and the habits that fix it: clear between tasks, compact with focus, keep memory lean.

      • Recency notes for mid-2026: Claude Code is on the 2.1 line with the native installer now recommended over npm, and your default model depends on your plan (Opus 4.8 on Max/API, Sonnet 4.6 on Pro). See Model configuration.

      Next episode: settings.json, permissions, and plan mode in depth.

      26 min

    About OCDevel Claude Code

    From the publisher's feed

    Take Claude Code from its first useful change in your terminal to a repeatable software delivery workflow. For working developers who already ship applications and use Git, this course starts with…