3 Claude Code updates this week and how to use them
A weekly radar that filters out the noise: Claude in Chrome, an automatic MCP connection fix, and a new dataviz skill.
What you get
A weekly filter of Claude Code updates down to three things that actually change how you work
Who it is for
For anyone already working with Claude Code who does not have time to read every line of the changelog.
Why this matters
Nobody has time to go through every line of the changelog. This weekly radar filters out the noise and leaves only the updates that actually change how you work.
Update 1: Claude in Chrome officially left beta
Claude can now navigate and act inside a real Chrome browser, not just read code. This is an official capability that moved from research preview to full availability.
- Let the agent check an interface it built itself, not just describe it.
- Useful for tasks that need real interaction with a site: testing a form, a login flow, confirming a page loaded correctly after a deploy.
- It is not a replacement for a dedicated testing automation tool (Playwright and so on) when you need stability and CI, but it is great for a quick manual check mid-conversation with the agent.
Update 2: MCP headersHelper reconnects on its own after a 401/403
If your MCP server returns an authorization error mid-run, Claude Code no longer gets stuck. The headersHelper reruns itself and reconnects automatically.
- If you work with MCP servers whose tokens expire and refresh (OAuth, short-lived tokens), this is exactly the fix for that pain.
- You do not need to do anything to turn this on, it is part of the tool's default behavior.
- If you are still getting repeated disconnects after the update, that is probably a sign of a different problem (wrong permissions, a token that does not refresh server-side), not the old bug.
Update 3: the /dataviz skill for designing dashboards and charts
A new skill that teaches Claude Code how to build charts and dashboards that look right, including a built-in color palette checker that actually runs.
- Run /dataviz when you are building an internal dashboard, a chart for a client presentation, or a data view inside an app.
- The color checker helps catch accessibility problems (weak contrast, colors that do not distinguish between categories) before the dashboard ships.
- Useful for internal projects and for code that generates charts for content.
How to use this now
Not every line in the changelog deserves attention. Check only what actually touches your workflow this week, and ignore the rest.