How to Run Claude Code
Without Destroying Your Machine
Claude Code is the most powerful AI coding tool available. It’s also a resource monster that will saturate your internet, pin your CPU, and leave orphaned processes everywhere.
This guide shows you how to run it all day without any of that. Every tool is free, open-source, and portable (no install required).
Quick Start
- 1.Download Nimbus Toolbox — it launches and manages everything else
- 2.Clone Bandwidth Governor — the #1 most impactful tool for Claude users
- 3.Set upload limit to 60%, download to 40%, target node.exe
- 4.Start Claude Code. Your internet stays stable. That’s it.
Step 1: Tame Your Bandwidth
The Problem
Claude Code streams large amounts of data to and from Anthropic's API. Each message includes your full project context — file contents, directory structures, conversation history. On a typical session, this can saturate a residential upload connection within minutes.
The Solution: Bandwidth Governor
Bandwidth Governor creates Windows QoS policies that cap upload and download bandwidth per-application. Set Claude Code (node.exe) to use 50-60% of your upload and 40% of your download. Everything else — Zoom, streaming, browsing — gets the remaining bandwidth automatically.
Recommended Settings
- ›Upload limit: 60% of your total upload speed
- ›Download limit: 40% of your total download speed
- ›Target process: node.exe (Claude Code runs on Node)
- ›Use the built-in speed test to find your baseline
Step 2: Cap Your CPU
The Problem
Claude Code doesn't just talk to the API — it runs TypeScript compilers (tsc), builds (next build), linters (eslint), and formatters. These can spawn 4-8 parallel processes, each trying to use all available cores. Your machine becomes unresponsive.
The Solution: Process Governor
Process Governor sets processor affinity limits per-app. Cap node.exe to 50% of your cores. On an 8-core machine, Claude gets 4 cores — still plenty fast for compiling, but your OS, browser, and other apps keep the other 4.
Recommended Settings
- ›CPU limit: 50% of cores (e.g., 4 of 8)
- ›Target: node.exe
- ›Enable persistent rules so it applies automatically
- ›Monitor real-time usage to verify
Step 3: Kill Background Bloat
The Problem
The average Windows machine has 150-300 background processes running. Many are unnecessary — telemetry, updaters, sync services, media players. Each one steals CPU cycles and RAM from Claude Code.
The Solution: Game Governor
Game Governor was built for gamers but works perfectly for AI coding sessions. Create a 'Claude Mode' profile that auto-kills non-essential processes when you start coding. Frees up 2-3GB of RAM and 10-15% CPU instantly.
Recommended Settings
- ›Create a kill list: Spotify, Discord, OneDrive, Teams (if not needed)
- ›Keep critical services: antivirus, audio drivers, network stack
- ›Use the Lag Blame Log to find what's eating resources
- ›Enable 'Game Mode' equivalent for Claude sessions
Step 4: Manage Your Ports
The Problem
Claude Code spins up dev servers (next dev on port 3000), API routes, preview instances, and test runners. Sometimes they don't shut down cleanly. You end up with orphaned processes holding ports hostage.
The Solution: Port Pilot
Port Pilot gives you a visual overview of every listening TCP port, the process that owns it, and a one-click kill button. No more 'Error: listen EADDRINUSE :::3000'.
Recommended Settings
- ›Check ports before starting a new dev server
- ›Kill any stale node.exe processes on 3000-3999
- ›Use auto-refresh to monitor during active development
Step 5: Protect Your Clipboard
The Problem
Working with Claude Code means constantly copying API keys, environment variables, error messages, code snippets, and file paths. One wrong paste and you've shared an API key in a commit or a Slack message.
The Solution: Clipboard Vault
Clipboard Vault maintains a full searchable clipboard history and auto-flags anything that looks like an API key, token, or secret. Pin frequently-used snippets. Search your history when you need that error message from 20 minutes ago.
Recommended Settings
- ›Enable secret detection (auto-flags API keys, tokens, passwords)
- ›Pin your commonly-used snippets (boilerplate, env vars)
- ›Use search to find that error message you copied earlier
Step 6: Monitor Everything
The Problem
When Claude Code is running a 10-minute Next.js build, you want to know if it's progressing or stuck. When your machine slows down, you want to know which process is the culprit — immediately.
The Solution: System Pulse
System Pulse tracks CPU, memory, and network usage per-process in real-time. It sends data to a cloud dashboard so you can monitor from your phone. If a process goes haywire, you can kill it remotely.
Recommended Settings
- ›Install the agent on your dev machine
- ›Check the cloud dashboard at cloudnimbusllc.com/system-pulse
- ›Set up alerts for CPU > 90% sustained
- ›Use the historical logs to identify patterns
Step 7: Launch Everything at Once
The Problem
Starting 5-7 tools manually before every coding session is tedious. You forget one, and 3 hours later your internet is dead because Bandwidth Governor wasn't running.
The Solution: Nimbus Toolbox
Nimbus Toolbox is the launcher. One click in the system tray launches your entire toolkit. It auto-discovers installed tools and lets you clone any you're missing directly from GitHub.
Recommended Settings
- ›Install Nimbus Toolbox first — it manages everything else
- ›Use 'Clone & Install' for any tools you don't have yet
- ›Pin to startup so it's always ready
- ›Configure your default launch set
Who This Is For
Claude Code power users
Running Claude 4+ hours/day and tired of the resource problems
Developers with limited bandwidth
Residential internet, shared connections, or metered plans
People who also need their computer
You're running Claude AND Zoom AND a browser AND Slack
Anyone who's been asked 'why is the WiFi slow?'
You know who you are.
Get Started
All tools are free, open-source, and portable. No install required. Just download and run.
Built by Glen Bradford — Cloud Nimbus LLC — because running Claude Code shouldn’t require apologizing to your household.