{"version":"2.1.292","anchor":"plugin-hook-table-gains-promptautocomplete-validator-treat","canonical_anchor":"plugin-hook-table-gains-promptautocomplete-validator-treat","heading":"Plugins can hook into prompt autocomplete","tier":"use","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/plugin-hook-table-gains-promptautocomplete-validator-treat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Plugins can hook into prompt autocomplete\n\nPlugins gain a `prompt.autocomplete` hook point, and the plugin checker lists hooks that answer a plugin's own command separately\n\n**Unclear.** What a `prompt.autocomplete` hook receives or can do when it runs is not stated.\n\n**What**\n\nA plugin is an add-on that extends Claude Code, and a hook is code a plugin runs when a certain event happens. Two things changed:\n\n- The list of events a plugin can hook into now includes `prompt.autocomplete`, which relates to suggestions offered while you type a prompt.\n\n- When the plugin checker finds a `command.run` hook that responds to a command the plugin itself ships, it now lists it as \"answers its own command\" instead of treating it as a hook that controls whether commands may run.\n\n**Why**\n\nPlugin authors get a new point to hook into, and the checker's report no longer mixes up a plugin handling its own command with a plugin controlling other commands.\n\n- Area: Plugins\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}