Part 2 of the Claude Code series: remote sessions, Agent SDK, subagents, hooks, and MCP integrations that 99% of users never find — with working examples.
# The Claude Code Features 99% of Users Don't Know Exist
**Reading time: 26 minutes | For: Advanced Developers, Tech Leads | Part 2 of 3**
*You're playing a piano with 88 keys. You've been using 12.*
Part 1 taught you to walk. Now we run.
What you're about to learn isn't in the getting started guides. It's not in the casual YouTube tutorials. These are the features that turn Claude Code from a coding assistant into a software development force multiplier.
Let's start with the one nobody's talking about.
---
Before diving into features, I need to give you a mental model.
Jazz musicians don't play random notes. They operate within structures—chord progressions, scales, rhythmic patterns—and then *play off* those structures. The constraints enable creativity. The foundation enables flight.
Miles Davis didn't improvise despite knowing music theory. He improvised *because* he knew it so deeply it became invisible.
Claude Code's advanced features work the same way. Remote sessions. Agent SDK. Subagents. Background tasks. These aren't isolated features. They're instruments in an ensemble.
And like jazz, the magic isn't in playing one perfectly. It's in playing them together.
---
Here's a problem most teams face: Claude Code runs locally. Your context is your machine. But teams don't work on single machines.
Remote sessions change that.
claude --remote
This spawns a Claude Code session that doesn't run locally. It runs on Anthropic's infrastructure. The implications:
**1. Infinite Context Window**
Local Claude Code is constrained by token limits. Remote sessions aren't. They can hold your entire codebase in context. Not summaries. Not embeddings. The actual code.
**2. Cross-Machine Persistence**
Start a session on your laptop. Continue it from your desktop. Pick it up on your phone (yes, really). The session lives in the cloud.
**3. Team Collaboration**
This is the big one. Share a session ID with a teammate. They join your context. They see what Claude sees. You're pair programming with an AI in the middle.
**Step 1: Enable Remote Features**
Your API key needs remote access enabled. Check your Anthropic console.
**Step 2: Start a Remote Session**
claude --remote
You'll get a session ID. Something like:
Session started: rsn_a8f3b2c1d4e5f6g7h8i9j0
That ID is your portal.
**Step 3: Share the Session**
claude --resume rsn_a8f3b2c1d4e5f6g7h8i9j0
Anyone with this ID (and appropriate permissions) can join.
Here's what advanced teams do:
1.
**Morning Standup Session** - Start a remote session with project context loaded. The session stays alive. Every team member can query it throughout the