claude-code - 💡(How to fix) Fix [BUG] Plan acceptance does not auto-rename session when using Vertex AI provider [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#45274Fetched 2026-04-09 08:09:11
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×4commented ×1

Error Message

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

When accepting a plan in plan mode, the session should auto-rename based on the plan content. This works correctly on a personal Claude subscription account but does NOT work when using Claude Code via Vertex AI (API key mode).

Environment:

  • Claude Code version: 2.1.96
  • Provider: Vertex AI (Google Cloud)
  • OS: macOS (Darwin 25.4.0)
  • Same version on personal subscription account works correctly

What Should Happen?

Session auto-renames based on plan content (as it does on subscription-based accounts)

Error Messages/Logs

Steps to Reproduce

  1. Use Claude Code v2.1.96 connected via Vertex AI
  2. Enter plan mode and create a plan
  3. Accept the plan
  4. Observe: session name does not update — stays as the default

Claude Model

None

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.96

Platform

Google Vertex AI

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

Investigate differences in configuration or API behavior between personal Claude subscription accounts and Vertex AI (API key mode) to resolve the session auto-rename issue.

Guidance

  • Verify that the Vertex AI setup is correctly configured to support session auto-rename based on plan content, comparing settings with the working personal subscription account.
  • Check the API documentation for Vertex AI to ensure that the auto-rename feature is supported and properly implemented in the Claude Code version 2.1.96.
  • Test the session auto-rename feature with a minimal plan content to isolate if the issue is content-specific or a general configuration problem.
  • Compare the API requests and responses between the personal subscription account and the Vertex AI setup to identify any differences that could cause the auto-rename feature to fail.

Example

No specific code example can be provided without more details on the API or configuration differences between the two environments.

Notes

The issue might be specific to the integration with Vertex AI or how Claude Code handles API key mode versus personal subscription accounts. Without more logs or error messages, it's challenging to provide a precise fix.

Recommendation

Apply workaround: Investigate and adjust the Vertex AI configuration to match the personal subscription account settings as closely as possible, focusing on settings related to plan mode and session naming. This approach is recommended because it allows for a targeted adjustment to the potentially problematic configuration without requiring an upgrade or significant code changes.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING