dsh-image-tiler

LIMITATIONS

Known limitations

- **A tiled upload costs more vision tokens than a single image.** Cutting one source into N pieces sends N images; that is the point, but a 20-tile upload is a much larger request than a 1-image upload. - **Tile size is capped by the store's normalization policy.** A tile larger than `normalizedImageMaxPixels` (4194304, i.e. about 2048x2048) is downscaled after the crop, which is why the planner fills the whole `maxImagesPerMessage` budget (20 by default) instead of using a few big pieces. - **The piece count follows `maxImagesPerMessage`, so a lower value gives worse tiles.** With the budget lowered to 6, an 8000x8000 source becomes five 4579x915 strips: complete and clear, but not the shape a reader would pick. The default of `20` produces the squarest layout. - **Several large uploads in one message share the budget.** Ten images at once leave two pieces each, below the four a layout needs to divide a source rather than shave it, so they are sent at the provider's print. Send large images one or two at a time when their detail matters. - **Tiles are whole regions, not overlapping pages.** A glyph on a seam is cut in half, and neither neighbouring tile shows it whole. - **Only the inline image path is tiled.** Files attached as documents, and images that arrive through other tools, are not. - The plugin was verified against `0.2.0-rc.2` on Windows. Other platforms are untested.