I Ranked Every Claude Feature. Here's the Tier List.

TL;DR

• I ranked every Claude feature by one thing only: how much it changes my actual day doing knowledge work and automation. Not benchmarks. Not building apps.
• The whole S tier shares a pattern. Every feature up there removes me from the loop. They let the work keep going while I am gone.
• The crown goes to /goal: set a finish line and Claude keeps working until it is met.

What is the one pattern that runs through the whole S tier?

When I lined up the twelve features that genuinely changed how I work, I noticed they all do the same thing. They take me out of the loop. /goal, Routines, /loop, Subagents, Agent Teams, Remote Control, Auto Memory. None of them are about getting a smarter answer to a single question. They are about letting the work continue without me sitting there feeding it the next prompt.

S Tier: the features that actually changed how I work

10. Auto Memory. It remembers my preferences and patterns per repo, on its own, without me writing anything down. The "on its own" part is the whole thing. I am not maintaining a notes file, and I am not re-explaining how I like things done every time I come back. The tool quietly learns the shape of how I work in each project.

8. /rewind. Roll back code and conversation to any earlier checkpoint. This one is here for a quieter reason than the rest. The walk-away features only work if walking away is safe, and /rewind is the safety net. If an agent runs off in a bad direction while I am not watching, I roll the whole thing, code and chat both, back to a checkpoint and continue. It is the feature that lets me trust all the others.

7. Subagents. Spin off background agents, each in its own context window. The "own context window" detail is what makes this work instead of a mess. Each subagent gets its own clean room to think in, so a big background job does not pollute the main thread I am working in. I fire one off, keep going on my main task, and collect the result later.

6. /loop. Re-run a prompt on an interval, like polling a deploy or checking on a pull request. Plain on paper, big in practice. So much of real work is "go check on this again in a few minutes," and before /loop that meant me being the timer. Now I set the interval and the prompt, and the tool does the checking. When I want work to continue until a condition is true, that is what /goal is for.

4. Routines. Cloud agents that run on a schedule, from an API call, or on GitHub events, with my laptop closed. Read that last part again. Laptop closed. Up to now everything on this list still assumed my machine was on. Routines do not. They run on Anthropic-managed cloud infrastructure whether I am working, asleep, or on a plane. They are a research preview on Pro, Max, Team, and Enterprise plans, and a nightly or weekly routine against a repository and its connectors needs nothing from my machine.

2. Skills. Folders with a SKILL.md file that teach Claude my own workflows. This is the one I would hand to someone else first, because it compounds. A Skill teaches the tool how I do a specific thing, once, and then Claude uses it when it is relevant or when I call it with a slash command. I use skills for interface design work and for recurring SEO and content tasks, workflows I taught the tool once and do not have to re-explain every session. This is the same thing I help owners do when they're choosing and adopting new technology: codify the workflow once so the team doesn't relearn it every time. If /goal is the crown, Skills are the reason the rest of the kingdom keeps running.

1. /goal. The crown. Set a completion condition, and Claude keeps working until it is met.

What is in the A tier, so close to S?

• Dispatch lets me start a task on my phone and have Claude run it on my desktop and send back the result.
• Claude Desktop App is the home base on Mac and Windows for chat, Cowork, and Claude Code.
• Claude Design turns a description of a prototype, deck, or one-pager into a first draft I can refine.
• Plugins and Marketplace install whole bundles of skills, agents, hooks, and MCP servers in one go.
• Workspace Connectors wire up Gmail, Calendar, and Drive so Claude works with my Google data directly.
• File Creation and Editing builds Excel, Word, PowerPoint, and PDF files I can download.
• Ultracode is a Claude Code setting in the /effort menu: it sends xhigh effort to the model and has Claude orchestrate dynamic workflows for substantive tasks.
• Effort Levels let me dial reasoning depth from low up to max with /effort.
• Channels push Telegram, Discord, or iMessage messages into a live session, two-way. They are still a research preview.
• Hooks run my own commands automatically on session events.
• Auto Mode has a second model, a classifier, review actions instead of me, so I am not clicking yes all day.
• /background detaches a session to keep running as a background agent that I can check on later.
• Agent View gives me one dashboard of every background agent and its status.
• Plan Mode has Claude research and propose a plan before touching anything.
• /btw lets me ask a quick side question without derailing the main task.
• /usage shows what is driving my plan limits.
• /context shows exactly what is filling the context window.
• Prompt Caching reuses repeated context so big sessions cost less and respond faster.

What lands in B tier?

• Dynamic Workflows have Claude write a script that orchestrates many subagents for huge jobs.
• Git Worktrees run agents in isolated copies of the repo so they never collide.
• Ultrareview, run with /code-review ultra, sends a fleet of reviewer agents in the cloud to find and verify bugs before I merge.
• /deep-research fans out web searches and returns one cited report.
• Claude in Chrome is a side panel that clicks, fills forms, and acts across my tabs.
• Artifact Apps turn a description into shareable apps and tools.
• Computer Use points and clicks to run any app when there is no connector for it.
• Research chains multiple searches across the web and connected apps like Gmail and Google Docs into a cited report.
• Projects keep chats, files, and instructions together in one workspace.
• Mobile Push pings my phone when a long task finishes or needs me.
• /recap gives a quick recap of where I left off.
• Visual and interactive content draws diagrams and interactive charts right in the chat.
• Artifacts show substantial, standalone content in a dedicated window next to the conversation.
• Memory carries relevant context from past chats into new ones.
• The directory lets me browse and install skills, connectors, and plugins in one place.
• Claude for Microsoft 365 brings Claude into Word, Excel, PowerPoint, and Outlook.

Why are Cowork and voice in C tier?

• Voice Mode is full spoken conversations, hands-free.
• Cowork brings Claude Code's agentic capabilities to knowledge work beyond coding, no terminal needed.
• Interactive Connectors display live apps, like an Asana board, right inside the conversation.
• Citations let API responses point to the source documents behind an answer.
• Chat Search searches across all your past conversations.
• Claude in Slack does the task when you tag @Claude in a thread (Claude Tag, on Team and Enterprise plans).
• Cowork Plugins are bundles of skills and connectors for Cowork.
• Cowork Projects group Cowork tasks into a persistent workspace.
• Incognito Chats are not saved to your chat history or memory and are not used for training.
• /teleport pulls a Claude web session down into the terminal.

What is the D tier, and why is it not an insult?

D tier is table-stakes and plumbing. Low here does not mean bad. These are real and useful, they are just nobody's favorite, because they are the floor that everything else stands on. Half of them you would only notice if they vanished.

• Memory Files (CLAUDE.md) is a file Claude reads every session to know your project.
• Context Lifecycle is /clear, /compact, and /resume to manage the conversation.
• Web Search has Claude search the web and cite its sources.
• Permissions control what Claude can do without asking.
• Fast Mode is faster Opus output at a higher cost per token, toggled with /fast.
• File Uploads drop in images, PDFs, and docs.
• Output Styles change how Claude formats its answers.
• Headless Mode runs Claude as a one-shot command in scripts.
• Sandboxed Bash runs shell commands safely in a sandbox.
• Transcript Viewer scrolls back through the whole session with Ctrl+O.
• History Search searches past prompts with Ctrl+R.
• Shell Mode runs a raw shell command with the ! prefix.
• Voice Dictation lets me talk instead of type with /voice.
• Custom Themes change the CLI color theme.
• IDE Extension puts Claude Code inside VS Code and JetBrains.
• Mobile Apps put Claude on iOS and Android.
• Code Review reviews my git diff with /code-review.

FAQ

What is the difference between Skills and Subagents? They solve different problems. Skills are folders with a SKILL.md file that teach Claude your own workflows, so you codify how you do a task once and it knows it from then on. Subagents are background agents you spin off, each in its own context window, to handle work in parallel with your main thread. Skills teach. Subagents delegate. In my ranking Skills sits at number two and Subagents at number seven, both because they remove me from the loop in different ways.

Do I need to know how to code to use these features? Not for a lot of them. Plenty of the highest-impact features are commands and toggles, like /goal to set a finish line, /loop to re-run a prompt on an interval, and Routines to run cloud agents on a schedule. There is also Cowork, a no-terminal agent desktop, and Voice Mode for spoken conversations, both built for people who do not want a terminal. The deeper, scriptable features like the Status Line and Hooks reward technical comfort, but you can get most of the walk-away benefit without writing code.

What does /goal actually do, and why is it ranked number one? You set a finish line, and Claude keeps working until that finish line is met. I ranked it number one because it is the purest version of the pattern that runs through my whole top tier. Instead of giving a prompt or setting an interval, you describe what done looks like and step away, and the tool works toward that outcome until it is true. Nothing changed my actual day more than handing over the finish line instead of the next instruction.

Why are Cowork and Voice Mode ranked so low if they are good features? Because my ranking lens is "how much does it change my day," and I work in the terminal and in automation. Cowork is a no-terminal desktop and Voice Mode is hands-free spoken conversation, and both are genuinely good. They just are not how I personally work, so they land in C tier for me. If you work in a desktop app or prefer talking over typing, you should mentally promote that whole tier. The low ranking is about fit, not quality.

What does it mean that the S-tier features "remove you from the loop"? It means they let the work continue without you sitting there feeding the next prompt. Routines run on a schedule with your laptop closed. /loop re-runs a prompt on an interval. Subagents and Agent Teams run in the background and in parallel. Remote Control lets you steer from your phone. Auto Memory learns your patterns on its own. The common thread is that the work keeps going while you are gone.

Will I disagree with this tier list? Probably, and that is fine. These are my opinions as someone who uses Claude for automation and knowledge work, ranked by my real day rather than by benchmarks or app-building. Your work is different, so your tiers will be different. The useful exercise is not to agree with me. It is to run the same test on your own work and see which features actually change your week.

---

I write about using AI for real work, not the hype version, here. If this is your kind of thing, read more on the blog, see what I actually do, and if you want help putting any of this to work in your own setup, get in touch. I answer.

Related: How long does it take to set up AI automation for a business?