Kiro stuck in Working? Check terminal output before clearing cache.

The Working state does not identify the cause. Preserve the Specs goal and project diff, test terminal output, and treat cache clearing as a later diagnostic step rather than a guaranteed fix.

Quick answer for Kiro clear cache: preserve git status, git diff, changed files, Specs goal, and the last terminal output first. Then disable shell themes or customizations, restart Kiro, test one simple command, and clear cache only if the interface still freezes.

What the failure looks like.

The entire IDE stops responding with no useful error. A Specs-mode task can appear frozen for hours even though the underlying project files and previous edits remain available.

Why it happens.

Kiro's official troubleshooting identifies shell customizations such as Oh My Posh and Powerlevel10k as common causes when Kiro stays in Working or cannot read terminal output. Cache corruption can also cause local client problems, but deleting cache should not be the first universal fix.

Fix it without losing the task.

Save project files and capture the current Git diff, Specs goal, and last terminal output before restarting the IDE.

Run one minimal terminal command. If output is missing, temporarily test with shell customizations disabled and compare the result.

Only consider clearing cache if the client remains wedged after the terminal check. Follow Kiro's current guidance and preserve settings before changing local data.

After Kiro reopens, verify the project root, run a harmless command, and compare the diff before continuing the interrupted task.

What the next AI should receive.

Specs goal, Kiro version, terminal command and output, shell-integration comparison, preserved project diff, any cache action taken, and the first harmless command after recovery.

Check before restarting

First test whether terminal output works with a minimal command and the normal shell configuration. If you test without shell customizations, change only that variable and preserve the project diff.

Boundary of the evidence

Kiro documentation identifies shell-integration trouble as one cause of Working or missing terminal output; it does not prove cache corruption or justify deleting cache as a universal fix.

Diagnostic checkpoint

Compare terminal behavior with shell integration enabled and disabled before considering cache changes.

How ShardStitch helps.

A handoff can preserve the Specs goal, changed files, and last visible terminal result while you troubleshoot Kiro locally. It cannot clear Kiro cache or establish that the IDE has recovered.

Research basis.

Kiro's official troubleshooting guide documents the Working-status and terminal-output failure, including shell-integration fixes. Cache clearing remains a secondary local-client step, not a guaranteed universal repair.

FAQ.

Should I clear Kiro cache whenever the IDE stays in Working?

No. First check terminal output and shell integration, which Kiro troubleshooting documents as possible causes. Treat cache clearing as a separate later step, not a universal fix.

How do I know the interrupted command completed?

Use the terminal output or process result, not the IDE status alone. If no completion result exists, label the command unverified and rerun it only after checking for side effects.

Scope note: Evidence boundary: the cited Kiro troubleshooting material supports checking shell integration and terminal output. Cache clearing remains a later, local troubleshooting option, not a documented guaranteed repair.