Blog · July 7, 2026 · 8 min read · by Vilva Athiban P B
Claude Code Tips and Tricks: 12 Ways to Use Claude Code Effectively
Claude Code has quietly become the tool a lot of us live in all day — and not just programmers. People use it to maintain websites, clean up spreadsheets, automate boring chores, and build things they never thought they could build. But most tips lists out there are written for software engineers, full of jargon about hooks and configs.
This one isn't. These are twelve practical Claude Code tips and tricks — useful whether you're a beginner or you already spend hours a day in the terminal — for using Claude Code effectively without an engineering degree.
1. Always start in the right folder
Claude Code works inside whatever folder you open it from. Starting it from your home folder gives it a confusing view of your entire computer. Before you type claude, move into the project folder you actually want to work on (type cd, a space, then drag the folder onto the terminal and press Enter). Everything — context, memory, even notifications — works better from a project folder.
2. Brief it like a colleague, not a search engine
"Fix the About page" forces Claude to guess what's wrong. "The About page shows the team photos in the wrong order — founders should come first, and the layout breaks on phones" gets it right the first time. The one extra sentence of context you give upfront routinely saves a ten-minute round trip.
3. Use Plan Mode for anything big
Press Shift+Tab twice and Claude Code switches into Plan Mode: it reads everything, thinks, and presents a plan — without changing a single file. You review the plan in plain English, adjust it, and only then let it work. For anything that touches more than a couple of files, this is the difference between delegating and gambling.
4. Keep a briefing file (CLAUDE.md)
There's a special file called CLAUDE.md that Claude reads at the start of every session — think of it as a standing briefing document. What the project is, how you like things done, what to never touch. You don't have to write it yourself: type /init once and Claude drafts it for you. Every session after that starts smarter.
5. Clear the slate between unrelated tasks
When you finish one task and start something unrelated, type /clear. Long, winding conversations make Claude slower and more forgetful — a fresh start with a clear head beats dragging two hours of old context into a new problem.
6. Interrupt early instead of waiting politely
If you can see Claude going down the wrong path, press Escape. It stops immediately and waits for new directions. Letting a wrong approach finish just so you can correct it afterwards wastes the whole run — steering early is always cheaper.
7. Stop watching it work
This is the tip that changes the day-to-day the most. A serious Claude Code task runs for several minutes, and the terminal is silent the whole time. So you either sit there watching text scroll — or you switch to something else and miss the moment it finishes (or worse, the moment it pauses to ask your permission and sits blocked while you're answering email).
Heavy users solve this with notifications. We built AI Done Now for exactly this: a Mac menu bar app that plays a sound and shows a clickable notification when Claude Code finishes or needs your input — with different alerts for "done" and "waiting for you", so you know whether to come back now or finish your coffee.
8. Treat permission prompts as your safety net
Claude Code asks before doing anything consequential — running commands, deleting things, installing software. Don't rush to approve everything blindly, and don't switch on "skip all permissions" modes you may see mentioned online. Those prompts are the moments you stay in control without needing to understand the code itself.
9. Run a second session
Nothing says you can only have one Claude Code running. Open a second terminal tab in a different project folder and you've doubled your output — one session redesigns your site while another cleans up your files. It takes a little organization (we wrote a full guide to running multiple Claude Code sessions), but it's how extensive users get so much done.
10. Ask it to explain anything, anytime
You never need to pretend you understood. "Explain what you just changed like I'm not a programmer" is a completely valid prompt, and Claude is genuinely good at it. Make it a habit after every big change — you'll learn your own project faster than you expect.
11. Ask for save points before big changes
Before Claude attempts something risky, say: "make a checkpoint first so we can undo this if it goes wrong." Claude uses a system called git to snapshot your project, and it handles the details for you. If the experiment fails, one sentence — "go back to the checkpoint" — restores everything.
12. Use it for the un-glamorous stuff too
Claude Code isn't only for building things. Renaming five hundred photos, merging spreadsheets, converting file formats, drafting a README — the boring chores you've postponed for months are usually one prompt away. Some of the happiest Claude Code users barely "code" with it at all.
The common thread
Every tip here points the same direction: treat Claude Code less like a chatbot you babysit and more like a capable colleague you brief, check in on, and trust to work while you do something else. Set up the briefing file, plan before big jobs, run a parallel session — and let notifications tell you when you're needed, instead of your eyes.
Keep reading
Desk Exercises for Programmers: 15 Moves to Do While Your AI Agent Codes
7 min read
Exercise While Coding: Turn Claude Code Wait Time Into Micro-Workouts
7 min read
Claude Code Notch Notifications on Mac: See When Claude Is Done Without Watching the Terminal
7 min read
Claude Code Multiple Sessions: How to Run Agents in Parallel Without Losing Track
6 min read
A Claude Code Workflow That Doesn't Involve Watching the Terminal
5 min read
Claude Code Hooks: A Practical Guide to Automating Your Agent Workflow
7 min read
Claude Code Auto Mode: Fewer Permission Prompts Without Living Dangerously
7 min read
Claude Code Subagents: How to Delegate Work to Specialized Agents
7 min read
Claude Code Context Management: Treat the Context Window Like a Budget
6 min read
Per-Subagent Model Selection: Route the Grunt Work Down, Keep the Judgment Up Top
7 min read
Skills and Plugins: How to Teach Claude Code Your Way of Working
7 min read
Claude Code Background Tasks: Run Long Commands Without Blocking Your Session
6 min read
Codex CLI Notifications: How to Get a Ding When Codex Is Done or Needs Input
7 min read
Cursor Notification When Done: Every Way to Get Notified When Cursor Finishes
6 min read
Claude Code Notifications: How to Get Notified When Claude Code Finishes or Needs Your Input
6 min read
Want to Be Notified When Claude Responds? How Claude Notifications Work on Web, Desktop, and Mobile
5 min read
Claude Code Notification Scripts: Copy-Paste Recipes for Every Platform
6 min read
Get a Ding the Moment Codex Needs Your Response
6 min read
Get Notified the Moment Claude Code Is Waiting for Your Input
6 min read
“Notifications Are Turned Off for Claude” — Here Is the Fix
6 min read
Codex Sound When Done: Make Codex CLI Play a Sound When It Finishes
6 min read
terminal-notifier + Claude Code: Native macOS Alerts When Your Agent Finishes
6 min read
Gemini CLI Notifications: How to Get a Sound or Alert When Gemini Finishes
6 min read
Get Claude Code Notifications on Your Phone
6 min read
Claude Code Remote Control, Explained
7 min read
preferredNotifChannel: Claude Code's Built-In Notification Setting
6 min read
Claude Code Notifications in tmux and Over SSH
7 min read
Claude Code Effort Levels: Why Your Setting Keeps Getting Ignored
8 min read
Codex vs Claude Code Notifications: How Each One Tells You It Is Done
8 min read
Claude Code Notifications Not Working: A Diagnostic Checklist
10 min read
Claude Code Notifications Inside Your Editor's Terminal
7 min read
CLAUDE_CODE_DISABLE_BACKGROUND_TASKS Explained
7 min read
CLAUDE_CODE_DISABLE_BG_SHELL_PRESSURE_REAP Explained
8 min read
Cursor Alerts Explained: Every Alert Cursor Raises, and How to Control Them
7 min read
Claude Code Environment Variables: The Groups That Actually Matter
10 min read
Claude Code Notifications on WSL and Windows
9 min read
Claude Code Checkpoints and /rewind
8 min read
Claude Remote Control: How It Works, Turning It Off, and Auto Mode
7 min read
Claude Code /loop: Poll a Deploy, Babysit a PR, and Get Told When It's Done
8 min read
Setting Up NotchFit With OpenAI Codex CLI: Hooks, $notchfit-plan, and the Daily Flow
7 min read
Claude Mods Explained: What the New Plugin Layer Can Do, and How to Turn On 'You Should Know'
9 min read
NotchFit vs Mac Break Reminder Apps: A Clock or a Signal From Your Coding Agent?
8 min read
Claude Code Headless Mode: Running claude -p in Scripts and CI, and the Three Signals That It Finished
10 min read
Building a Movement Habit at a Desk: Use the Agent Run as the Cue, One Set as the Unit, and Streaks Carefully
8 min read
Claude Code MCP Servers Explained: Adding Servers, Choosing a Scope, Handling Secrets, and Why Long Tool Calls Go to the Background
10 min read
/notchfit:plan Explained: How Claude Code or Codex Writes a Weekly Workout Plan the Notch Can Actually Run
8 min read
Claude Code Spinner Verbs Explained: What “Pondering” and “Brewing” Mean, How to Change Them, and Why You Should Stop Watching the Spinner
7 min read
Why NotchFit's Done and Permission Alerts Wait Until Your Set Ends, When That Costs You, and How to Turn the Workout Off
7 min read
How to Resume a Claude Code Session: --continue vs --resume, Naming Sessions, the Session Picker, Branching, and What Comes Back
9 min read
NotchFit on a Mac Without a Notch: How Pill Mode Works on Mac mini, iMac, Mac Studio and a MacBook With the Lid Closed
6 min read
How to Run a Claude Code Session in the Background: /background, claude --bg, Agent View, and Getting Back to It
9 min read
What a Notch App Can See: NotchFit's Local-First Design, What the Claude Code and Codex Hooks Send, and What Stays on Your Mac
7 min read
Why Codex CLI Asks for Permission Every Time, and How to Tune the Sandbox and Approval Policy Without Going Full Access
8 min read
What to Do While Claude Code or Codex Works: A Simple Protocol for the Two-to-Twenty-Minute Gap in Every Agent Run
7 min read
Is It Possible to Get a Notification When Claude Code or Codex Hits a Reset? Yes for Claude Code: the quota_auto_resume Hooks, Explained
8 min read
What a MacBook Notch App Can Actually Do: The Five Kinds of Notch Utility, Their Trade-offs, and Where NotchFit Fits
7 min read
How to Make MCP Servers Not Take Up as Much Context in Claude Code: Tool Search, alwaysLoad, Scopes and Output Caps
8 min read
The notchfit Command Line: Drive Your Workout, Read Status as JSON, Validate Plans and Test the Notch Without Leaving the Terminal
7 min read
How to Audit MCP Tool Calls Made by Claude Code: A Five-Minute Hook Audit Log, OpenTelemetry Tool Events, and the Transcript for Investigations
9 min read
Exercise Snacks: What the Research Actually Says About One-Minute Vigorous Breaks, What It Does Not, and How NotchFit's Agent-Run Sets Compare
8 min read
How Long Until a Claude Code MCP Tool Call Times Out? The Four Timers (Startup, Two-Minute Backgrounding, Idle, Wall-Clock), Their Defaults, and Which One to Change
8 min read
Sitting Too Long as a Developer: The Posture Problems Coding Agents Made Worse, What the Research Says About Breaking Up Sitting, and How NotchFit Turns an Agent Run Into the Break
8 min read
Claude Code .mcp.json Explained: Where Project-Scoped MCP Servers Are Read From, What Happens in Subfolders and Monorepos, and Why a Committed Server Shows Pending Approval
8 min read
Standing Desk Exercises for Developers: Why Standing Still Is Not the Goal, Eight Movements That Fit a Thirty-Second Agent Run, and How NotchFit Cues Them From the Notch
8 min read
The claude mcp Command Reference: add Syntax by Transport, What --scope local, project and user Actually Mean, add-json and add-from-claude-desktop, list, get, remove, login and serve
9 min read
Your First Week With NotchFit: Install and Simulate, Run Real Tasks, Write a Smaller Plan Than You Want, Tune the Alerts, Survive the First Skipped Day, and Decide What Stays
8 min read
How to Stop a Running Claude Code Task: Esc vs Ctrl+C, Background Tasks, Subagents, and Disconnecting Remote Control
8 min read
Pomodoro vs Agent-Driven Breaks: Timing Movement to Claude Code and Codex Runs Instead of a Timer
7 min read
Claude Desktop MCP Configuration: claude_desktop_config.json, Logs, Extensions, and the Difference From Claude Code
9 min read
The 20-20-20 Rule for Developers: Eye Strain, the Evidence, and Agent Runs as the Cue
8 min read
Claude Agent SDK + MCP Servers: mcpServers, allowedTools, Status Checks and Auth
9 min read
Discreet Desk Exercises for an Open-Plan Office While Claude Code Runs
7 min read