kiro-fix-session-images

Repair Kiro CLI sessions that stopped working with this error:

At least one of the image dimensions exceed max allowed size for many-image requests: 2000 pixels

A screenshot larger than 2000px (usually a Retina capture) gets stored in the session history, so every later request that replays it fails. This tool scans each session's transcript, downscales every embedded image above the limit to 1900px on its longest side, and rewrites the file in place. The original is kept next to it with .bak added to its name.

Warning: Close the session in Kiro before running, then resume it.

Install

With uv (recommended):

uv tool install kiro-fix-session-images

Or run it once without installing:

uvx kiro-fix-session-images --all --dry-run

Or with pip:

pip install kiro-fix-session-images

Quick start: fix a broken session

Works for Kiro CLI and Kiro IDE sessions, in both on-disk layouts: ~/.kiro/sessions/<hash>/<id>/messages.jsonl and the flat ~/.kiro/sessions/cli/<id>.jsonl. A session's sub-agent transcripts (sub-executions/) are repaired along with it.

1. Exit the broken session. In Kiro CLI type /exit; in Kiro IDE close the chat tab. Kiro must not be writing to the session file while it is repaired.

2. Pick the session and fix it. cd into the project directory and run:

cd /path/to/your/project
uvx kiro-fix-session-images

A list of this directory's sessions opens (every directory's, if this one has none), newest first, each marked ok or N oversized. Type to filter (title, id or workspace), use the arrow keys to move, and press Enter to fix the highlighted session. Tab switches to sessions from every directory; Esc quits without changing anything.

Prefer to fix everything at once? uvx kiro-fix-session-images --all.

3. Resume the session.

kiro-cli chat --resume                  # Kiro CLI: most recent session here
kiro-cli chat --resume-id sess_<id>     # Kiro CLI: a specific session

In Kiro IDE, reopen it from the session history list.

If the session still fails, put the original back by copying the .bak file over the transcript. Where that is depends on the layout:

# directory layout (Kiro CLI and IDE)
cd ~/.kiro/sessions/<hash>/<id>
cp messages.jsonl.bak messages.jsonl
cp sub-executions/<uuid>.jsonl.bak sub-executions/<uuid>.jsonl   # if one was repaired

# flat layout
cd ~/.kiro/sessions/cli
cp <id>.jsonl.bak <id>.jsonl

Sub-agent transcripts that the flat layout links through parent_session_id in <id>.json are listed and repaired as sessions of their own, not with their parent.

Usage

# Pick a session from a list (run inside the project directory)
kiro-fix-session-images

# List sessions for this directory with their IDs and status, then exit
kiro-fix-session-images --list
kiro-fix-session-images --list --title deploy   # match title, id or workspace
kiro-fix-session-images --list --all            # every directory

# Fix one session by ID (CLI sess_<id> or the bare IDE id both work)
kiro-fix-session-images sess_<id>

# The sess_ prefix is added automatically if you omit it
kiro-fix-session-images <id>

# Fix every session
kiro-fix-session-images --all

# Report what would change without touching any file
kiro-fix-session-images --all --dry-run

# Use a smaller target size (default 1900, must be below 2000)
kiro-fix-session-images --all --max 1600

# Scan a different sessions directory (default ~/.kiro/sessions)
kiro-fix-session-images --all --root /path/to/sessions

Each affected session is printed as <id>: resized X/Y images, followed by a done: N oversized image(s) fixed summary. A repaired sub-agent transcript is printed under its session as <id> (sub-execution <uuid>): resized X/Y images. With --dry-run the wording changes to would resize and found.

How resizing works

Images are resized with Pillow, which is installed as a dependency, and saved back in their original format (PNG, JPEG, GIF or WEBP) with their EXIF metadata and color profile intact. Animated GIF and WEBP keep every frame.

If an image can't be read, that image is skipped and reported as N unreadable. The other images in the session are still fixed, the rest of the run continues, and the exit status is 1. --dry-run reports and exits the same way, so it tells you in advance what the real run cannot repair.

Platforms

macOS, Linux and Windows. Requires Python 3.9 or newer.

License

MIT