[BUG] Typo in workspace trust warning: "untusted" should be "untrusted"

Open Beginner friendly
#92,931 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
92/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
vscode
Domain
frontend

Research direction

Search the repository for the exact misspelled text "untusted workspaces are not supported" and inspect the VS Code extension footer warning where it appears. Correct the spelling to "untrusted workspaces are not supported" and verify the extension detail page displays the revised message.

Written by the indexing model from the issue text.

Description

area:ide bug platform:vscode
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?

The extension footer displays a typo in its workspace trust warning message: it reads "untusted workspaces are not supported" instead of "untrusted workspaces are not supported." The word Untrusted is spelled incorectly.

What Should Happen?

The message should read "untrusted workspaces are not supported."

Error Messages/Logs
N/A
Steps to Reproduce
  1. Open the Extensions panel in VS Code
  2. View the "Claude Code for VS Code" extension detail page
  3. Observe the warning text below the Enable/Uninstall buttons
Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.263

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information
Image
Dominant language
TypeScript
Stars
147k
Forks
24k
Avg merge
8h 14m
Merged PRs (30d)
18

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from anthropics/claude-code

All issues in anthropics/claude-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.