[BUG] Bug Report: Claude Code v1.0.62

Bug Report: Claude Code v1.0.62

Environment

• Version: 1.0.62
• Platform: Windows (win32)
• Installation: npm global
• Node.js: 20
• First time user: Yes

Bug 1: @-mention File Tagging Issues

Description

As a new Claude Code user, I'm experiencing issues with the @-mention functionality for file tagging. While Claude seems to understand what I'm referring to when I mention files, the auto-completion feature is not working properly.

Expected Behavior

• When typing @, I should see auto-completion suggestions for files in my project
• I should be able to easily reference files using the @-mention syntax
• The feature should work as documented

Actual Behavior

• No auto-completion appears when typing @
• Cannot properly utilize the @-mention functionality
• Claude understands file references but the UX is broken

Steps to Reproduce

1. Start Claude Code in a project directory
2. Type @ in the chat
3. Expect to see file suggestions
4. No auto-completion appears

Bug 2: Custom Slash Commands Not Working (v1.0.62)

Description

Custom slash commands created in .claude/commands/ directory are not being recognized or executed in version 1.0.62, despite following the documentation correctly.

Expected Behavior

• Custom .md files in .claude/commands/ should appear as available slash commands
• Commands should be listed in /help
• Commands should be executable using /command-name

Actual Behavior

• Custom commands do not appear in /help output
• Cannot execute custom commands (e.g., /test, /simple)
• Commands are completely ignored by the CLI

Steps to Reproduce

1. Create .claude/commands/ directory in project root
2. Add custom command files (e.g., test.md, simple.md) with proper markdown format
3. Restart Claude Code
4. Run /help - custom commands are not listed
5. Try to execute /test - command not found

File Structure Created

.claude/
└── commands/
    ├── test.md
    └── simple.md

Sample Command File (simple.md)

# Commande simple

Ceci est une commande de test simple.

Exécuter : `git status`

Workaround Found

• Downgrading to version 1.0.61 resolves the issue
• Custom commands work perfectly in v1.0.61
• This suggests a regression introduced in v1.0.62

Impact

• @-mention bug: Severely impacts file referencing workflow for new users
• Custom commands bug: Prevents utilization of custom automation workflows
• Both issues significantly degrade the user experience

Additional Notes

The custom slash commands bug appears to be a regression specifically in v1.0.62, as the same setup works flawlessly in v1.0.61. This suggests the recent changes in v1.0.62 may have broken the custom command loading mechanism.

Requested Actions

1. Fix @-mention auto-completion functionality
2. Investigate and fix custom slash commands regression in v1.0.62
3. Consider adding better error messages/debugging for custom command loading issues