fix(cli): plugin update skips Cursor silently and leaves renamed hook scripts behind

Ouverte
#1,180 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
53/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
typescript
Domaine
cli, tooling

Piste de recherche

Start with plugin-update-use-case.ts, plugin-add-use-case.ts, and install-ai-tool-use-case.ts; trace how updates select installed tools and how replace handles previously tracked files. Add tests for a renamed hook through plugin update, replacement, and Cursor setup, checking that edited files are preserved. Done means updates report or reach Cursor, obsolete unchanged files are removed on replacement, and the tests pass.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Description

After the plugin renames a hook script (here hooks/aidd-context/update_memory.js → memory.cjs), updating does not reach every installed tool, and nothing says so.

  1. Cursor is skipped by aidd plugin update. Cursor plugins are recorded with scope user; PluginUpdateUseCase.updatePluginsForTool filters them out when no plugin name is given. The command prints "Updated" for the other tools only. The project's .cursor/hooks.json keeps calling the old script until aidd setup runs again. Naming the plugin fails: Tool 'cursor' does not support scope 'project'.
  2. opencode and Kilo keep orphan files on a reinstall. aidd setup / a reinstall goes through replace: true (install-ai-tool-use-case.ts:128); dropExistingPlugin (plugin-add-use-case.ts) drops the manifest record but never deletes the previously tracked files the new version no longer ships. They are inert (the bridge spawns only current hooks) but stay on disk, untracked, so clean misses them. plugin update itself removes them through deleteOldFiles.
  3. No test covers a renamed hook script through plugin update, through replace, or through Cursor setup again.
Affected file(s)

cli/src/contexts/framework/application/plugin/plugin-update-use-case.ts, cli/src/contexts/framework/application/plugin/plugin-add-use-case.ts, cli/src/contexts/framework/application/install/install-ai-tool-use-case.ts

Expected behaviour
  • An update reaches every installed tool, or names the tool it skipped and the command that updates it.
  • A replaced install removes the files the new version no longer ships, hash-checked like removeObsoleteScripts, so a user-edited file is kept.
Observed behaviour

Measured with the CLI built from a scratch copy: install from origin/next, bump aidd-context, marketplace refresh then plugin update, and separately setup again.

  • Cursor: stays on the old version; .cursor/hooks.json still runs update_memory.js on every sessionStart.
  • opencode / Kilo after setup again: .opencode/hooks/aidd-context/update_memory.js and the .kilo copy remain beside memory.cjs.
  • No case of two memory writers running at once was found.
AI tool

Cursor, OpenCode, Kilo

Additional context

Smallest fixes:

  • Cursor: warn after plugin update that Cursor needs plugin update --scope user then aidd setup, or drive that sequence from the default update.
  • opencode / Kilo: capture the previous record's plugin.files in prepareForInstall (next to prevHooksMap) and delete those absent from the new set on replace, with the same hash check as removeObsoleteScripts.
  • Tests: a rename (update_memory.js → memory.cjs) through plugin update, through replace, and through Cursor setup again.

Unverified: Codex and Copilot host loading (host registration failed in the sandbox); Cursor projects installed before hook provenance records.

Langage dominant
TypeScript
Étoiles
481
Forks
45
Merge moyen
1 j 13 h
PR mergées (30 j)
91

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de ai-driven-dev/framework

Toutes les issues de ai-driven-dev/framework

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.