[FEATURE] spinnerVerbs in Claude VS Code Extendsion.

Resolved 💬 2 comments Opened Feb 6, 2026 by IanM-33 Closed Feb 6, 2026

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

There's no VSCode setting to make the extension read the spinnerVerbs config. The available claudeCode.* settings in VSCode (like preferredLocation, environmentVariables, etc.) don't include anything for spinner verbs.

The VSCode extension's UI is a webview that renders its own loading states - it doesn't use the same terminal-based spinner that the CLI does, so there's no hook point for those custom verbs.

Proposed Solution

Get the VSCode Extension to read the same settings that the CLI does to show custom spinnerVerbs.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

I configured custom spinnerVerbs in ~/.claude/settings.json with "mode": "replace" and a list of custom verbs. These work perfectly in the CLI — the spinner cycles through my custom verbs while processing. However, when using Claude Code through the VSCode extension, the custom verbs don't appear anywhere. The extension seems to have its own loading/status UI that doesn't read the spinnerVerbs setting.

It would be great if the VSCode extension respected the same spinnerVerbs configuration from settings.json, either in the status bar text, the inline loading indicator, or wherever the extension shows processing state. This would give users a consistent, personalized experience across both the CLI and VSCode extension.

Additional Context

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗