ClaudeOps — A New Practice for Embedding Claude into Your Operations

Introduction I'm Yuki Tatsunami, founder of OkojoAI. I started out as a software engineer, then moved into Deep Learning research. For the past year or so, I've been spending most of my time building LLM-powered software and SaaS products. Honestly, I'd rather just be doing Deep Learning research. But the reality is, in fast-moving spaces, you can't compete without tools like Claude Code. I use it, even though it sometimes feels like it's taking away the joy of thinking through problems myself. That tension is actually where ClaudeOps comes from: what do you delegate to Claude, and what do you keep thinking through yourself? What is ClaudeOps? Here's my definition: ClaudeOps is the practice of running Claude continuously in the background to automate routine detection, triage, and action generation — where judgment is shared between Claude and humans, and final approval always stays with humans. Compared to existing Ops practices: What gets automated DevOps Build, test, deploy MLOps Mo