01What Is Claude Code Update 2.1.181?

Claude Code update 2.1.181 is a new version of Anthropic's tool that writes and fixes code while you talk to it like a person. This update brings 39 changes and one system prompt change. It fixes several bugs that could save you time or prevent you from losing work.

In this episode, Julian Goldie explains the most important fixes and new features. He covers a new command called slash config, a file corruption bug fix, and a setting to reduce phone notifications. He also talks about faster startup and smoother streaming.

This update is all about making the tool more reliable and easier to use.

02Key Features and Fixes in 2.1.181

Here are the main changes in this update:

  • slash config command – Change settings directly in chat by typing slash config key=value (for example, slash config thinking=false). No need to edit config files.
  • File corruption fix – Write and edit commands no longer create empty or cut-off files on network drives or cloud-synced folders like OneDrive or Google Drive.
  • Client presence file setting – Set a marker file to tell Claude Code you are at the machine, so it stops sending push notifications to your phone.
  • Faster startup – Fixed a regression that added 120 milliseconds to every launch. Now it opens faster for users without MCP servers.
  • Line-by-line streaming – Long text now appears as it is generated instead of waiting for the first full line.
  • Auto-retry on connection drop – If your internet fails mid-response, it retries automatically instead of showing an error.
  • Cleaner memory updates – The end memories line now shows a summary instead of listing every file.
  • Prompt caching fix – Fixes caching breaking on custom API setups and Foundry due to attestation token changes.
  • Mac login fix – Fixes error -600 in open OSA script and browser login flows on Mac.
  • sandbox.allowAppleEvents setting – Opt-in to allow Claude Code to send Apple events when running in a sandbox.

03How to Update and Get Started with 2.1.181

To use this update, you need to install version 2.1.181. If you already use Claude Code, just update it. If you are new, start by installing Claude Code and then update to this version.

  1. Open your terminal or command prompt.
  2. Run the update command for Claude Code (the exact command depends on how you installed it, but it usually is something like 'claude update' or your package manager).
  3. Verify the version by running 'claude --version' and check for 2.1.181.
  4. Once updated, try the new slash config command. Type slash config thinking=false to turn off long thinking output.
  5. If you want to stop phone notifications, set the Claude_client_presence_file setting to point to a marker file on your computer.
  6. Test the file write fix by creating a file in a synced folder like OneDrive and ensure it saves fully.

04Using the New Slash Config Command

The slash config command lets you change settings right in the chat. You type slash config followed by key=value. For example, slash config thinking=false turns off the thinking-out-loud output.

This is useful when you want fast answers instead of long explanations.

This command works in three places: normal typing, when you run Claude Code with the -P flag (for scripts), and in remote control (when controlling Claude Code from another machine). So no matter how you use it, the same trick works everywhere.

For example, imagine you are running Claude Code to manage content for the AI Profit Boardroom. You want quick answers, so you type slash config thinking=false. In two seconds, you are moving again.

Before this update, you would have to find a config file, know the exact setting name, edit it, save it, and restart. Now it is as easy as typing a sentence.

05Results and Comparisons from the Episode

Julian shows how these small fixes stack up. The file corruption bug is a big deal. It was producing files with zero bytes or cut-off content on network drives and cloud-synced folders.

If you save work to OneDrive or Google Drive, you could lose content without knowing. That is now fixed.

The startup slowdown regression added 120 milliseconds to every launch. That is fixed for users without MCP servers. That means Claude Code opens faster than it did a few weeks ago.

Streaming now shows text line by line. The actual speed under the hood didn't change, but it feels smoother and faster. Also, connection drops now auto-retry.

Before, you got a flat error and lost whatever was being built. Now it retries, which helps on spotty Wi-Fi.

Prompt caching works better now. Before, an attestation token changed on every request, making Claude Code think it was talking to a new account each time. That made things slower and more expensive.

Now it remembers the conversation.

06Tips, Limits, and Mistakes to Avoid

Here are some tips and warnings from the episode:

  • Update now – The file corruption bug alone is reason enough. If you save work in synced folders, check your recent files to make sure nothing was lost.
  • Use slash config for speed – Turn off thinking output when you want clean, fast answers.
  • Set the presence file – If you work at your machine and don't want phone pings, set the Claude_client_presence_file to a marker file.
  • Be careful with sandbox.allowAppleEvents – Only opt in if you trust the workflow. It allows Apple events between apps.
  • Check your version – If you are not tracking updates, you may be using an older, slower, buggier version without knowing it.

One mistake to avoid: ignoring updates. These changes ship every few days. If you don't update, you miss fixes like the file corruption bug.

Another mistake: using synced folders without checking them after this bug. It could have eaten your files.

07Who Should Use This Update and Why It Matters

If you are already using Claude Code, update it. The fixes are not optional extras. The file corruption fix is critical for anyone saving work to synced folders.

The slash config command is a big convenience for anyone who wants to customize settings without digging through files.

If you are not using Claude Code yet, this is a good time to start. The tool is becoming more reliable every week. The faster startup, smoother streaming, and auto-retry on connection drops make it more dependable for real work.

This episode is aimed at business owners and developers who want to save time. The new features help you spend less time fighting the tool and more time using it to get work done. Julian also mentions that inside the iProfit Boardroom, they track every update and turn it into step-by-step tutorials.

He also mentions the free AI Success Lab with notes and a community of 75,000 people.

08Practical Example: Use Update 2.1.181 Today

Here is a practical way to use this update today. Open Claude Code and ask it to help you write a weekly content plan for the AI Profit Boardroom community. Ask for topics, headlines, and a posting schedule.

Then use slash config to turn off the long thinking output. Type slash config thinking=false. You get a clean, fast answer instead of a wall of reasoning text.

This example shows how the update makes Claude Code more useful for everyday business tasks. It also shows how the slash config command saves time. You don't have to dig through settings files.

You just type the setting right in the chat and keep moving.

This is the kind of update that quietly makes your whole week smoother once you know it's there.