Section Insights
Reducing Bloat in System Prompts
How can I optimize my system prompt to remove unnecessary tokens?
Many harnesses, particularly Claude Code, come with excessive bloat in their system prompts. Users can customize their settings to disable unused features, significantly reducing the number of tokens sent with each request.
- System prompts often contain unnecessary tokens that can be removed.
- Customization options allow users to disable features they don't use.
- Reducing the size of the system prompt can improve output quality.
Customizing Claude Code Settings
What steps can I take to customize Claude Code's system prompt?
Users can edit the global settings.json file to disable features like plan mode controls and tool definitions that are not needed, effectively streamlining the system prompt.
- Editing the settings.json file is crucial for customization.
- Disabling unnecessary tools can lead to a more efficient system prompt.
- Personal preferences should guide the customization process.
Removing Unused Tools
Which tools can be safely removed from Claude Code's system prompt?
Users can remove tools such as the 'ask user question' tool, cron scheduling, and custom code review skills if they are not utilized, leading to a cleaner system prompt.
- Identifying and removing unused tools can simplify the system prompt.
- A personalized setup enhances user experience and efficiency.
- Regularly reviewing tool usage is beneficial for optimization.
Impact of Disabling Features
What is the effect of disabling features on the system prompt size?
Disabling various features, including dynamic workflows and remote control, can drastically reduce the system prompt size from 25K tokens to around 8K, improving performance.
- Significant reductions in system prompt size can be achieved by disabling features.
- A smaller system prompt can lead to better performance and outputs.
- Awareness of feature usage is key to effective customization.
Using Proxies for Optimization
How can I monitor and optimize my system prompt?
Utilizing a proxy to analyze the system prompt allows users to identify and retain only the necessary components, enhancing the quality of outputs by minimizing distractions.
- Proxies can provide insights into what is being sent in the system prompt.
- Optimizing the system prompt leads to improved output quality.
- Focusing on essential components reduces distractions for the agent.
Transcript
0:00 Most harnesses, but especially Claude Code, ship with a ton of bloat in the system prompt. There is very likely thousands and thousands of tokens of stuff you're not using in your system prompt. So, when I did mine, I found that I had an whole stuff with workflow, with design sync, with monitor, that I simply wasn't using. And that is about, you know, 8,000, 10,000 tokens per request. Fortunately, Claude Code allows you to customize this stuff, so you can actually put this in your global settings.json file, and you can disable all sorts of useless stuff. So, I didn't want it to control when I entered and exited plan mode. So, I just disabled those tools, and the tool definitions get removed from the system prompt. I personally really hate the ask user question tool, so I never use it, or I never want to see it, and so I just removed the tool definition from Claude system prompt. Equally, I don't want it to schedule crons for me, so I just deleted those as well. I don't use the custom code review skill that ships with it, so I disabled the bundled skills. I disabled everything to do with dynamic workflows. I don't use those either. I even disabled remote control, because there was a lot actually in the system prompt for that. Disabled Claude AI connectors, which were burning a ton of tokens I didn't even realize. And I disabled the artifacts feature. All of that means that I dropped my initial starting system prompt, or the system tools, from 25K down to around 8K. I put this in an article so that you can use a proxy to see what you're actually shipping, which is really, really useful. Then, you can tune the settings to choose just the bits of the system prompt that you need. The less you send over the wire, the better your outputs are going to be, because the agent has less stuff distracting it.
Summary
- Many harnesses, especially Claude Code, come with excessive bloat in the system prompt.
- Users can customize their settings in the global settings.json file to disable unused features.
- Removing unnecessary tools can reduce the system prompt size from 25K tokens to around 8K tokens.
- Disabling features like workflow management, scheduling, and custom skills can improve output quality.
- A proxy can be used to identify and manage the components of the system prompt being shipped.
- Less clutter in the system prompt leads to better focus and performance from the AI agent.
Questions Answered
How can I optimize my system prompt to remove unnecessary tokens?
Many harnesses, particularly Claude Code, come with excessive bloat in their system prompts. Users can customize their settings to disable unused features, significantly reducing the number of tokens sent with each request.
What steps can I take to customize Claude Code's system prompt?
Users can edit the global settings.json file to disable features like plan mode controls and tool definitions that are not needed, effectively streamlining the system prompt.
Which tools can be safely removed from Claude Code's system prompt?
Users can remove tools such as the 'ask user question' tool, cron scheduling, and custom code review skills if they are not utilized, leading to a cleaner system prompt.
What is the effect of disabling features on the system prompt size?
Disabling various features, including dynamic workflows and remote control, can drastically reduce the system prompt size from 25K tokens to around 8K, improving performance.
How can I monitor and optimize my system prompt?
Utilizing a proxy to analyze the system prompt allows users to identify and retain only the necessary components, enhancing the quality of outputs by minimizing distractions.