[BUG]

Preflight Checklist

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

What's Wrong?

GitHub Issue: Slash commands not discovered in non-elevated terminal on Windows
Repository: https://github.com/anthropics/claude-code/issues

Title: Slash commands not discovered in non-elevated terminal on Windows

Labels: bug, windows

Description
Slash commands in .claude/commands/ are not being discovered when running Claude Code from a non-elevated terminal on Windows, but they work correctly when running from an elevated PowerShell session.

Environment
OS: Windows 10 Build 26100
PowerShell Version: 5.1.26100.6899
Claude Code Version: 2.0.25
Terminal Context: JetBrains Rider integrated terminal (non-elevated)
Number of slash commands: 31 command files in .claude/commands/

Actual Behavior
In elevated PowerShell: All 31 slash commands are discovered and available
In Rider integrated terminal (non-elevated): No project-level slash commands are discovered
Additional Context
File permissions verified:
.claude\commands NT AUTHORITY\SYSTEM:(I)(OI)(CI)(F)
BUILTIN\Administrators:(I)(OI)(CI)(F)
AMPNETWORK\shane.erben:(I)(OI)(CI)(F)
File accessibility verified:
All 31 .md files are readable from the current user context
Working directory is correct (C:\Users\shane.erben\Documents\Cerebro)
.claude/commands path resolves correctly (Test-Path returns True)
Files have proper YAML frontmatter with description field
Sample command file structure:
---
description: Simple test command
---

Say "Hello! This is a test slash command and it's working!"
Claude Code global config:
User-level directory exists at C:\Users\shane.erben\.claude\
No user-level commands folder (all commands are project-level)
Project has .claude/settings.local.json with MCP server configuration
Workaround
Running JetBrains Rider as Administrator allows slash commands to be discovered in the integrated terminal, but this is not an ideal solution for day-to-day development workflow.

Impact
This issue prevents developers from using project-level slash commands in their normal IDE workflow on Windows unless they run their IDE with elevated privileges, which is not recommended for security and usability reasons.

What Should Happen?

Expected Behavior
Slash commands should be discovered and available regardless of whether the terminal session is elevated or not, as long as:

Files have correct permissions
Files are in the correct location (.claude/commands/)
Files have proper frontmatter with description field

Error Messages/Logs

Steps to Reproduce

Steps to Reproduce
Create a .claude/commands/ directory in a project with properly formatted slash command files (with description frontmatter)
Open the project in JetBrains Rider
Launch Claude Code from Rider's integrated terminal (non-elevated)
Type / and observe available commands
Compare with running Claude Code from an elevated PowerShell session

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.0.25 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_