[FEATURE] Feature request: Water usage tracker alongside cost tracker

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Add a water consumption metric alongside the existing cost tracker to help users understand the environmental footprint of their Claude Code usage.

Proposed Solution

Motivation

Claude Code currently displays token usage and estimated cost, which helps users make informed decisions about their AI usage. A water consumption estimate would extend
this transparency to environmental impact.

As AI usage grows, users increasingly want to understand the full cost of their choices—not just financial, but environmental. Having this information visible would:

• Help users make informed decisions about when AI assistance is worth the environmental cost
• Encourage mindful usage patterns
• Position Anthropic as a leader in AI sustainability transparency

Proposed Implementation

Display an estimated water usage metric (e.g., in milliliters or liters) in the session summary, similar to how cost is currently shown.

This would require:

1. Anthropic calculating and publishing water-per-token estimates (even rough averages would be valuable)
2. Exposing this data via the API or as a derived metric in Claude Code

Considerations

Water usage varies based on:

• Data center location and cooling method
• Local climate conditions
• Power generation source

Even an averaged estimate with appropriate caveats would be more useful than no visibility at all. The estimate could include a note about its limitations.

References

• Growing industry interest in AI environmental impact reporting
• Some providers publish aggregate water usage in sustainability reports, but per-request metrics aren't yet common

Alternative Solutions

_No response_

Priority

Low - Nice to have

Feature Category

Other

Use Case Example

LIke the cost counter I would use this to prioritize my work and as a way to choose which Claude version was the most appropriate, this would also mean companies would have transparency for future reporting and accountability to customers about their usage, and real data to make decisions about the cost/benefit of having Claude or an employee do a task.

Additional Context

I believe this will be required in future, may as well get ahead of it. It will also be an incentive to find ways for LLMs to use less water and energy directly needed for humans.