What people actually use Claude Code for

29 million daily installs. 1,862 upvotes on a Reddit post about never writing code again. I dug through hundreds of sources to find out what people actually build with Claude Code.

Claude Code launched six months ago. Since then it has hit somewhere between $1 and $2.5 billion in annual revenue, reached 29 million daily installs in VS Code, and is on track to sit behind more than 20% of all daily code commits by the end of 2026. Big numbers. But they don't tell you what people do with it.

I've spent the past few weeks digging through Reddit threads, X posts, YouTube videos, and developer blogs to find out. Not the marketing version. The real one. What are developers, founders, and non-technical users building with Claude Code and Cowork right now?

The answers surprised me.

People stopped writing code. They started managing agents.

The most upvoted post I found on r/ClaudeAI (1,862 upvotes, 466 comments) was called "I Haven't Written a Line of Code in Six Months." The author described running several Claude Code agents in parallel and building tooling and workflows around them instead of writing code directly.

The top comment, at 227 upvotes, caught the mood: "Every time I see someone say AI isn't there yet, I'm shocked. They have no idea what's coming in the next 12-24 months."

Another commenter with over 20 years of experience put it his own way: "After forty years of coding, I'm now a shepherd of Claudes."

That's the biggest shift. Claude Code isn't an autocomplete tool for code. People treat it as an autonomous workforce they direct and review.

The personal software movement is real

One of the more interesting trends: people building software purely for themselves. @robustus on X built a weather app called skyfast.ai because, in his own words, "all weather sites are terrible." He noted that even if the app forever gets exactly one monthly active user, it was worth the hour.

A non-technical user built a surf forecasting app with Claude Code's help. It's on the App Store now, with over 100 users.

That used to mean hiring a developer, or months of learning to code yourself. Now it takes an afternoon and a clear description of what you want. The bar for "worth building" is close to zero.

14 minutes from idea to working automation

@NoahEpstein_ on X described building a complete outreach automation system. He wrote the requirements in plain English. Claude Code planned the architecture and built the whole system on its own. Total time: 14 minutes.

@JaredOfAI built an AI phone agent by connecting Claude Code to ElevenLabs for voice synthesis. Day 4 of a 30-day solo app challenge, and his agent was already making real phone calls.

@binarly_io documented a security example: given only a binary file and a CVE ID, Claude Code pulls the vulnerability details, identifies the relevant functions, decompiles them, and produces an annotated report. That kind of analysis used to take a security researcher hours.

These are shipped, working systems, not demos.

Non-code uses that save real time

Claude Code has "Code" in the name, but a growing share of users never write a single line.

File handling at scale. Sorting invoices by reading every file in a messy folder, renaming them to a standard format, and moving them to the right place. Cleaning up a chaotic Downloads folder. Finding duplicate files across drives.

Log analysis. @fat_rat_dev on X described feeding 150,000+ server logs from a Mobile Device Management system into Claude Code. He pasted the error context and asked for the cause. He got a detailed explanation and a fix in minutes instead of hours.

Video production. A top comment on r/ClaudeAI described using Remotion (a React-based video framework) with Claude Code to create and edit videos as code. The user lifts components straight from his app or landing page and turns them into animated demos.

Knowledge management. @sandraleow on X described pairing Obsidian with Claude Code and creating custom commands: /trace to follow how an idea developed over months, and /ghost to generate answers in her own voice based on her notes.

A Substack post documented 67 use cases organized by profession, from data engineers to marketers to HR teams. The pattern is consistent: people use Claude Code for any task that involves reading, sorting, transforming, or generating text and files.

The workflows that separate beginners from power users

Across all the sources I went through, five workflow patterns kept showing up:

Plan before you build. Boris Cherny, the Anthropic engineer who created Claude Code, says this is the single most important habit. Never let Claude write code before you've reviewed and approved a written plan. Separating planning from execution prevents the most common failure: Claude building the wrong thing fast.

Run sessions in parallel. Cherny himself runs five Claude Code sessions locally on his MacBook and 5-10 more on Anthropic's website at the same time. Power users treat Claude Code less like a chatbot and more like a team of junior developers they can assign different tasks at once.

Use skills, not just prompts. @Suryanshti777 on X (1,503 likes) argued that skills are "the real breakthrough" with Claude Code. Instead of asking Claude random questions, you give it structured capabilities it can run again and again. One user built governance rules for Claude Code with Claude Code itself.

Build institutional memory with CLAUDE.md. Teams keep a file called CLAUDE.md in their git repository. Every time Claude makes a mistake, they add it to the file so it never repeats it. That turns Claude Code from a stateless tool into something that learns your codebase over time.

Let Claude verify its own work. Whether through browser automation, bash commands, or running test suites, letting Claude check its own output improves quality 2-3x. The pattern: generate, verify, fix, verify again.

Enterprise is moving fast

It's not just indie hackers and side projects. Deloitte rolled Claude out to 470,000 employees, the largest enterprise deployment to date. Over 500 companies spend more than $1 million a year on Anthropic products, up 7x year over year. Claude Code runs in Rails codebases, Python data pipelines, Terraform infrastructure configs, and Kubernetes deployments in production.

One team built their own internal SWE-Bench by picking pull requests from their Rails codebase that represent good engineering work, then having an AI derive the original spec from each PR. They use it to benchmark Claude Code against competitors on their own codebase, not generic Python benchmarks.

What this means for you

The gap between people who use Claude Code as a chatbot and people who use it as an autonomous system is growing. The tool is the same. The difference is workflow.

If you're still copy-pasting code snippets from a chat window, you might be using 10% of what's available. The people getting the most value write plans, run parallel sessions, build skills, maintain CLAUDE.md files, and let Claude verify its own work.

None of this requires you to be a senior developer. Non-technical users build apps, sort files, and automate workflows with the same tool. The skill isn't coding. The skill is describing clearly what you want, and knowing when to step in and correct.

Take one task you do every week. Describe it in plain English. Let Claude Code handle it. When that works, add one more task, then another. That's how every power user I found got started.