The Best Claude Code Features You Didn't Know Exist

Claude Code has a bunch of amazing features you’ve probably never used.

These features can not only save you time and effort, but they can also make it more fun to vibe code.

In this post, we’ll cover our top seven hidden (or lesser-known) Claude Code features.

1. Remote Control

Remote Control lets you access a Claude Code session on your computer from your phone, tablet, or browser.

Run claude remote-control (or --remote-control, or /remote-control from inside a session you’ve already started), and you get a session URL and a QR code you can scan with the Claude mobile app.

Your code, your files, and the actual execution stay on your computer the whole time. The phone/browser are just a window into that session.

If a long task is still running when you leave your desk, Claude can send a push notification when it finishes, or when it needs a decision from you.

2. Dynamic Workflows

Type the word ultracode anywhere in a prompt, or just ask in plain English (“use a workflow to…”), and Claude Code stops working turn by turn.

Instead, it writes a JavaScript script that describes the job as a series of steps, and hands it to a separate runtime. The runtime then executes the script in the background while your session stays free to keep chatting.

These dynamic workflows can run up to 1,000 of subagents across a single job, each auditing one file or verifying another agent’s finding before it gets reported to you.

Anthropic’s own example is a codebase-wide sweep for a specific bug pattern:

Use /workflows to see each step, how many agents are running, and what they found.

3. Cross-Session Messaging

Your Claude Code sessions can message each other. If you’ve got one session running in a terminal and another running in a different directory (or even on a different machine!), one of them can send the other a message, without you having to copy-paste anything.

So, if you enter: “The API generator session should follow the same convention that I shared above,” Claude figures out which of your other sessions answers to “API generator,” and delivers the message there directly.

This is great for keeping separate sessions aligned even when you are using them to work on different parts of a project.

4. Dispatch

To invoke Remote Control, you need a session already running on your machine. With Dispatch, you don’t.

Dispatch is a special chat in Claude Desktop’s Cowork tab where you can send Claude a message to start a task remotely.

For example, if you text it: “Open a Claude Code session and fix the login bug.” then Dispatch:

• Recognizes that as development work
• Spins up a real Claude Code session on your machine to handle it
• Tags it with a Dispatch badge in the sidebar
• Pushes a notification to your phone the moment it finishes or needs a decision from you.

5. Channels

Channels push outside events straight into an existing Claude Code session.

Install a plugin, connect your bot, and anything you send to the bot will appear in your running Claude Code session. Claude’s replies will come back through that same bot chat.

So, for example, you type a question into your Telegram bot: “What’s failing in the build?” Claude picks it up inside a running Claude Code session, checks the relevant files, and responds in that same Telegram chat.

It can also receive webhook alerts, so something like a CI failure can go straight into the Claude Code session that already has the right project context.

6. Fast Mode

Fast Mode is not a smaller or dumber model standing in for Opus. It’s the same Opus model, using a different backend configuration that trades cost efficiency for speed. Toggle it with /fast, then Tab.

But know this before enabling it: the first message after you enable Fast Mode bills your entire existing conversation at the fast-mode rate, not just the new message.

So, if you enable it three hours into a long debugging session, you pay fast-mode prices for those three hours of accumulated context.

Fast Mode is best for live debugging and rapid iteration, where faster responses are worth the extra cost. For longer unattended tasks, it usually makes more sense to leave it off.

7. Custom Keybindings

Run /keybindings and Claude Code opens (or creates) the keybindings JSON file.

From there, you can customize shortcuts for almost every action across 19 different contexts, including chat input, autocomplete, the transcript viewer, and the diff dialog.

It supports proper chord sequences too, not just single keystrokes: e.g., you can bind an action to ctrl+k ctrl+s (press Ctrl+K, release, then Ctrl+S).

This gives you much more control over how you navigate and work inside Claude Code.

Wrapping Up

Claude Code is one of the best things to happen to software development in many years.

The features the Anthropic team keep on adding continue to make vibe coding more convenient and accessible.

But remember, human oversight and care still remain important, for more reasons than one.