{"version":"2.1.287","anchor":"cloud-session-hooks-panel-reworded-and-gains-plugin-hooks-se","canonical_anchor":"cloud-session-hooks-panel-reworded-and-gains-plugin-hooks-se","heading":"Cloud session hooks panel reworded and gains a plugin hooks section","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/cloud-session-hooks-panel-reworded-and-gains-plugin-hooks-se","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Cloud session hooks panel reworded and gains a plugin hooks section\n\nThe panel listing this machine's hooks for a cloud session has shorter text and makes room for a section about plugin hooks\n\n**Unclear.** It is not clear what decides when this panel is shown.\n\n**What**\n\nHooks are commands that run automatically at certain points in a session. A cloud session runs Claude Code on a remote machine. A panel lists the hooks on your own machine and how they relate to a cloud session.\n\nThat panel has changed:\n\n- The explanation is shorter. It now says: \"Each row says where one of this machine's hooks runs for this cloud session. Hooks committed to the repository run in the cloud.\"\n\n- The panel makes room for a section about plugin hooks when there are any.\n\n- Each row can now show whether its hook is in force.\n\nBefore, the text said the hooks below were configured on this machine, in your user settings, the checkout's settings.local.json, or a --settings file.\n\n**Why**\n\nThe panel tells you where each of your hooks runs for a cloud session, and points out that hooks saved in the repository run in the cloud.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}