The frontier AI coding tools ship new capabilities almost daily and at least weekly. If you learned your tool a month ago and haven’t looked since, you might be missing features that could change how you work.

A few examples from the last week alone: Claude Code shipped /code-review –fix that auto-applies findings to your code, pinned background sessions that survive updates, and per-category cost breakdowns in /usage. GitHub Copilot added auto model selection that routes to the best model per task, granular memory controls with a /memory command, and Copilot for Eclipse went open source. That’s one week, two tools.

You don’t need to follow everything. But for your primary tool, find the one feed that tells you what changed:

Also: watch for events. Code with Claude London just happened (videos on YouTube). Microsoft Build is coming up. These often announce features before the changelog does.

Spend 10 minutes once a week scanning your tool’s changelog. That’s it. The compound effect of knowing what’s available — before you need it — is enormous. (You can even use your agent to update you!)

💡 Try this: Bookmark your primary tool’s changelog and check it next Monday morning. Note one thing you didn’t know existed. 🔗 github.blog/changelog/label/copilot/
🔗 code.claude.com/docs/en/whats-new

How do you keep up with tool changes?

🟢 Follow changelogs regularly
🟡 Hear about stuff from colleagues
🔴 Mostly discover features by accident
⚪ Don’t have time — just use what works

Found a feature recently that changed your workflow? Share it