1 00:00:00,000 --> 00:00:06,080 If you updated Claude Code to version 2.1.283 this week, and you run it through 2 00:00:06,137 --> 00:00:10,960 Amazon Bedrock, Google Cloud Vertex AI, or with telemetry turned off, 3 00:00:11,008 --> 00:00:14,160 something pretty dramatic just shifted under your feet. 4 00:00:14,224 --> 00:00:18,000 Your interactive terminal sessions are now booting straight into auto mode by 5 00:00:18,080 --> 00:00:18,720 default. 6 00:00:19,090 --> 00:00:20,570 Yeah, straight into the deep end! 7 00:00:21,190 --> 00:00:24,910 No prompt asking for permission to read a folder, no tap on the shoulder. 8 00:00:25,470 --> 00:00:26,470 Just straight to work. 9 00:00:27,170 --> 00:00:32,070 The changelog notes put it plainly: interactive sessions on third party providers or 10 00:00:32,110 --> 00:00:36,570 with telemetry off start in auto mode when no permission mode is configured. 11 00:00:36,750 --> 00:00:42,350 Which is wild if you are sitting inside an enterprise VPC expecting manual control. 12 00:00:42,490 --> 00:00:44,030 But you know why they did it, right? 13 00:00:44,156 --> 00:00:48,430 Prompt fatigue was completely choking developer velocity on those third party 14 00:00:48,478 --> 00:00:49,070 endpoints. 15 00:00:49,217 --> 00:00:54,030 Every single file inspect, every git status, you had to hit enter to approve. 16 00:00:54,902 --> 00:00:55,982 Oh, mate, totally. 17 00:00:56,442 --> 00:00:58,322 It was like driving with the handbrake on. 18 00:00:58,962 --> 00:01:02,842 You ask it to scan a repo, and it stops every two seconds asking, 19 00:01:03,282 --> 00:01:05,082 can I peek at package dot json? 20 00:01:05,582 --> 00:01:06,902 Can I check git status? 21 00:01:07,562 --> 00:01:09,582 But, but, here is the rub. 22 00:01:10,302 --> 00:01:14,342 If a developer isn't expecting it, seeing your terminal run shell commands on its 23 00:01:14,402 --> 00:01:16,842 own without a prompt gives you quite the fright. 24 00:01:16,958 --> 00:01:19,918 Right, but auto mode does not mean total anarchy. 25 00:01:20,105 --> 00:01:25,278 It uses a classifier to separate routine, read only actions from destructive things 26 00:01:25,326 --> 00:01:27,518 like deleting files or pushing commits. 27 00:01:27,638 --> 00:01:32,798 The classifier grants automatic passes to safe reads, but still pauses and prompts 28 00:01:32,838 --> 00:01:34,318 you for risky mutations. 29 00:01:34,333 --> 00:01:40,333 True, but if your company policy mandates human confirmation on every single step, 30 00:01:40,367 --> 00:01:44,973 having an update quietly flip that default could rattle some cage doors in 31 00:01:45,031 --> 00:01:45,933 compliance. 32 00:01:46,120 --> 00:01:49,853 If you want the old manual behavior back, how do you pin it down? 33 00:01:49,875 --> 00:01:50,995 Super straightforward. 34 00:01:51,095 --> 00:01:55,715 You just open your settings dot json in your dot claude folder, 35 00:01:55,735 --> 00:01:58,755 and set permissions, defaultMode, to default. 36 00:01:58,867 --> 00:02:00,915 That locks it back to manual approvals. 37 00:02:01,155 --> 00:02:04,835 Or, if you are mid session and Claude starts running too fast, 38 00:02:04,883 --> 00:02:08,515 just hit Shift plus Tab to cycle back to manual mode on the fly. 39 00:02:08,542 --> 00:02:10,142 Shift plus Tab, easy as. 40 00:02:10,262 --> 00:02:14,142 And you can run slash status in your console to inspect what the auto mode 41 00:02:14,193 --> 00:02:15,822 classifier is actually up to. 42 00:02:15,915 --> 00:02:19,422 Which brings up a sneaky gotcha for cloud proxies, doesn't it? 43 00:02:19,758 --> 00:02:20,098 Yes! 44 00:02:20,338 --> 00:02:21,798 That is a huge detail. 45 00:02:22,498 --> 00:02:27,458 If your corporate proxy strips custom gateway headers, Claude Code might fail over 46 00:02:27,518 --> 00:02:32,818 to evaluating auto mode locally, which burns extra input tokens against your Bedrock 47 00:02:32,858 --> 00:02:37,438 or Vertex model quota instead of using the fast server side classifier. 48 00:02:38,158 --> 00:02:41,558 You have to keep an eye on that CLAUDE CODE AUTO MODE SERVER setting. 49 00:02:41,625 --> 00:02:46,025 Sneaky token costs, nobody wants that on their cloud bill at the end of the month. 50 00:02:46,285 --> 00:02:50,905 Now, what about the other goodies tucked into 2.1.283? 51 00:02:50,985 --> 00:02:53,625 Because there are some absolute gems in here. 52 00:02:53,745 --> 00:02:55,325 The MCP image change! 53 00:02:56,005 --> 00:02:59,285 Before this, if a Model Context Protocol tool generated an image, 54 00:02:59,745 --> 00:03:04,365 say a UI test screenshot or a data plot, it stayed trapped in the tool payload. 55 00:03:05,085 --> 00:03:09,665 Now, Claude Code automatically saves MCP returned images directly to disk files. 56 00:03:09,828 --> 00:03:11,108 That is massive. 57 00:03:12,108 --> 00:03:15,428 That means your local Bash scripts, or Claude's built in Read tool, 58 00:03:15,948 --> 00:03:19,928 can immediately pick up the file, inspect the bytes, or pass it down a build 59 00:03:20,048 --> 00:03:20,548 pipeline. 60 00:03:21,068 --> 00:03:25,008 It turns visual tool outputs into real workspace artifacts. 61 00:03:25,250 --> 00:03:30,450 And there is a really handy change for flags: system prompt and append system prompt 62 00:03:30,570 --> 00:03:35,090 now let you pass both raw text and a file path simultaneously. 63 00:03:35,223 --> 00:03:39,010 It automatically prepends the file content before your inline string. 64 00:03:39,117 --> 00:03:43,330 So you can load a base company instruction file and slap a quick session specific 65 00:03:43,383 --> 00:03:44,610 override on the end. 66 00:03:44,905 --> 00:03:46,725 And thank goodness for the Windows fix! 67 00:03:47,265 --> 00:03:52,905 On PowerShell, previous builds had a scary edge case where running cmd slash c rd or 68 00:03:53,465 --> 00:03:58,865 rmdir could bypass checks and let things delete drive roots or user profile folders. 69 00:03:59,405 --> 00:04:02,665 They patched that right up so PowerShell refuses to touch root directories. 70 00:04:04,255 --> 00:04:08,595 Yeah, not accidentally wiping C drive is definitely a quality of life improvement. 71 00:04:08,667 --> 00:04:09,627 Too right, mate. 72 00:04:09,817 --> 00:04:14,267 Alright, go check your settings files and mind those auto permissions. 73 00:04:14,387 --> 00:04:15,627 Catch you next time.