Claude Code Has 15 Power Features. I Was Using 3.
Most Claude Code users are running the tool the same way they ran their first code editor — with a fraction of its actual capability unlocked. A new post from dev.to, inspired by a Boris Cherny X thread cataloging features from the Claude Code engineering team itself, maps out all 15+ power features that the average developer skips entirely. The author's specific claim: dropping from roughly 15 manual context switches per hour to about 3 after adopting the full feature set. That's not a hypothetical efficiency gain — it's a concrete workflow change with a documented mechanism.
The features worth immediate attention: Teleport (--export/--import session.json) lets you move full sessions with context intact between machines, eliminating the 10–15 minutes of re-explaining that kills momentum when switching laptops or handing off to a colleague. Remote-Control lets a second terminal send commands to a running Claude session without interrupting state. /btw injects background context mid-session without breaking flow. --bare gives pipe-friendly output for scripted claude -p calls. The Chrome extension bridges browser-to-editor without copy-paste. Each of these is in the current v2.1.88 release but appears in almost no tutorials — they were designed for power users who go looking, not casual ones who don't.
The piece credits Boris Cherny's X thread directly as the discovery catalyst, which gives it direct lineage from the engineering team. For developers who feel like they've hit a ceiling with Claude Code's output quality or context management: the features in this list are almost certainly the gap, not the model itself.