Feature Request: Storage retention/pruning settings for kiroagent globalStorage

[GerardDeLapelinDumont]

Kiro Product

IDE

Feature Description

Problem

~/Library/Application Support/Kiro/User/globalStorage/kiro.kiroagent/ grows unbounded. Reached 5.4 GB in ~3 weeks (796+ session files). No settings, commands, or docs for managing this storage.

kiro-cli has --delete-session for its SQLite DB, but Kiro IDE globalStorage has no equivalent.

Requested Features

1. Max storage size setting — auto-prune oldest sessions when limit reached
2. Retention period setting — auto-delete sessions older than N days
3. Manual prune command — e.g., /cache prune --older-than 7d
4. Storage usage visibility — show current usage via command or settings

Steps to Reproduce

1. Use Kiro IDE for 2-3 weeks across multiple workspaces
2. Check globalStorage folder — observe multi-GB growth
3. Search settings for storage limit or pruning — none exist

Use Case

SA using Kiro IDE daily across 6+ customer workspaces. On a 228 GB MacBook, the globalStorage consumed 5.4 GB in 3 weeks — nearly filling the disk alongside other dev tools. Had to manually investigate and identify the folder as the culprit. Users on smaller drives or heavier usage patterns will hit this faster.

Additional Context

The 5.4 GB breaks down as: ~4.8 GB conversation session files (JSON, ~2-3 MB each), ~564 MB LanceDB vector index. The session files are the growth problem — the index is reasonable. A simple retention policy on session files would address 90% of the issue.

[github-actions]

🤖 Potential Duplicate Detected

This issue appears to be similar to:

• #6359: Ephemeral session mode and session auto-cleanup (85% similar)
• #4760: Bulk Session Management (Delete/Archive Multiple Sessions) (85% similar)

What happens next?

• ⏰ This issue will be automatically closed in 3 days
• 🏷️ If this is not a duplicate, you can prevent automatic closure by adding a comment or reacting with 👎 to this message.
• 💬 Comment on the original issue if you have additional information

Why is this marked as duplicate?
Both issues address session storage management and cleanup functionality. Issue #6359 requests session auto-cleanup and ephemeral sessions, while the new issue requests storage retention/pruning settings for session files. Both identify the same core problem of session data accumulation without cleanup mechanisms.

[GerardDeLapelinDumont]

Reviewed the flagged potential duplicates — I don't believe this is a duplicate of either:

• Ephemeral session mode and session auto-cleanup #6359 (Ephemeral mode + auto-cleanup) targets kiro-cli session storage in the SQLite database (data.sqlite3).
• Bulk Session Management (Delete/Archive Multiple Sessions) #4760 (Bulk session management) targets the Kiro IDE session picker UI.

This issue (#6780) is about the Kiro IDE globalStorage/kiro.kiroagent/ folder on disk, which stores full conversation context snapshots as individual files. This folder grew to 5.4 GB in 3 weeks and is a separate storage layer from the session database. Deleting sessions via the session picker or CLI does not reclaim this disk space.

The specific problem: each conversation turn saves a full context snapshot (not incremental diffs), so long sessions on complex documents produce files of 15-20 MB each. A single heavy day generated ~1 GB of snapshot files.

Happy to close if the team confirms that fixing #6359 would also address globalStorage cleanup, but from what I can see these are independent storage mechanisms.

[github-actions]

Thank you for your feedback! 🙏

The duplicate label has been removed and this issue has been sent back for maintainer review.

A maintainer will review this issue shortly.