---
title: Screen library: every screen of every flow, searchable
description: The newest screenshot of every step across your flows in one gallery. Search by title, text, URL or step id before you design or build a screen that already exists.
seo_title: Screen library: search every screen your flows captured
seo_description: The newest screenshot of every step across your flows in one gallery, searchable by title, page text, URL or id, on the web, in the CLI and over MCP.
query: searchable library of app screenshots
kind: use-case
order: 15
updated: 2026-10-03
demo: false
---
A designer asks whether the app already has an empty state for the cart. Someone remembers seeing one, in some run, in some project. The screen library answers in a second, with the screenshot and a link to the step.

## The problem

Screens are captured in runs, and runs are sorted by scenario and date. To find a pattern you have to know where it was walked. So teams redraw dialogs and empty states that already exist, slightly differently each time.

## What changes with Kaloko

`/<org>/screens` on kaloko.app shows the newest capture of every step across the organization's flows, one tile per step. Search matches step and flow titles, ids, paths, URLs, the page title and the H1, and ignores diacritics. Filters narrow it to a project, product, module, locale, viewport, device, status or environment. It is in every plan.

## How it works

1. **Open the library**: **Screens** in the top navigation of kaloko.app, or `/<org>/screens`.
2. **Search**: type "empty cart", "košík" or a URL path; filter by project, locale or status (`fail` shows the screens that are broken right now).
3. **Open the step**: each tile links to the step on the canvas of its run, in the locale and viewport you picked.
4. **From the terminal**: `kaloko screens "empty cart" --project shop --locale en` lists the same, with the canvas link of each; `--designs` adds design versions, `--json` gives it to an agent. MCP agents call `search_screens`.

## Skills and prompts

```
Before you design the empty cart, look in the Kaloko screen library for empty states we already have and reuse their pattern.
```

Expected outcome: the agent runs `kaloko screens "empty" --designs`, names the screens it found with their links, and says which one it follows.

```
Which screens of the shop are failing right now?
```

Expected outcome: `kaloko screens --project shop --status fail` with each step and its link.

## What you get

- One place to see what the product looks like today, across projects and languages.
- Fewer duplicate patterns, because finding the existing one takes less time than drawing a new one.
- A starting point for docs and support: every tile links to the run it came from.

## FAQ

### Does it show old runs?

No. Each step shows its newest capture. Older captures stay in the runs and their history.

### Who sees which screens?

Everyone sees the screens of the projects they can open; restricted projects stay restricted.
