Is there a way to subscribe to Claude Code updates via RSS or a webhook? I found this website, but it doesn't seem to offer anything.
https://claudelog.com/claude-code-changelog/

Claude Code CLI 2.0.73 changelog:

• Added clickable [Image #N] links that open attached images in the default viewer.

• Added alt-y yank-pop to cycle through kill ring history after ctrl-y yank.

• Added search filtering to the plugin discover screen (type to filter by name, description, or marketplace).

• Added support for custom session IDs when forking sessions with --session-id combined with --resume or --continue and --fork-session

• Fixed slow input history cycling and race condition that could overwrite text after message submission.

• Improved /theme command to open theme picker directly.

• Improved theme picker UI.

• Improved search UX across resume session, permissions, and plugins screens with a unified SearchBox component.

• [VSCode] Added tab icon badges showing pending permissions (blue) and unread completions (orange).

Source: Anthropics Claude Code(GitHub)

Claude Code CLI 2.0.70 changelog:

• Added Enter key to accept and submit prompt suggestions immediately (tab still accepts for editing)

• Added wildcard syntax mcp__server__* for MCP tool permissions to allow or deny all tools from a server.

• Added auto-update toggle for plugin marketplaces, allowing per-marketplace control over automatic updates.

• Added plan_mode_required spawn parameter for teammates to require plan approval before implementing changes.

• Added current_usage field to status line input, enabling accurate context window percentage calculations.

• Fixed input being cleared when processing queued commands while the user was typing.

• Fixed prompt suggestions replacing typed input when pressing Tab.

• Fixed diff view not updating when terminal is resized.

• Improved memory usage by 3x for large conversations.

• Improved resolution of stats screenshots copied to clipboard (Ctrl+S) for crisper images.

• Removed # shortcut for quick memory entry (tell Claude to edit your CLAUDE.md instead).

• Fix thinking mode toggle in /config not persisting correctly.

• Improve UI for file creation permission dialog.

Source: Anthropics (GitHub)

🔗: https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md

🔗: https://code.claude.com/docs/

I updated my Claude Code guide with all the December 2025 features (Opus 4.5, Background Agents)

Hey everyone! A number of weeks ago I shared my comprehensive Claude Code guide and got amazing feedback from this community. You all had great suggestions and I've been using Claude Code daily since then.

With all the incredible updates Anthropic shipped in November and December, I went back and updated everything. This is a proper refresh, not just adding a changelog - every relevant section now includes the new features with real examples.

What's actually new and why it matters

But first - if you just want to get started: The repo has an interactive jumpstart script that sets everything up for you in 3 minutes. Answer 7 questions, get a production-ready Claude Code setup. It's honestly the best part of this whole thing. Skip to "Installation" below if you just want to try it.

Claude Opus 4.5 is genuinely impressive

The numbers don't lie - I tested the same refactoring task that used to take 50k tokens and cost $0.75. With Opus 4.5 it used 17k tokens and cost $0.09. That's 89% savings. Not marketing math, actual production usage.

More importantly, it just... works better. Complex architectural decisions that used to need multiple iterations now nail it first try. I'm using it for all planning now.

Named sessions solved my biggest annoyance

How many times have you thought "wait, which session was I working on that feature in?" Now you just do /rename feature-name and later claude --resume feature-name. Seems simple but it's one of those quality-of-life things that you can't live without once you have it.

Background agents are the CI/CD I always wanted

This is my favorite. Prefix any task with & and it runs in the background while you keep working:

& run the full test suite
& npm run build
& deploy to staging

No more staring at test output for 5 minutes. No more "I'll wait for the build then forget what I was doing." The results just pop up when they're done.

I've been using this for actual CI workflows and it's fantastic. Make a change, kick off tests in background, move on to the next thing. When tests complete, I see the results right in the chat.

What I updated

Six core files got full refreshes:

• Best Practices Guide - Added Opus 4.5 deep dive, LSP section, named sessions, background agents, updated all workflows

• Quick Start - New commands, updated shortcuts, LSP quick ref, troubleshooting

• Sub-agents Guide - Extensive background agents section (this changes a lot of patterns)

• CLAUDE.md Template - Added .claude/rules/ directory, December 2025 features

• README & CHANGELOG - What's new section, updated costs

The other files (jumpstart automation script, project structure guide, production agents) didn't need changes - they still work great.

The jumpstart script still does all the work

If you're new: the repo includes an interactive setup script that does everything for you. You answer 7 questions about your project (language, framework, what you're building) and it:

• Creates a personalized CLAUDE.md for your project

• Installs the right agents (test, security, code review)

• Sets up your .claude/ directory structure

• Generates a custom getting-started guide

• Takes 3 minutes total

I put a lot of work into making this genuinely useful, not just a "hello world" script. It asks smart questions and gives you a real production setup.

The "Opus for planning, Sonnet for execution" workflow

This pattern has become standard in our team:

1. Hit Shift+Tab twice to enter plan mode with Opus 4.5

2. Get the architecture right with deep thinking

3. Approve the plan

4. Switch to Sonnet with Alt+P (new shortcut)

5. Execute the plan fast and cheap

Plan with the smart expensive model, execute with the fast cheap model. Works incredibly well.

Installation is still stupid simple

The jumpstart script is honestly my favorite thing about this repo. Here's what happens:

git clone https://github.com/jmckinley/claude-code-resources.git
cd claude-code-resources
./claude-code-jumpstart.sh

Then it interviews you:

• "What language are you using?" (TypeScript, Python, Rust, Go, etc.)

• "What framework?" (React, Django, FastAPI, etc.)

• "What are you building?" (API, webapp, CLI tool, etc.)

• "Testing framework?"

• "Do you want test/security/review agents?"

• A couple more questions...

Based on your answers, it generates:

• Custom CLAUDE.md with your exact stack

• Development commands for your project

• The right agents in .claude/agents/

• A personalized GETTING_STARTED.md guide

• Proper .claude/ directory structure

Takes 3 minutes. You get a production-ready setup, not generic docs.

If you already have it: Just git pull and replace the 6 updated files. Same names, drop-in replacement.

What I learned from your feedback

Last time many of you mentioned:

"Week 1 was rough" - Added realistic expectations section. Week 1 productivity often dips. Real gains start Week 3-4.

"When does Claude screw up?" - Expanded the "Critical Thinking" section with more failure modes and recovery procedures.

"Give me the TL;DR" - Added a 5-minute TL;DR at the top of the main guide.

This community gave me great feedback and I tried to incorporate all of it.

Things I'm still figuring out

Background agents are powerful but need patterns - I'm still learning when to use them vs when to just wait. Current thinking: >30 seconds = background, otherwise just run it.

Named sessions + feature branches need a pattern - I'm settling on naming sessions after branches (/rename feature/auth-flow) but would love to hear what others do.

Claude in Chrome + Claude Code integration - The new Chrome extension (https://claude.ai/chrome) lets Claude Code control your browser, which is wild. But I'm still figuring out the best workflows. Right now I'm using it for:

• Visual QA on web apps (Claude takes screenshots, I give feedback)

• Form testing workflows

• Scraping data for analysis

But there's got to be better patterns here. What I really want is better integration between the Chrome extension and Claude Code CLI for handling the configuration and initial setup pain points with third-party services. I use Vercel, Supabase, Stripe, Auth0, AWS Console, Cloudflare, Resend and similar platforms constantly, and the initial project setup is always a slog - clicking through dashboards, configuring environment variables, setting up database schemas, connecting services together, configuring build settings, webhook endpoints, API keys, DNS records, etc.

I'm hoping we eventually get to a point where Claude Code can handle this orchestration - "Set up a new Next.js project on Vercel with Supabase backend and Stripe payments" and it just does all the clicking, configuring, and connecting through the browser while I keep working in the terminal. The pieces are all there, but the integration patterns aren't clear yet.

Same goes for configuration changes after initial setup. Making database schema changes in Supabase, updating Stripe webhook endpoints, modifying Auth0 rules, tweaking Cloudflare cache settings, setting environment variables across multiple services - all of these require jumping into web dashboards and clicking around. Would love to just tell Claude Code what needs to change and have it handle the browser automation.

If anyone's cracked the code on effectively combining Claude Code + the Chrome extension for automating third-party service setup and configuration, I'd love to hear what you're doing. The potential is huge but I feel like I'm only scratching the surface.

Why I keep maintaining this

I built this because the tool I wanted didn't exist. Every update from Anthropic is substantial and worth documenting properly. Plus this community has been incredibly supportive and I've learned a ton from your feedback.

Also, honestly, as a VC I'm constantly evaluating technical tools and teams. Having good docs for the tools I actually use is just good practice. If I can't explain it clearly, I don't understand it well enough to invest in that space.

Links

GitHub repo: https://github.com/jmckinley/claude-code-resources

You'll find:

• Complete best practices guide (now with December 2025 updates)

• Quick start cheat sheet

• Production-ready agents (test, security, code review)

• Jumpstart automation script

• CLAUDE.md template

• Everything is MIT licensed - use however you want

Thanks

To everyone who gave feedback on the first version - you made this better. To the r/ClaudeAI mods for letting me share. And to Anthropic for shipping genuinely useful updates month after month.

If this helps you, star the repo or leave feedback. If something's wrong or could be better, open an issue. I actually read and respond to all of them.

Happy coding!

Not affiliated with Anthropic. Just a developer who uses Claude Code a lot and likes writing docs.

It's a pretty well known tip at this point that to get the most out of Claude you need to do 2 things:

1. Don't let the context window get too big. The more prompts you have in a single session the more performance declines, so clear the context often.

2. Claude needs necessary context on what has happened before in the project for optimal results. You should maintain a memory bank i.e. a CHANGELOG.md file that allows fresh conversations to be contextually aware of code history.

(If you haven't heard this before, there are some good details in this post)

My question is has anyone figured out good tips on how to work with a "memory bank" like this? E.g. what information should it contain? How long do you let it get before compacting it? Do you keep it going indefinitely, or just for a specific feature? How do you decide what goes in CHANGELOG.md vs CLAUDE.md? How do you instruct a fresh Claude session to read the context? etc.

I have been doing this myself and after a couple days of working the file is over 1000 lines long with 33k characters. Claude is putting a ton of information for each updated like summary of changes, bugs encountered and how they were fixed, code examples, implementation details, testing status, etc. It's not easy to tell how much this is helping. I'm wondering how much information is too much? Has anyone who is using this workflow figured out the optimal info to store?

My changelog process was absolute hell. Every month I'd spend 3+ hours digging through commits, coordinating with engineers, figuring out what users actually care about. Classic "should take 20 minutes but somehow takes all afternoon" situation.

Got fed up last week and decided to be lazy. I just dumped below prompt in claude code:

"I want to create user focused changelog for my product core. Changelog should be for august month. Take all releases made in aug as input data for aug changelog. Search from core memory for guidelines on creating a user-focused changelog and follow that"

It chewed through 47 commits, separated user-facing stuff from backend nonsense, and gave me clean copy in 3 minutes. The wild part? It already knew my formatting preferences from previous work.

Now I'm using it for documentation reviews, architecture summaries, and random content tasks. These coding agents are ridiculously good at any "read a bunch of stuff and make sense of it" workflow.

What other non-coding uses have people found?

[EDIT: Adding this info to provide more info about my claude code setup.

I'd used claude code on this project for july's changelog last month, where I had to explain the structure multiple times. But that whole conversation got stored in memory, so this time it just recalled those guidelines automatically.

My claude setup has 2 sub-agents as well:

1. memory-search agent - pulls relevant context from core-mcp for each task

2. memory-ingest agent - auto-saves summaries back to memory so it builds up project knowledge over time

Setup guide is here if useful: https://docs.heysol.ai/providers/claude-code

So not vanilla claude code prompt, but the memory mcp helped to smoothly get this time around."

Also the final changelog output on website, was further edited to add few things, but still the time taken drastically reduced.]

Version 1.0.24:
• Improved /mcp output
• Fixed a bug where settings arrays got overwritten instead of merged

Version 1.0.25:
• Slash commands: moved "project" and "user" prefixes to descriptions
• Slash commands: `improved reliability for command discovery`
• Improved support for Ghostty
• Improved web search reliability

Finally My Slash Commands are working again, I never did the delete my whole config reset trick... I just awaited the official patch and here we are! Thank you Anthropic.

PSA: Maybe it is just me but there is a new /permissions Slash Command UX and it is feels great!

Guys, do reprot back on the improved web search reliability, happy coding.

Salut,

Quelqu'un sait pourquoi le changelog manque 9 versions ?

https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md

Only see the release notes until 1.0.54? Curious to what was implemented

Salut les gars,

Je viens de créer une GitHub Action qui utilise Claude Code pour générer automatiquement des changelogs pour vos projets.

Au lieu d'écrire manuellement les notes de version, cette action prend votre historique de commits et produit un changelog propre et structuré avec l'aide de Claude Code. Parfait pour simplifier les flux de travail de publication et maintenir une documentation cohérente.

Si ça vous intéresse, voici le repo : https://github.com/mistricky/ccc ♥️

I have been using this for a few months now and have had very good results. It only works on Mac right now (so fork it, fix, it is open sourced) and works great with Ruby on Rails. I know it is a terrible name but that is the name Claude chose for it!

https://github.com/brobertsaz/claude-os

Read more about it https://thebob.dev/ai/tools/productivity/2025/10/31/why-we-built-claude-os-and-what-it-actually-is/

🚀 What is Claude OS?

Claude OS is Claude Code's personal memory system - making AI the best coding assistant in the universe by remembering everything across sessions.

The Problem

You work with Claude Code on a feature, close the terminal, come back tomorrow... and Claude forgot everything. You explain the same architecture. You reference the same files. You repeat yourself constantly.

The Solution

Claude OS gives Claude persistent memory:

• 📝 Remembers decisions across all sessions

• 🔍 Searches past work automatically at session start

• 📚 Indexes your docs and makes them searchable

• 🧠 Learns patterns that improve over time

• 🔄 100% Local - Never leaves your machine, fully private

Please check it out and if you want to make changes, PR it :)

The changelog is outdated:
👉 https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md → 1.0.11
👉 Latest version on npm: https://www.npmjs.com/package/@anthropic-ai/claude-code/v/1.0.16

Please update it to reflect recent changes 🙏

Line 5 seems like a pretty big deal to me. Any reports of how it works and how Code performs in general after the past few releases?

iirc yesterday claude code updated from 1.0.44 to 1.0.45 and today, running the same update command, it decides to 'update' from 1.0.45 to 1.0.44

hope am not hallucinating..

I called /init when starting to work and noticed the CLAUDE.md file that was generated.

After heavily working on the repo for a week - often also using CC - the code base drastically changed and expanded. However, CC never touched the CLAUDE.md file again. Can it help to call /init again after some time.

Also I noticed when I restart CC, any past chats are gone. This seems like a nice feature in a way, as I guess the model is better focused on the new topic rather than the previous history blurring the input. But it might be nice if some crucial details that might have come up in a previous session were still there. Any advice?