{"version":"2.1.305","anchor":"plugin-hook-lookup-for-remote-machines-now-returns-an-object","canonical_anchor":"plugin-hook-lookup-for-remote-machines-now-returns-an-object","heading":"Plugin hook lookup for another machine retries when the plugin is missing","tier":"internal","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/plugin-hook-lookup-for-remote-machines-now-returns-an-object","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Plugin hook lookup for another machine retries when the plugin is missing\n\nWhen Claude Code looks up a plugin's hooks for another machine and the plugin is not found, it now repeats the same lookup\n\n**Unclear.** What the changed retry means for plugins that are missing or late to sync is not known.\n\n**What**\n\nHooks are commands a plugin runs at set points in a session. When Claude Code looks up a plugin's hooks for another machine, it now checks whether the plugin was found. If it was not, Claude Code runs the same lookup again. Before, the retry used a different lookup.\n\n**Why**\n\nThis may change how Claude Code handles a plugin that is missing or has not finished syncing.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}