All videos
0:00 / 0:00
ai

3 Claude Code Features You'll Wish You Knew Sooner

Mark Kashef16 June 2026Watch on YouTube

Part of series

Ep. 10 · Claude Code Free

View the series

Description

Master Claude Code: https://www.skool.com/earlyaidopters/about --- Your Claude Code sessions get worse over time -- not because Claude is broken, but because your context window fills up with noise. In this video, I walk you through 3 built-in features that keep Claude Code focused during long sessions: /btw for side questions that don't eat context, context: fork for running heavy skills in a separate context window, and /fork for branching conversations so dead-end exploration doesn't pollute your main session. One continuous demo from start to finish. --- Timestamps 0:00 - Why Claude Code gets worse over time 0:46 - The context decay problem (diagram) 1:27 - The three shields: /btw, /fork, context: fork 1:44 - How context: fork works (explainer) 2:34 - The demo: vault search with context: fork 4:44 - Vault search results 5:07 - Using /btw for side questions 6:11 - Slide deck results 6:33 - Using /fork to branch the conversation 7:56 - Version 2 results 8:16 - Recap and best practices --- Book a Consultation: https://calendly.com/d/crfp-qz3-m4z #claudecode #claude #anthropic #ai #aitools #aiautomation #contextwindow #aicoding #aitips #claudecodefeatures #aiprogramming #aiworkflow #productivity #devtools

What you'll learn

  • Claude Code sessions degrade over time because the context window fills with noise, not because Claude is broken
  • The /btw command allows you to ask side questions without consuming context in your main session
  • Context: fork creates a separate context window for resource-intensive tasks, keeping your main session clean
  • The /fork feature lets you branch conversations so dead-end exploration doesn't pollute your primary work
  • These three features work together to maintain Claude Code focus and efficiency during extended coding sessions

Frequently asked questions

What is the 'context decay' problem discussed in the video?
Context decay is when your Claude Code session gradually performs worse as you conduct more conversations, because the context window fills with noise and irrelevant information from earlier interactions. This degrades the quality of Claude's responses over time.
How does /btw differ from /fork and context: fork?
/btw handles side questions without consuming context in your main session. /fork branches your entire conversation so dead-end exploration doesn't pollute your main work. Context: fork runs heavy tasks in a separate context window while keeping your main session intact.
When would you use context: fork?
You use context: fork for resource-intensive tasks like vault searches or processing complex skills that consume significant context. This prevents your main session from being flooded with information from these heavy operations.
How can you prevent wrong directions in your coding from hindering your progress?
By using /fork to branch your conversation, dead-end exploration can happen in a separate branch without polluting your main session. If a direction doesn't work, you can return to your clean main session.

Topics

claudecodingai-toolsprompt-engineeringworkflow