Bug Description
The /agents slash command returns no output even when agent markdown files are properly stored in ~/.claude/agents/.
Steps to Reproduce
- Create agent markdown files with proper YAML frontmatter in
~/.claude/agents/
- Run the
/agents command in Claude Code
- Command returns "(no content)" instead of listing available agents
Expected Behavior
The /agents command should display a list of available agents stored in ~/.claude/agents/
Actual Behavior
The command returns no output, showing "(no content)"
Current Workaround
Agents can still be invoked directly using the Task tool with "Use the [agent-name] agent to..." syntax, so functionality is preserved but discovery is broken.
Environment
- Platform: macOS Darwin 24.5.0
- Claude Code version: Latest as of 2025-08-06
- Agent files location:
~/.claude/agents/
- Agent files present:
- blockchain-engineer.md
- pr-reviewer.md
- pr-reviewer-monitor.md
- product-manager.md
- qa-tester.md
- security-reviewer.md
- senior-dev.md
- ux-designer.md
Additional Context
- All agent files have proper YAML frontmatter with
name: and description: fields
- Tried creating an
agents.json manifest file in ~/.claude/ but this didn't resolve the issue
- Agents work when invoked directly through the Task tool
Bug Description
The
/agentsslash command returns no output even when agent markdown files are properly stored in~/.claude/agents/.Steps to Reproduce
~/.claude/agents//agentscommand in Claude CodeExpected Behavior
The
/agentscommand should display a list of available agents stored in~/.claude/agents/Actual Behavior
The command returns no output, showing "(no content)"
Current Workaround
Agents can still be invoked directly using the Task tool with "Use the [agent-name] agent to..." syntax, so functionality is preserved but discovery is broken.
Environment
~/.claude/agents/Additional Context
name:anddescription:fieldsagents.jsonmanifest file in~/.claude/but this didn't resolve the issue