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

Abierto
#1,180 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
53/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
cli, tooling

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
481
Forks
45
Merge medio
1 d 13 h
PR fusionados (30 d)
91

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ai-driven-dev/framework

Todos los issues de ai-driven-dev/framework

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.