[Feature Request] Customizable Plugin Display Names via marketplace.json
Resolved 💬 3 comments Opened Jan 15, 2026 by BenGWeeks Closed Feb 27, 2026
Feature Request: Customizable Plugin Display Names
Reference: https://github.com/T-Minus-15/claude-plugins
Current Behavior
Agent namespaces show verbose, redundant paths:
t-minus-15-team:poppie:agents:poppie (agent)
Desired Behavior
Allow plugins to define a friendly display name in marketplace.json:
T-Minus-15 Team: Poppie the Planner (Agent) - Project Manager and team orchestrator
Suggested Implementation
Add display_name field to .claude-plugin/marketplace.json (snake_case to match existing properties):
{
"name": "t-minus-15-team",
"display_name": "T-Minus-15 Team",
"description": "AI agents for the software development lifecycle",
"plugins": [...]
}
Display format:
{display_name}: {name} (Agent) - {description}
Where:
display_namecomes frommarketplace.jsonnamecomes from the agent definition (e.g., "Poppie the Planner")descriptioncomes from the agent definition
If display_name is not set, fall back to title-cased version of the name field.
Why This Matters
- Current namespaces expose internal folder structure to users
- Redundant path segments (e.g., "poppie" appearing twice) are confusing
- Plugin authors want professional, branded agent presentations
- Users benefit from clear, human-readable agent identification
Example Transformation
| Current | Proposed |
|---------|----------|
| t-minus-15-team:poppie:agents:poppie | T-Minus-15 Team: Poppie the Planner |
| my-plugin:helper:agents:helper | My Plugin: Helper Agent |
Notes
- The
display_nameshould be defined once inmarketplace.json, not repeated in each agent file - This keeps configuration centralized and follows DRY principles
Environment Info
- Platform: linux
- Version: 2.1.7
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗