# Claude Code New Updates: Better Desktop App, Simple Mode, In-built Worktrees, New Hooks & MORE!

- **Channel**: AICodeKing
- **Date**: 2026-02-23
- **Duration**: 13m 44s
- **Views**: 9963
- **URL**: https://www.youtube.com/watch?v=BMG4c-QT8hI

## Description
In this video, I'll be going through all the major Claude Code updates, including Git Worktree Isolation, the new Claude Code Desktop with app preview and GitHub integration, Opus 4.6, Auto Memory, Claude Code Security, and a lot more.

Key Takeaways:

- Git Worktree Isolation is now built into Claude Code natively, letting you run multiple agents on the same repo without conflicts.
- Claude Code Desktop now has a live app preview, code review panel, and GitHub integration for automated PR m

## Transcript
Hi, welcome to another video. So, Claude Code has been getting a ridiculous amount of updates recently, and I think it's time we sit down and go through all the major changes because if you haven't been keeping up, you're missing out on some genuinely game-changing stuff. We're talking about new CLI features, the new Cloud Code desktop with app preview and GitHub integration, Opus 4.6, automemory, Claude Code security, and a bunch of other things. So, let's get right into it. Now, on the CLI side, if you saw my last video, I already covered hooks, skills, hot reload, context forking, and all that. So, I'm only going to talk about the updates from the last couple of weeks, and there are some really good ones. The biggest new feature is Git Workree isolation. They added a -w flag or d-worktree that lets you start cla work. So, if you're running multiple cla code sessions on the same repo, their code edits no longer conflict with each other. Each session gets its own work tree. Sub aents also support this now with isolation colon workree in agent definitions. If you've been using tools like Ralphie to get workree isolation, this is now built right into cloud code natively, which is pretty great. They also improved background agent control. There's now a control + F key binding that kills background agents with a two press confirmation. You press it twice within 3 seconds and it kills all background agents. Agent definitions also support background true now which makes them always run as background tasks and background agents continue running when you press escape to cancel the main thread. Previously, control + C and escape were being silently ignored when background agents were running and the main thread was idle, which was really annoying. That's fixed now. There's a new config change hook event that fires when configuration files change during a session. This is mostly aimed at enterprise users who want security auditing. You can use it to block configuration changes using exit code 2 or a JSON decision. So if someone tries to change cloud code settings mid session in a way that violates your security policy, you can catch and block that. Policy settings changes can't be blocked though, which makes sense. Simple mode also got an upgrade. If you use the claude_code underscore simple environment variable, it now includes the file edit tool alongside the bash tool. Previously, simple mode only had bash, which was pretty limiting. It still disables MCP tools, attachments, hooks, and claw. MD loading, so it stays lightweight, but having fileed in there makes it way more usable. LSP servers now support a startup timeout configuration. You can specify how long Claude should wait for an LSP server to initialize in milliseconds. This is important for slower servers like the Java language server that need significant initialization time. Without this, they just time out and you'd get no type information. And on the model side, Sonnet 4.5 has been officially replaced by Sonnet 4.6 as the default model, which comes with a 1 million token context window. Some users reported temporarily losing access to the 1M context after an auto update, but that's been resolved now. They also fixed a bunch of stability things. Sessions no longer become invisible when the working directory involves SIM links. Session data loss on SSH disconnect is fixed because they now flush session data before hooks and analytics during graceful shutdown. Those excessiveclaw.json.backup files that were accumulating on every startup fixed memory usage for shell commands with large output no longer grows. unboundedly and startup performance got better by removing eager loading of session history. So, a lot of reliability improvements under the hood. Now, let's talk about Claude Code Desktop because this is where things get really interesting. Claude Code Desktop now has a built-in app preview feature. You can start a DV server directly from cloud code and preview your running application in real time inside the desktop interface. It detects errors from the console logs automatically and can iterate on those errors without you having to copy paste anything. So you tell Claude to build a React component. It spins up the DV server. You see the preview live. It catches a rendering error and it fixes it all within one interface. This is pretty amazing to be honest. They also added a proper code review panel. You can see all the changes Claude made with inline comments, identify bugs before pushing, and review diffs in a dedicated panel. It's like having a mini pull request experience right inside the desktop app. But the feature that I think a lot of people are going to love is the GitHub integration. Claude Code Desktop can now monitor your pull requests in the background. It watches your CI checks and if something fails, it can automatically attempt to fix the failure. And if you enable it, it can even automerge PRs once all checks pass. So you push a PR, go do something else, and Claude handles the rest. For people who do a lot of open-source or manage multiple repos, this is a massive timesaver. And session mobility got a big upgrade, too. You can start a session in the CLI, move it to the desktop with the /esktop command, and then move it to the web with a single button click. Your full session context persists across CLI, desktop, and mobile, which is just amazing. Now, let's talk about Claude Opus 4.6 because the model upgrade matters a lot for Claude Code users. Opus 4.6 came out in early February and it brings a 200,000 context window with a 1 million token context in beta. The max output is now 128,000 tokens. It has something called adaptive thinking where Claude dynamically decides when and how much to think about a problem. But the big thing for coding is the longer task completion horizon. Anthropic's own numbers show Opus 4.6 can sustain work for up to 14 hours at a 50% success rate. That's insane. For practical purposes, it means Claude can handle much larger multifile projects without losing track of what it's doing. If you're on the $200 max plan, this is honestly where you start seeing the value. Moving on, let's talk about automemory, which is a new feature that just rolled out. Claude Code now automatically records and recalls memories across sessions. It stores learnings, patterns, and insights it discovers while working on your project. These live in tilda/.cloud/ projects inside a memory directory specific to each project. So if Claude learns that your project uses a specific testing pattern or that you prefer a certain code style, it remembers that the next time you start a session, it's autosynced across all subdirectories within the same Git repository. There's a 200line hard limit on the memory file to keep things lean. And if you don't want it, you can disable it with an environment variable. This is something I've seen people hack together with customclaw.md files for a while, but having it builtin and automatic is a completely different experience. You don't have to maintain your own memory system anymore. Claude just learns as it goes. Now, I briefly want to mention Claude code security, which is in a limited research preview right now. This is an automated security analysis feature that scans your codebase for vulnerabilities. But here's what makes it different from traditional security scanners. It uses semantic reasoning like how a human security researcher would think instead of just pattern matching. It understands how components interact, how data flows through your application, and it catches complex vulnerabilities that rule-based tools like Snike or Sonar Kubie would miss. All suggestions require human approval before implementation, which is good. It's still early days, but I think this could become a really strong selling point for cloud code. Next up, MCP servers got a major performance upgrade. They added lazy loading, which reduces context usage by up to 95%. They also added MCP tool search, which lets Claude search across all your configured MCP servers without eating up your context window. So if you have a bunch of MCP servers for things like Google Drive, Jira, Slack, or whatever custom tools you use, Claude can now access all of them efficiently without the context overhead. This is a really good improvement for sure. For the IDE users, VS Code got some nice improvements, too. The plan preview now auto updates as Claude iterates. Commenting is only enabled when the plan is actually ready for review. And the preview stays open when you reject a plan instead of closing. They also improved the permission destination chooser. So your choice of project, user, or session scope persists across sessions. Jetbrains has an official Claude code plugin now from the Jet Brains marketplace with a diff viewer for reviewing changes and LSP integration gives Claude realtime code understanding including type information errors and navigation. So your IDE and Claude code are properly talking to each other now. Claude code is also now included with every team plan standard seat which is great for teams that were on the fence about it. So taking a step back the overall picture here is that claude code is maturing fast. The desktop app with preview code review and GitHub integration is turning it into something closer to a full development environment. Get work tree isolation means you can run parallel agents without conflicts natively. The model upgrades with Opus 4.6 mean the agent can handle longer and more complex tasks. Automemory means it gets smarter the more you use it. And the MCP and IDE improvements mean it plays better with your existing tools. I believe Claude Code is currently the most featurerich AI coding agent out there. Cursor is great for inline editing. Copilot is solid for autocomplete, but nobody else has this combination of terminal power, desktop features, multi- aent coordination, and tool integration. That said, the competition is heating up and the token costs are still significant, especially if you're using Opus, but if you're serious about AI assisted development, Claude Code is hard to beat right now. Overall, it's pretty cool. Anyway, share your thoughts below and subscribe to the channel. You can also donate via Superthanks option or join the channel as well and get some perks. I'll see you in the next video. Bye.
