Claude for Authors: The Three Tools You’re Probably Only Using One Of
This is Part 1 of a new series on using Claude to run your author business. Starting with the basics — because “Claude” isn’t one thing anymore.
I’ve been getting the same question from about forty different directions since Ireland: “What is Claude Code and why won’t you shut up about it.” (Fair.) So I made two things.
A 45-minute video where I break down all three Claude tools, do a live demo, and walk through the weekend I handed Claude Code my entire Notion task backlog and sat in my easy chair while it worked through 100+ tasks. It’s 45 minutes of me being thorough and slightly unhinged. That one’s for the people who learn by watching someone push buttons and gasp.
This newsletter, which covers the same ground in about eight minutes of reading. No buffering required.
If you consume both, there’s overlap — that’s on purpose, not early-onset memory loss. (Though ask me again in a few years.) Pick whichever fits your capacity.
Most of you have used Claude. You’ve opened claude.ai, typed a question, gotten an answer. Maybe you’ve used it to brainstorm plot points, draft a blurb, or ask why your Mailerlite automation isn’t firing. (It’s always the trigger. Always.)
That version of Claude — the chatbot in a browser — is one of three tools Anthropic makes now. The other two are where things get interesting for running your author business. And almost nobody in the indie author space is explaining them clearly, because the people who use them are mostly developers writing for other developers.
I’m an old-school programmer — DOS, COBOL, C++ back in the Y2K and Code Red Mountain Dew era. I stepped away from coding for a long time, and Claude Code brought me back. Not as a developer, exactly, but as a product manager who can build things again. That’s a distinction worth understanding, and I’ll come back to it later in this series. For now, let me translate the three tools into author-friendly language.
Hey, real quick: if you’re also into vibe coding, I have a Discord Channel to come hang out with a nerd herd: https://discord.gg/MZKACmjSjs
The Three Claudes, in Plain English
Claude Chat is the one you know. You type, it responds, you copy-paste the output somewhere useful. It lives in your browser or the Claude app. Think of it as a very smart coworker who can only communicate through sticky notes — you hand one over, they hand one back.
Claude Cowork is the one most of you should care about right now. It launched in January 2026 and it lives in the Claude desktop app. You open it, point it at a folder on your computer, and say “do this.” It reads your files, creates new ones, edits existing ones, and works through multi-step tasks on its own — checking in with you along the way. If Claude Chat is a coworker who communicates through sticky notes, Cowork is a coworker who has a key to the office and can actually sit down at the desk and do the work.
Claude Code is Cowork’s more powerful (and more intimidating) sibling. It runs in your terminal (the black screen with the blinking cursor that makes you feel like you’re in a 90s hacker movie). It can write code, run commands, create files, connect to your databases, manage your servers — anything you could do from a command line, Claude Code can do for you. This is the tool I used to build AmandaBot, authorautomations.social, and most of the infrastructure that runs my business. It is extremely powerful and it looks like The Matrix. (It’s also how I scrapped my entire Ireland presentation and rebuilt it in an afternoon, which is a story for another installment.)
Here’s why that distinction matters: in Chat, you are the bottleneck. You copy text in, you copy text out, you paste it somewhere, you format it, you save it. Every step is a manual handoff. In Cowork, Claude handles the handoffs. You describe the outcome, and it produces deliverables — actual files, in your actual folder, ready to use. In Code, you can do everything in Cowork, and more.
When You’d Use Which
This is the part I wish someone had spelled out for me six months ago instead of making me piece it together from developer Twitter threads.
Use Chat when you need a conversation. Brainstorming, Q&A, feedback on a blurb, “is this sentence grammatically correct or am I losing my mind.” Anything where the back-and-forth is the point.
Use Cowork when you have a task with a tangible output. You want a document created. Files organized. A spreadsheet built from scattered information. A batch of social media posts drafted and saved. Anything where you’d normally say “I need to sit down for an hour and just power through this” — that’s a Cowork job.
Use Code when you want to clone yourself. Chat answers questions. Cowork handles tasks. Code is where you build the systems that run your business while you’re not looking — the connectors that link Claude to your email, your website, your social platforms. The skills that teach it how you want things done. The agents that handle recurring work on your behalf. The hooks that trigger workflows automatically. This is how I built AmandaBot, and it’s how I run a publishing company, a training business, a magazine, and a social media platform from my iPad while traveling across two continents. Code is the infrastructure layer, and you don’t need a CS degree to use it. (I don’t have one. I have stubbornness and a COBOL background from the Reagan administration, which is arguably worse.)
Most authors will live in Chat and Cowork. That’s completely fine. Code is where you go when you’re ready to build the systems that let you stop doing the work and start overseeing it — and we’ll get there later in this series.
What This Actually Looks Like: A Real Example in Cowork
Full disclosure: my own book organization lives in StorytellerOS now, so I don’t actually need Cowork for this particular task anymore. But I wanted to test it with something familiar so I could show you what the experience feels like — and a messy book launch folder is about as universal as it gets.
I had a folder on my desktop with everything for an upcoming book launch. Cover images in three sizes. A blurb document. A series overview. A few versions of taglines I’d been noodling on. Comp titles in a text file. Release date, preorder links, ISBNs — scattered across multiple docs because I am a chaotic creature who organizes by vibes.
I opened Cowork, pointed it at the folder, and said: “Read everything in here and create a complete book launch media kit. I need a one-sheet with the cover, blurb, comp titles, buy links, and author bio. Then create a separate file with 20 social media posts in my voice — mix of announcement posts, countdown posts, and reader-question posts. Save everything back into this folder.”
Cowork read every file. It figured out which cover was the final version (because I’d named it “FINAL-final-v3-USE-THIS” like a professional). It pulled the blurb, matched it to the comp titles, grabbed the links, and produced a clean one-sheet as a markdown file and 20 social posts in a separate document. Saved them right into my launch folder.
I reviewed the posts, tweaked maybe four of them, and moved on with my life.
The same task in Chat would have meant: open each document, copy the contents, paste them into the chat window one at a time (hoping I don’t hit the context limit), explain what I want, get the output back as text in a chat bubble, then copy it out and paste it into a new document, format it, and save it myself. Every handoff is manual. Every step is me.
In Cowork, I described the outcome and went to make coffee. (The espresso machine at home works. Unlike certain Regus locations I could name.)
Getting Started
Cowork is available now in the Claude desktop app on Mac and Windows. You’ll need a Claude Pro subscription ($20/month) at minimum — it’s also available on Team and Enterprise plans.
To try it:
Download the Claude desktop app from claude.ai if you don’t have it
Open the app and click “Cowork” in the sidebar
Choose a folder to give Claude access to (start with something low-stakes — a folder of drafts, your book metadata, your launch files)
Give it a task in plain English
Watch it work and approve or redirect as it goes
Start small. “Organize these files by project” or “read this manuscript and create a chapter-by-chapter summary” or “build me a spreadsheet of all the ISBNs, titles, and publication dates from these documents.” Once you see what it can do with your own files, you’ll start seeing Cowork-shaped tasks everywhere.
Full Disclosure: It’s New, and It Shows
Cowork is genuinely useful and I would not be writing a multi-part series about it if I didn’t believe that. I also need you to know that it is sometimes buggy as hell.
It doesn’t always do what you ask it to do. The Chrome browser takeover feature is a bit of a nightmare and will eat your tokens like chocolate chip cookies the day before you start Keto. It can be frustratingly dumb about connecting to all your tools, and while the interface is friendly enough, the troubleshooting and initial setup might make you want to toss your computer into the nearest body of water. (If you’re near a lake, I recommend a good overhead throw. Very cathartic.)
I’m telling you this now so you don’t hit your first wall and think you’re doing it wrong. You’re not. The tool is young. These are all pitfalls I’ll go over in depth across this series and at the AI Summit — what to expect, what to work around, and what to just wait for Anthropic to fix.
What’s Coming in This Series
This is Part 1. Here’s where we’re headed:
Part 2: Cowork for Your Social Media — I’ll walk through using Cowork to generate and schedule social content for your books, including how it connects to authorautomations.social and the Claude plugin that lets you manage your posting calendar in plain English.
Part 3: Building Your First Claude Skill — Skills are reusable instructions that make Claude better at specific tasks — and they work in Cowork, not just Code. I’ll show you how to create one for your own writing or business workflow.
Part 4: Connectors — Giving Claude Access to Your Tools — Connectors are how Claude talks to the rest of your business. Email, Google Drive, your calendar, your social platforms. I’ll walk through what’s available, how to set them up, and which ones are worth your time right now.
Part 5: Clone Yourself with Claude Code — This is where you go from doing the work to building the systems that do the work for you. Connectors, skills, agents, and the infrastructure that lets you run a business from your iPad. I’ll show you what’s possible and where the on-ramp is. (I promised you I’d redo the walkthrough I recorded a few weeks ago with the new features, and I will.)
Part 6: The Agentic Author Stack — How all of this fits together. Chat, Cowork, Code, MCP servers, authorautomations.social, and the tools that connect them. The full picture of what it looks like to run an author business with AI agents handling the operations.
If there’s something specific you want me to cover, reply to this email. I read every one of them. (AmandaBot does too, but she’s polite enough not to spoil the answers.)
The summit is April 21–22. Day 1 is free. If you’ve been on the fence, this series will give you a head start on everything we’ll cover in the paid sessions on Day 2. Details at aisummit.indieauthortraining.com.
I'm back in Texas this week, reunited with my espresso machine and a desk that doesn't require a subscription. Part 2 drops in a few days and not weekly. In the meantime, go download the Claude desktop app and point Cowork at your messiest folder. You'll either be impressed or you'll want to throw your laptop in a lake. Either way, you'll have something to tell me about.