CommandCodeAI / CommandCodeAI/command-code
Allow deleting remote Taste packages from web (Studio) and CLI
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- Keine Sprachdaten
- Sterne
- 4k
- Forks
- 350
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
Feature Description
Holas.
There is currently no way to delete remote Taste packages (commandcode.ai/username/taste). I verified
this in two places:
- Web / Studio: The Taste tab in commandcode.ai/studio only lets you view, push, and pull profiles.
Opening a remote package shows no "Delete", "Remove", or trash icon to delete it. The public view
(/username/taste) is read-only. - CLI: cmdc taste (equivalent to npx taste) only exposes push, pull, list, lint, open. There is no
delete/rm subcommand or flag to remove a remote package.
Request: Add the ability to delete remote Taste packages in both channels:
- In Studio: a delete button per package (on the package card and/or in the detail view).
- In CLI: a subcommand like cmdc taste delete --remote (or rm) that removes the package from
the remote registry.
Use Case
I have 2 old remote packages (waku-portafolio, michi-cards-final) and want to reduce them to
a single one (my global Taste). Today the only option is to overwrite with push --overwrite; I cannot
delete the remote I no longer use. This accumulates obsolete profiles and prevents keeping a single
clean remote.
Additional Context
Expected behavior:
- In Command Code Studio (commandcode.ai/studio → Taste tab), each remote Taste package should have
a delete/remove control (trash icon or "Delete" button) both on the package card and inside the
package detail view, allowing the user to permanently remove a remote package.- The CLI should provide a delete subcommand, e.g. cmdc taste delete --remote (or rm),
that removes a package from the remote registry (commandcode.ai/username/taste). - A user should be able to reduce their remote Taste packages to a single one (e.g. their global
Taste) by deleting the obsolete ones.
- The CLI should provide a delete subcommand, e.g. cmdc taste delete --remote (or rm),
Actual behavior:
- Studio's Taste tab only supports viewing, pushing, and pulling profiles. Opening a remote package
shows no delete/remove option — the public view (/username/taste) is read-only.- cmdc taste --help lists only push, pull, list, lint, open. There is no delete/rm subcommand or
flag to remove a remote package. - cmdc taste list --remote lists remote packages but offers no way to delete them.
- The only available action is cmdc taste push --all --remote --overwrite, which overwrites an
existing package but cannot remove a remote package the user no longer wants (e.g. old
waku-portafolio and michi-cards-final packages remain in the registry with no deletion path).
- cmdc taste --help lists only push, pull, list, lint, open. There is no delete/rm subcommand or
Steps to reproduce:
- cmdc taste list --remote → lists remote packages with no delete option.
- cmdc taste --help → no delete command listed.
- Studio → Taste → open a package → no delete option.
How important is this to you?
Important for my workflow
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Es werden keine Dateien oder Tests genannt. Beginne damit, den cmdc taste-Einstiegspunkt und den Studio Taste-Tab nachzuverfolgen, und folge dann, wie list --remote Pakete liest und wie Paketkarten oder Detailansichten gerendert werden. Die Aufgabe ist erledigt, wenn ein authentifizierter Benutzer ein ausgewähltes Remote-Paket über beide Kanäle löschen kann und das Paket aus den Remote-Auflistungen entfernt wurde.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- cli
- Bereich
- cli, web-dev
- Issue-Typ
- Feature
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Ruhig
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 48/100