Claude Code: The gap between "made" and "working"

Claude Code: The gap between

The biggest lesson from running dozens of tools built with Claude Code over 15 months on my work laptop and three months on a Mac mini is that while code rarely breaks, operations fail constantly. AI generates high-quality code and comprehensive tests that catch bugs effectively, yet the system often collapses outside the codebase. I've realized that "created" does not mean "functioning."

I encountered four main failure patterns. First, the "mute" process: a Discord bot managed by launchd with KeepAlive enabled. The process remained active but stopped responding due to quota exhaustion or expired logins. Because launchd perceived the process as healthy, it never restarted it. I had to shift my monitoring from process survival to response logs; now, a monitor kills the process if it becomes unresponsive, forcing launchd to restart it within 30 seconds.

Second are the silent failures of scheduled tasks. A conversation compression agent failed for three days without a single notification due to one incorrect model setting. Similarly, Google API tokens in test mode expire every seven days, causing all dependent crons to fail silently. I now use a pre-expiration warning system rather than failure alerts, as knowing after the fact is too late. I encountered this with an external hard drive as well—a delete command finished without error, but the filesystem was silently rejecting writes.

Third is the illusion of success. I registered fourteen English blog posts and a sitemap in Search Console, which reported "Success." However, after three weeks, zero posts were indexed. Individual URL inspections revealed redirection errors for the five pages Google actually attempted to crawl. A dashboard being active doesn't mean data is flowing, and the existence of a backup doesn't guarantee recovery.

Finally, environmental differences caused scripts to work in the terminal but fail in cron due to an empty PATH and different home directories. I learned that a notification is not a delivery; the pipeline only ends when the result reaches the target file.

Because I am not a professional developer, my blind spot was operations. AI provides the code and tests, but it won't monitor whether a tool is still running unless instructed. Now, whenever I build a tool, I add one line to the prompt: "Make a monitor for this too." Specifically, I implement response-log monitoring, data freshness checks, and expiration warnings.

Related posts

This post is the English edition of a Korean write-up: 원문 보기

Comments

Post a Comment

Popular posts from this blog

npm command not found on Windows: fix the PATH

Image
I recently hit a wall while configuring my development environment on Windows. It's one of those subtle issues that can waste an afternoon if you don't know what to look for. Here's exactly how I diagnosed and fixed a 'command not found' error after a successful global install. The Problem I decided to add a markdown processing tool to my toolkit by running: npm install -g markdown-it-cli The terminal output confirmed the installation succeeded, displaying a message about added packages. Satisfied, I tried to use it by typing markdown-it-cli in the command line. Windows immediately responded with: 'markdown-it-cli is not recognized as an internal or external command, operable program or batch file.' This error means Windows looked through every folder in its search list and couldn't find an executable with that name. Attempts and Failures My initial reaction was to suspect the package itself might be broken. I tried running it using npx , wh...
Read more

Claude CLI 401 Unauthorized Refresh Token Issue

Symptom: claude commands fail with 401 Unauthorized and the message "refresh token was already used. Please log out and sign in again." Cause: The refresh token expired after being consumed by another session or a background process. Refresh tokens are single-use credentials. Fix: Run claude auth login to refresh authentication without running a logout command first. Why claude login alone did not clear the 401 I was running a pipeline command when every subsequent CLI call failed. The terminal returned this exact output: Error: 401 Unauthorized Message: "Authentication failed: refresh token was already used. Please log out and sign in again." Code: "AUTH_ERROR" The error text explicitly instructs me to log out. I spent roughly ten minutes searching the terminal for a logout function. The prompt only showed AUTH_ERROR . I assumed clearing old sessions was required first. That assumption blocked progress. The instructions in the error message ...
Read more

Tailscale without sudo: what userspace mode actually costs you

At first, I installed Tailscale on macOS knowing I did not have admin rights to write to system directories. The CLI package installed cleanly enough, landing entirely within my user space without triggering any permission errors or requiring elevated prompts. The installation process felt seamless, but the friction appeared immediately during usage. Every single command I typed required appending --socket=$HOME/.tailscale/tailscaled.sock to talk to the daemon. I found myself adding this flag to status checks, key generation, and connection queries across multiple sessions. The repetition was exhausting for a tool I expected to run in the background, turning routine operations into a chore. I eventually wrote a shell function to wrap this flag, allowing me to call tailscale directly without typing the socket path every time. This workaround saved my sanity but highlighted that userspace mode demands extra configuration just to use the CLI, and any automation scripts I maintained had...
Read more