[BUG] Incorrect User Path in statusline-setup Agent

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?

The statusline-setup agent incorrectly generated/referenced a non-existent Windows user path (C:\Users\jdg11) instead of the actual user path (C:\Users\sarah) when attempting to configure the statusLine in VSCode with PowerShell on Windows.

What Should Happen?

Expected Behavior

The statusline-setup agent should have:

1. Correctly detected the actual Windows user (sarah)
2. Used the correct path C:\Users\sarah
3. Or prompted for the correct user path if detection failed

Error Messages/Logs

Steps to Reproduce

Reproduction Steps

1. User opened Claude Code in VSCode with PowerShell terminal
2. User ran /statusline command to configure statusLine
3. User was prompted with: "statusline is setting up statusLine..."
4. Agent attempted to configure statusLine from shell PS1 configuration
5. BUG: Agent generated code referencing C:\Users\jdg11 path
6. User rejected the tool use due to unknown user reference
7. User asked "So what user is jdg11?"

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

1.0.77 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Claude Code Bug Report: Incorrect User Path in statusline-setup Agent

Bug Summary

The statusline-setup agent incorrectly generated/referenced a non-existent Windows user path (C:\Users\jdg11) instead of the actual user path (C:\Users\sarah) when attempting to configure the statusLine in VSCode with PowerShell on Windows.

Environment

• OS: Windows (Windows 11/10)
• Shell: PowerShell in VSCode
• Claude Code Version: Current as of October 13, 2025
• Working Directory: D:\Coding Projects\conspirapin-new
• Actual Windows User: sarah (C:\Users\sarah)
• Incorrectly Referenced User: jdg11 (C:\Users\jdg11 - does not exist)

Reproduction Steps

1. User opened Claude Code in VSCode with PowerShell terminal
2. User ran /statusline command to configure statusLine
3. User was prompted with: "statusline is setting up statusLine..."
4. Agent attempted to configure statusLine from shell PS1 configuration
5. BUG: Agent generated code referencing C:\Users\jdg11 path
6. User rejected the tool use due to unknown user reference
7. User asked "So what user is jdg11?"

Expected Behavior

The statusline-setup agent should have:

1. Correctly detected the actual Windows user (sarah)
2. Used the correct path C:\Users\sarah
3. Or prompted for the correct user path if detection failed

Actual Behavior

The agent incorrectly referenced a non-existent user path C:\Users\jdg11 in the generated code.

Security Investigation Performed

After the user raised security concerns, the following checks were performed to ensure system security:

1. Windows User Account Check

net user

Result: Only legitimate accounts present (sarah, Administrator, DefaultAccount, Guest, WDAGUtilityAccount)

2. C:\Users Directory Check

ls C:\Users

Result: No jdg11 directory exists. Only sarah, Default, Public, and system directories present.

3. WMI User Account Query

wmic useraccount where "Name='jdg11'" get Name,SID,Status

Result: "No Instance(s) Available" - User does not exist

4. Direct Directory Access Test

dir C:\Users\jdg11

Result: "No such file or directory" - Confirms directory doesn't exist

5. Environment Variable Check

set | findstr jdg11

Result: No environment variables reference jdg11

6. Git History Check

git log --all --format="%H %an %ae%n%B" | grep -B2 -A2 "jdg11"

Result: No git commits reference jdg11 (all commits correctly show "Co-Authored-By: Claude <noreply@anthropic.com>")

Conclusion

• No security breach occurred - The jdg11 user does not exist on the system
• This appears to be a bug in the statusline-setup agent's user detection logic
• The agent somehow generated/hallucinated an incorrect user path
• User correctly rejected the tool use preventing any potential issues

Impact

• User concern about potential security breach
• Unable to complete statusLine configuration
• Trust impact - user questioned if unauthorized access occurred

Suggested Fix

1. Improve user detection logic in statusline-setup agent for Windows systems
2. Add validation to ensure detected paths actually exist before using them
3. Fallback to prompting user for correct path if detection fails
4. Add logging for how user paths are determined for debugging

Additional Notes

• The mysterious "jdg11" username appears to be completely fabricated by the agent
• GitHub user jdg11 (ID: 167076405) exists but is unrelated to this issue
• No actual files or configurations were modified due to user rejecting the tool use

Conversation Timeline

1. User attempts to configure statusLine
2. Agent tries to detect PS1 configuration
3. Agent generates code with incorrect C:\Users\jdg11 path (REJECTED)
4. User asks about jdg11 user
5. Assistant incorrectly claims jdg11 appears in git commits (error - no such commits exist)
6. User corrects assistant - noting they are the only one besides Claude co-authoring
7. Assistant realizes error and investigates
8. Security investigation performed - system confirmed secure
9. Bug identified as agent error in path detection

Reproducibility

Unknown - the bug may be intermittent or specific to certain Windows configurations. The statusline-setup agent's user detection logic needs investigation.

---

Report Generated: October 13, 2025
Reported By: Sarah Cox (sarah.cox@gmail.com)
Project: conspirapin-new
System: Windows with PowerShell in VSCode