10 Claude Code Tips You Didn't Know

Claude Code started as a terminal assistant. It's now an agentic system that reads entire codebases, executes commands, manages git workflows, and spawns subagents. If you're still using it as a chat interface with a shell wrapper bolted on, you're barely touching it. Features like CLAUDE.md and MCP servers dominate the conversation. The CLI itself, though, has a deep set of power-user capabilities that mostly go ignored. These are features built for parallelised, production-grade engineering workflows. Here are 10 patterns worth knowing. 1. Context Pre-Warming via Session Forking Resuming a session across multiple terminals interleaves the history. That corrupts the context window in ways you won't notice until the model starts hallucinating about files that don't exist. -fork-session solves this. It duplicates the full session lineage at that exact moment and produces a clean, completely independent branch. Think of it as git branch for your LLM context window. The workflow is "pre-w