Unbounded growth of spec execution history in globalStorage (~8GB+ / 6000+ files)

[haabe]

Before opening, please confirm:

• I have searched for duplicate or closed issues

Operating System

MacOS Tahoe

Kiro Version

0.6.32

Bug Description

Kiro is currently storing 6,422 execution log files (including failed ones) and never cleaning them up. Each file contains the full context of a spec generation run, including your prompts and environment context.

• Location: ~/Library/Application Support/Kiro/User/globalStorage/kiro.kiroagent///
• File count: 6,422 files
• Total size: ~8.2GB (21GB across all workspaces)
• File type: JSON execution logs with workflowType: "spec-generation"
• Issue: No cleanup/rotation of old or failed executions

Steps to Reproduce

1. Work with Kiro over time
2. See the execution log grow

Expected Behavior

Execution history should have retention limits

Conversation ID

No response

Additional Context

No response

[clx-jlmoreno]

Confirming this issue with even larger scale:

Environment:

• macOS 14.x, Kiro IDE 0.x (latest preview)
• Location: ~/Library/Application Support/kiro/User/globalStorage/kiro.kiroagent/

Storage Growth:

• 13GB total across all sessions
• 8,670 chat files in active session alone
• Multiple old project sessions (1.7GB, 143MB, 72MB each)

Breakdown:

$ du -sh ~/Library/Application\ Support/kiro/User/globalStorage/kiro.kiroagent
13G     kiro.kiroagent

# Session directories:
12G     d1c95acd1215dbe372efb48819c04345/  (current project)
1.7G    c0a23e81228432f1086bb8684f5c0604/  (old project)
143M    b1a9dfdf8e3da69e70d440745dabdb5f/  (old project)

Impact:

• No built-in cleanup mechanism in IDE or CLI
• Manual deletion required: rm -rf <session-hash>/
• Storage grows unbounded over 3+ months of active use

Workaround Used:
Manually deleted old project sessions, saved ~3GB. Current project still 12GB with no way to prune old chat history while keeping task tracking.

Suggested Solution:

• IDE Command: Cmd+Shift+P → "Kiro: Manage Storage"
• Settings UI: Visual breakdown + cleanup options
• Retention policy: kiro.storage.retentionDays setting
• Similar to VS Code's "Developer: Clean Workspace Storage"

This is a critical UX issue for long-term Kiro IDE users.

[morozow]

I've submitted a PR with a storage cleanup utility that helps reclaim disk space consumed by Kiro without breaking anything.

What it solves:

• Removes duplicate conversation history and old workspace snapshots
• Safely deletes file version cache that accumulates over time
• Gives you control over what to delete and how old it should be

What it preserves:

• Active sessions and current workspace data
• Code search index
• All configuration files

The script requires explicit confirmation before deleting anything, so you can review what will be removed first.

PR: #5755