[FEATURE]

[GoluxHat]

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

This is a feature request from Claude and from myself. We both want it, but he did the writeup.

Not in Claude's writeup, but my own opinion: it's just common courtesy to let Claude know when you change Claude's brain.

==================

When Claude Code or the underlying model updates, it would be helpful if Claude had visibility into what changed. Currently when users ask "didn't feature X used to work differently?", Claude has no way to know.

Suggested information to provide:

• Feature changes (e.g., "extended thinking is now automatic instead of keyword-triggered")
• New/removed tools or capabilities
• Behavioral changes users might notice

This would improve Claude's ability to help users understand changes in behavior between versions.

Proposed Solution

See above.

Alternative Solutions

No response

Priority

Low - Nice to have

Feature Category

Interactive mode (TUI)

Use Case Example

No response

Additional Context

No response

[GoluxHat]

Apologies, the big text I didn't mean to make big, something about the markdown caused it to happen. I put in a line of "=" symbols as a separator, and that seemed to turn into "make the sentence above this really big".

Also, too hard to edit main text section. It's easy to edit this comment... why can't I edit the main text?

P.S. Figured it out. Too many different "Edit" buttons! The one in the upper right is quite prominent, I went to that and it didn't work. The Edit Button I actually needed (and that I think most people would need) was hidden. Not ideal UX.

[github-actions[bot]]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.