[FEATURE] Plugin parity in Chat (Desktop)

Resolved 💬 1 comment Opened May 6, 2026 by jenross-de Closed Jun 4, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

I am a designer and often hopping between Claude Code and Chat in the Desktop app. My team creates and maintains design skills via a plugin, but it can't be accessed when using Chat. So, we have to create/maintain skills in that ecosystem as well.

Proposed Solution

Create plugin parity for Chat so that teams only have to maintain skills within plugins (not both plugins and skills ecosystem for Chat).

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Configuration and settings

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗