Missing a way to view *files* that were changed during the last run.

[Holokai]

Before opening, please confirm:

• I have searched for duplicate or closed issues

Operating System

Microsoft Windows NT 10.0.26200.0

Kiro Version

1.1.14

Bug Description

Kiro no longer provides a way to view the files changed by a previous agent run.

After an agent run modifies files and completes, its changed-file information is no longer available after moving to another run or returning to the completed run. The files remain modified on disk and are visible through Git/Source Control, but Kiro does not expose the run-specific list of changed files or its associated diffs.

This is a regression from the previous Kiro behavior, where completed runs retained a Changed Files/View Changes entry that allowed users to review exactly what each run modified.

The problem is especially disruptive when several runs occur in the same workspace because Git shows the aggregate working-tree changes but cannot identify which agent run produced each change.

Steps to Reproduce

1. Open a local multi-root workspace in Kiro 1.1.14.
2. Start an agent run and ask it to modify one or more files.
3. Wait for the run to complete.
4. Confirm that the files were changed through Source Control or git status.
5. Start another agent run, switch conversations, or otherwise navigate away from the completed run.
6. Return to the previous run.
7. Attempt to view the files changed specifically by that run.

Actual result:
There is no available Changed Files/View Changes view for the previous run, so its changed files and diffs cannot be reviewed from the run history.

Expected Behavior

Expected result:
Every completed local agent run should retain its Changed Files/View Changes view, including the list of files changed by that run and the corresponding diffs.

Conversation ID

No response

Additional Context

Environment: - Kiro: 1.1.14 - Commit: f694ef1b025756b1ae27ae7c3d9ed4215b0160fe - Architecture: x64 - OS: Windows NT 10.0.26200.0 - Shell: PowerShell 7.6.6 - Workspace type: Multi-root - Session type: Vibe - Execution: Local agent session

Impact:
This removes run-level change traceability. In a workspace with several agent runs, Source Control only shows aggregate uncommitted changes and cannot establish which run changed each file. Reviewing, accepting, reverting, or diagnosing one run independently is therefore substantially harder.

Regression:
This functionality was available before the recent Kiro update.

Related reports reviewed:

• Diff Viewer Not Rendering for Modifications #11209 concerns diff rendering for modifications.
• View changes button doesn't work. #11003 concerns a View Changes button that does not work in a multi-root workspace.
• This report concerns changed-file history becoming unavailable for previous/completed runs.

[github-actions]

🤖 Potential Duplicate Detected

This issue appears to be similar to:

• #11145: Missing ability to see modified files in each checkpoint (92% similar)
• #11003: View changes button doesn't work. (82% 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 report the same core problem: after a recent Kiro update, users can no longer view which files were modified by a specific completed agent run. Both describe this as a regression from previous behavior where file change information was accessible per-run, and both request that completed runs retain a way to review changed files and diffs.