[Windows] MCP server log files grow unbounded, consuming 18+ GB of disk space

[JWVENTURE]

Bug Description

MCP server log files in Warp on Windows grow without any size limit or rotation, consuming massive amounts of disk space. A single log file reached 16.4 GB and total MCP logs consumed 18.3 GB across 1,423 log files.

Environment

• OS: Windows 11 Home Single Language (10.0.26200)
• Warp Version: v0.2026.03.25.08.24.stable_05
• Architecture: x64
• Install Method: winget (Warp.Warp)

Disk Usage Breakdown

AppData\Local\warp\Warp\data\logs\mcp\
  3015eae1-de41-4460-bedd-6b015ee59e8d.log    16,456 MB (16.4 GB!)
  b23235ab-8257-4fd5-8d13-213a51d8fa50.log     1,751 MB (1.7 GB)
  e8aad4f7-e47f-4b68-84d4-a56530df41fc.log       119 MB
  46b32854-8fc8-49e4-a5f9-1cf45b94df37.log         3.8 MB
  c78da7ed-05b0-4c94-a36e-52e533313afe.log       0.9 MB
  ...

Total: 1,423 log files = 18,340 MB (18.3 GB)

Other Warp data:

warp.sqlite                                91 MB
AppData\Roaming\warp                     25 MB
Program Files\Warp                        ~200 MB (installation)
------------------------------------------
TOTAL WARP FOOTPRINT                      ~18.7 GB

Steps to Reproduce

1. Use Warp on Windows with MCP servers configured (Claude Code MCP, etc.)
2. Run development sessions that generate MCP traffic
3. Observe that log files in AppData\Local\warp\Warp\data\logs\mcp\ grow indefinitely
4. No rotation, truncation, or size limit is applied

Expected Behavior

• MCP log files should have a maximum size limit (e.g., 10-50 MB per file)
• Old log entries should be rotated or truncated
• Total log storage should be bounded (e.g., 500 MB max)
• User should be able to configure log retention settings

Actual Behavior

• Log files grow unbounded to 16+ GB each
• No rotation or truncation occurs
• Total disk usage can reach 18+ GB from logs alone
• No user-configurable settings to control log size

Workaround

Manually delete log files:

Remove-Item "$env:LOCALAPPDATA\warp\Warp\data\logs\mcp\*.log" -Force

This frees up ~18 GB but logs will grow unbounded again.

Impact

• Severe - Can consume entire SSD storage
• Particularly bad for developers on smaller SSDs (128GB/256GB laptops)
• No warning or notification to the user
• Silent disk space consumption

Suggested Fix

1. Log rotation: Rotate log files at a configurable size limit (default 50 MB)
2. Retention policy: Delete logs older than N days (default 7)
3. Total cap: Enforce maximum total log storage (default 500 MB)
4. Settings UI: Add log management to Warp Settings
5. Periodic cleanup: Background task to clean old/large logs

Additional Context

• The SQLite database (warp.sqlite) is 91 MB which seems reasonable
• This only affects MCP logs, not the main warp.log files which appear to have some rotation
• The log file names appear to be UUIDs suggesting they are per-session or per-MCP-server

[JWVENTURE]

UPDATE: Actual disk usage is 83 GB, not 18 GB

Initial report underestimated the impact. A deeper scan revealed the true scale:

AppData\Local\warp\Warp\data\logs\    85,118 MB (83.1 GB)
  - 1,438 log files
  - Total AppData\Local\warp footprint: 83.23 GB

This makes Warp the single largest consumer of disk space on a 928 GB drive (83 GB out of 666 GB used = 12.5% of all used space).

For context, the next largest consumers are:

• Downloads: 69.78 GB (user files)
• Claude Desktop: 13.81 GB
• Google Chrome: 13.08 GB
• Docker: 9.09 GB

83 GB for terminal logs is absolutely unacceptable.

Updated severity: CRITICAL

This is not just a minor annoyance - on a 256 GB laptop SSD, Warp would consume 32% of the entire drive with log files alone.