Skip to content

Claude Code Think Modes Explained: think, think hard, think harder, ultrathink

Purpose

When I use Claude Code, I sometimes see different thinking levels: think, think hard, think harder, and ultrathink. What do they mean? When should I use each one?

This post explains the four think modes and how to choose the right one.

What Are Think Modes?

Think modes activate Claude’s extended reasoning capability. The deeper the thinking, the more time and tokens it uses, but the better the results for complex problems.

Here’s a quick comparison:

Think Mode Comparison
┌──────────────┬────────────┬─────────┬─────────────────────────┐
│ Mode │ Time │ Tokens │ Best For │
├──────────────┼────────────┼─────────┼─────────────────────────┤
│ think │ 2-5 sec │ Low │ Quick questions │
│ think hard │ 5-15 sec │ Medium │ Algorithm design │
│ think harder │ 15-30 sec │ High │ Architecture analysis │
│ ultrathink │ 30-60 sec │ Highest │ Complex problems │
└──────────────┴────────────┴─────────┴─────────────────────────┘

When to Use Each Mode

think (Basic)

Use for simple questions and quick checks:

think examples
claude "think 这个函数有什么问题?"
claude "think 为什么这段代码报错?"
claude "think 这个正则表达式对吗?"

Best for:

  • Code review questions
  • Quick debugging
  • Simple explanations

think hard (Deep)

Use for algorithm design and complex logic:

think hard examples
claude "think hard 设计一个高并发的用户认证系统"
claude "think hard 这个排序算法的时间复杂度是多少?"
claude "think hard 如何优化这个数据库查询?"

Best for:

  • Algorithm design
  • System design
  • Performance optimization

think harder (Deeper)

Use for architecture analysis and difficult problems:

think harder examples
claude "think harder 分析这个微服务架构的数据一致性问题"
claude "think harder 这个分布式锁实现有什么问题?"
claude "think harder 如何设计一个可扩展的消息队列?"

Best for:

  • Architecture review
  • Distributed systems
  • Trade-off analysis

ultrathink (Maximum)

Use for the most complex problems:

ultrathink examples
claude "ultrathink 分析这个分布式系统的性能瓶颈并提出优化方案"
claude "ultrathink 设计一个高可用的全球支付系统"
claude "ultrathink 这个架构有哪些潜在风险?"

Best for:

  • Complex architecture design
  • Multi-system integration
  • Critical decisions

Cost Strategy by Subscription

Your subscription level affects how you should use think modes:

Cost Strategy
┌─────────────────┬────────────────────────────────────────────┐
│ Subscription │ Recommended Usage │
├─────────────────┼────────────────────────────────────────────┤
│ Free │ Use "think" mostly │
│ │ Use "think hard" sparingly │
│ │ Avoid "ultrathink" except critical tasks │
├─────────────────┼────────────────────────────────────────────┤
│ Pro │ Balance all modes │
│ │ Use "think hard" for complex problems │
│ │ Use "ultrathink" occasionally │
├─────────────────┼────────────────────────────────────────────┤
│ Max │ Use "ultrathink" freely │
│ │ Get maximum value from subscription │
└─────────────────┴────────────────────────────────────────────┘

Common Mistakes

  1. Using ultrathink for every query - Wastes tokens unnecessarily
  2. Ignoring think modes entirely - Misses better reasoning
  3. Not considering subscription tier - May exceed budget quickly

Summary

In this post, I explained the four think modes in Claude Code. The key points are:

  1. Match the mode to problem complexity
  2. Use think for everyday tasks, ultrathink for complex problems
  3. Consider your subscription tier when choosing modes
  4. Max plan users should use ultrathink freely to get full value

Think modes are Claude Code’s secret weapon for deep reasoning. Use them wisely.

Final Words + More Resources

My intention with this article was to help others share my knowledge and experience. If you want to contact me, you can contact by email: Email me

Here are also the most important links from this article along with some further resources that will help you in this scope:

Oh, and if you found these resources useful, don’t forget to support me by starring the repo on GitHub!

Comments