1 00:00:00,000 --> 00:00:04,800 So, I- I- I was spinning up the new Claude Code terminal agent this morning, 2 00:00:04,853 --> 00:00:05,280 right? 3 00:00:05,370 --> 00:00:08,080 Version 2.1.210. 4 00:00:08,260 --> 00:00:13,280 And bang, right out of the gate, my terminal starts yelling at me with these bright 5 00:00:13,326 --> 00:00:14,800 yellow startup warnings. 6 00:00:15,040 --> 00:00:18,240 It- it- it was all about deprecated permission rules. 7 00:00:18,313 --> 00:00:23,680 Apparently, my old ~/.claude.json is basically ancient history now. 8 00:00:24,259 --> 00:00:27,427 Yeah, they completely gutted the old permission model. 9 00:00:27,480 --> 00:00:31,987 If you've got Write, NotebookEdit, or Glob in your config, Claude is going to 10 00:00:32,040 --> 00:00:32,547 complain. 11 00:00:32,627 --> 00:00:35,587 They're forcing everyone over to a unified model. 12 00:00:35,694 --> 00:00:38,067 It's basically just Edit and Read now. 13 00:00:38,083 --> 00:00:39,843 And honestly, thank goodness. 14 00:00:39,953 --> 00:00:43,523 Because, man, the old way was a proper headache. 15 00:00:43,683 --> 00:00:50,563 Like, you'd have Write(path) and NotebookEdit(path) and Glob(path). 16 00:00:50,750 --> 00:00:52,563 It was so fractured. 17 00:00:52,723 --> 00:00:56,803 I remember setting up a project last month where I let the agent edit a file, 18 00:00:56,823 --> 00:01:00,723 but because of some weird edge case with Write versus NotebookEdit, 19 00:01:00,763 --> 00:01:04,643 the agent just completely choked when it tried to spin up a new file in that same 20 00:01:04,699 --> 00:01:05,283 directory. 21 00:01:05,496 --> 00:01:09,283 It just sat there throwing permission errors at itself. 22 00:01:09,592 --> 00:01:13,772 Right, because previously, writing a brand-new file and modifying an existing one 23 00:01:13,884 --> 00:01:16,972 were treated as totally separate capabilities. 24 00:01:17,012 --> 00:01:21,772 Now, with the unified Edit(path) rule, if Claude has permission to touch a path, 25 00:01:21,825 --> 00:01:24,892 it can read, write, create, or modify. 26 00:01:25,025 --> 00:01:27,612 It simplifies the entire security boundary. 27 00:01:27,692 --> 00:01:33,452 Your .claude.json goes from this massive, bloated block of fine-grained rules to 28 00:01:33,484 --> 00:01:36,812 just a couple of clean lines of Edit and Read array mappings. 29 00:01:36,792 --> 00:01:37,552 Exactly! 30 00:01:37,592 --> 00:01:41,752 It's like, why make the agent ask three different times just to do one job? 31 00:01:41,972 --> 00:01:46,472 Now, if you want to clean up your config, you literally just open up your global 32 00:01:46,752 --> 00:01:52,632 ~/.claude.json or your project-local one, and you collapse those old arrays. 33 00:01:52,872 --> 00:01:55,820 If you had "Write": ["src/**/*"] and "NotebookEdit": ["src/**/*"], 34 00:01:55,824 --> 00:01:58,783 you just delete both of those and replace them with "Edit": ["src/**/*"]. 35 00:01:58,787 --> 00:01:59,996 It's incredibly clean. 36 00:02:00,176 --> 00:02:04,316 But, uh, speaking of long operations, did you see what they did with the terminal UI 37 00:02:04,356 --> 00:02:06,076 for tools that take a while to run? 38 00:02:06,360 --> 00:02:07,683 Oh, the ticking timer! 39 00:02:07,803 --> 00:02:08,243 Yes! 40 00:02:08,307 --> 00:02:11,203 That is such a massive quality-of-life upgrade. 41 00:02:11,260 --> 00:02:15,443 Before, when Claude was running a long-running tool-like a heavy test suite or a big 42 00:02:15,496 --> 00:02:19,843 build step-the tool summary would just collapse, and you'd sit there staring at a 43 00:02:19,900 --> 00:02:20,923 static spinner. 44 00:02:20,993 --> 00:02:25,123 You had no idea if the process was actually hung or if it was just taking its sweet 45 00:02:25,203 --> 00:02:25,524 time. 46 00:02:25,703 --> 00:02:30,243 Now, there's a live, ticking elapsed-time counter right next to the collapsed tool 47 00:02:30,303 --> 00:02:31,043 summary. 48 00:02:31,123 --> 00:02:34,643 It actually counts up, second by second, so you know the daemon hasn't just 49 00:02:34,723 --> 00:02:36,003 flatlined on you. 50 00:02:36,000 --> 00:02:37,080 Mate, yes! 51 00:02:37,147 --> 00:02:38,160 It's the little things. 52 00:02:38,267 --> 00:02:40,320 It saves you from that awkward... 53 00:02:41,996 --> 00:02:44,720 you know, that "is it broken or is it just slow?" 54 00:02:44,827 --> 00:02:48,320 dance where you're tempted to hit Ctrl+C and ruin the whole run. 55 00:02:48,460 --> 00:02:51,280 And they also tweaked the claude attach behavior, right? 56 00:02:51,344 --> 00:02:53,200 Something about the daemon settling? 57 00:02:53,320 --> 00:02:54,448 Yeah, exactly. 58 00:02:54,520 --> 00:02:57,768 When you run claude attach to hook into an existing session, 59 00:02:57,788 --> 00:03:00,648 the background daemon integration is much more robust now. 60 00:03:00,776 --> 00:03:05,128 They added a settling delay to make sure the state is fully synchronized before the 61 00:03:05,181 --> 00:03:07,288 terminal prompt hands control back to you. 62 00:03:07,475 --> 00:03:11,288 No more race conditions where you start typing commands while the background process 63 00:03:11,341 --> 00:03:12,248 is still waking up. 64 00:03:12,762 --> 00:03:13,130 Brilliant. 65 00:03:13,317 --> 00:03:18,010 Oh, and for the Vim nerds out there, they finally added a setting for custom 66 00:03:18,090 --> 00:03:18,890 keybindings. 67 00:03:18,983 --> 00:03:24,650 There's a new JSON option called vimInsertModeRemaps that you can drop straight into 68 00:03:24,666 --> 00:03:25,850 your settings file. 69 00:03:25,930 --> 00:03:31,290 So if you're like me and your muscle memory is hardwired to use jk or jj to escape 70 00:03:31,347 --> 00:03:35,770 insert mode, you can finally do that in the Claude terminal interface without losing 71 00:03:35,786 --> 00:03:36,570 your mind. 72 00:03:36,967 --> 00:03:37,623 That's huge. 73 00:03:37,810 --> 00:03:41,544 No more accidental jj strings scattered all over our prompts. 74 00:03:41,643 --> 00:03:44,103 Alright, update your global configs, people. 75 00:03:44,263 --> 00:03:45,543 We are out of here.