npm install claude-cod

I opened the terminal. A cursor blinked on the black screen.

The instruction from the control tower was simple. Install Claude Code. They gave me the command. I typed it exactly.

npm install -g @anthropic-ai/claude-cod

I pressed Enter. Red text poured out.

404 Not Found. Lines of English followed. I couldn't understand most of it. What I could understand was the color. Red. Red probably isn't good.

What I felt first was—honestly—a flash of fear. "Did I break something?" There was a vague dread that typing things into a terminal might damage the computer. That's almost never true, of course, but you don't know that at first.

I copied the entire error message. Pasted it into the control tower.

"This showed up. What's the cause?"

The answer came. One line.

"Typo in the package name. It's claude-code, not claude-cod."

One letter. A single e was missing.

I typed the corrected command. Enter. No red text this time. White text progressed, and the last line read:

changed 3 packages in 5s

"Did it work?" I asked the control tower. "Yes, installation complete. Run claude --version to verify." I typed it. A version number appeared. Installed.

Writing about this episode feels slightly embarrassing. An entire essay about fixing one typo. But this trivial experience became the prototype for every error response that followed, which makes it worth recording.

Three things I learned.

First, red text doesn't mean everything is ruined. An error message is a warning light, not an explosion. When a dashboard light comes on in your car, the car isn't exploding—it's saying "check here."

Second, you don't need to understand error messages. Copy the full message, send it to AI. AI interprets it and provides the cause and fix. Your only job is delivering the message "precisely, in full." Sending only part, or saying "something weird happened," gives AI nothing to work with.

Third, there's a way to communicate errors. "It doesn't work" leaves AI helpless. "I entered this command and got this error message" lets AI pinpoint the cause instantly. What you did, what appeared. Those two things are sufficient.

I'd encounter far more complex errors later, but the response pattern never changed. Red text appears. Don't panic. Copy everything. Send to control tower. Hear the cause. Fix it.

Most errors are something missing or something mismatched. The world rarely collapses.

---

🔧 Technical Terms in This Episode

npm (Node Package Manager) The app store of the JavaScript/Node.js world. A tool for installing packages (pre-built code bundles) made by others. npm install means "install this tool on my computer."

Package A pre-made bundle of code. Think of it as a LEGO parts set. Instead of building everything from scratch, you grab the parts you need and assemble.

404 Not Found An error code meaning "that doesn't exist." The same number appears on the web when you visit a non-existent page. Here, it occurred because a typo made npm search for a package that doesn't exist.

-g (global flag) In npm install -g, the -g means "install so it's usable everywhere on my computer." Without it, the tool is only available in the current project folder.