{"version":"2.1.293","anchor":"hook-runs-on-another-machine-now-reported","canonical_anchor":"hook-runs-on-another-machine-now-reported","heading":"Hooks that ran on another machine no longer print failures at session end","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/hook-runs-on-another-machine-now-reported","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Hooks that ran on another machine no longer print failures at session end\n\nA failed SessionEnd hook that ran on another machine no longer writes its failure output locally, and a new message marks such hooks\n\n**What**\n\nA hook is a command you set up to run automatically at a certain point in Claude Code. `SessionEnd` hooks run when a session terminates. If such a hook is marked as having run on another machine, Claude Code no longer writes its failure output to your terminal's error output.\n\nA new message is also used for hooks run elsewhere: \"This hook runs on another machine, which could not run it.\"\n\n**Why**\n\nIn remote sessions, or sessions connected through another machine, you should no longer see misleading `SessionEnd` hook failures printed on your own computer.\n\n- Area: Hooks\n- Names: `SessionEnd`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}