Claude Code v2.1.289 fixes shell approvals as Opus 5.5 extends autonomous runs

Claude is pairing longer-running autonomous coding with tighter attention to the controls that govern agent actions. The Opus 5.5 guidance recommends handing over multi-step work with a clear finish line, while Claude Code v2.1.289 fixes a managed-machine approval rule affecting nested compound shell commands. Together, the changes make command-policy verification and explicit stop conditions part of safely operating longer agent runs.

• Claude's September 22 Opus 5.5 guidance says the model handles long, multi-part repository work better than prior Opus models, with early testers running coding tasks for hours with little oversight.
• The guidance recommends stating what “done” means, letting the run continue, and telling the model when to stop and ask; after a long run, users should review what it needs from them.
• Claude Code v2.1.289, dated October 3, fixes a deny-or-ask rule on a nested part of a compound shell command failing to hold over approval from a user-installed mod on managed machines.

Bottom line If you manage Claude Code on managed machines, deploy v2.1.289 and test deny/ask behavior before permitting extended Opus 5.5 runs.