[BUG] statusline-setup agent uses hardcoded developer path

Resolved 💬 4 comments Opened Feb 1, 2026 by evemcgivern Closed Mar 2, 2026

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?

Description

The statusline-setup agent attempts to read configuration from a hardcoded path /Users/jkrasnay/ instead of using the current user's home directory.

What Should Happen?

Expected Behavior

The agent should use the current user's home directory (e.g., /Users/evemcgivern/ or $HOME) to read shell configuration files.

Actual Behavior

The agent attempts to read from /Users/jkrasnay/, which:

  • Does not exist on the user's machine
  • Appears to be a hardcoded path from a developer's environment
  • Causes confusion and concern about unauthorized users on the system

Error Messages/Logs

Steps to Reproduce

Steps to Reproduce

  1. Run the /statusline command in Claude Code
  2. The agent attempts to configure statusline from shell PS1 configuration
  3. Agent tries to access /Users/jkrasnay/ instead of the actual user's home directory

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.29

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Environment

  • OS: macOS (Darwin 25.2.0)
  • User: evemcgivern
  • Command: /statusline → Task with subagent_type: "statusline-setup"
  • Date: 2026-02-01

Impact

  • Severity: Medium
  • Users cannot configure statusline settings
  • Creates false security concerns about unknown users
  • Suggests the agent has hardcoded paths instead of dynamic user detection

Suggested Fix

The agent should use environment variables or dynamic user detection:

  • Use $HOME or process.env.HOME
  • Use os.homedir() in Node.js
  • Use ~ with proper shell expansion
  • Never use hardcoded user paths like /Users/jkrasnay/

Additional Context

This was discovered while working on the CritForge project after completing documentation tasks. The tool use was rejected when the agent attempted to read from the incorrect path.

Error message received:

The user doesn't want to proceed with this tool use. The tool use was rejected

The agent should be updated to properly detect and use the current user's home directory across all supported platforms (macOS, Linux, Windows/WSL).

---

Note: The name "jkrasnay" suggests this might be John Krasnay's development machine path that was accidentally committed to the agent configuration.

View original on GitHub ↗

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