# Screens showing a change that was refused

Prompt · Agent harness and modern stack · G06

Finds screens that show a change right away and keep showing it after the server refused it.

## Prompt

```text
Trace every flow where the client updates UI state or local cache optimistically before server confirmation. Demonstrate what happens to user state, queued actions, and screen accuracy when the server rejects the mutation, times out, or returns canonical values that differ from the client's assumption.
```

**What it returns:** Each optimistic flow with a forced rejection and a screenshot or test of what the screen then shows.

**Skip it when:** Flows that wait for the server before updating the screen.

**Tools:** In-app browser or Playwright set to block or alter requests.

**Changes:** Adds a test that shows it

**Sessions:** One session

## Skills

- [diagnosing-bugs](https://www.atlasscope.dev/skills/diagnosing-bugs): Diagnosis loop for hard bugs and performance regressions.

## Related

- [Two systems that disagree](https://www.atlasscope.dev/prompts/two-systems-that-disagree): Finds data kept in two places (a saved copy and a table, the browser and the server) that can quietly disagree.
- [Status hidden in a pile of flags](https://www.atlasscope.dev/prompts/status-hidden-in-a-pile-of-flags): Finds features whose real status is spread across a pile of yes/no flags, so combinations that should be impossible can happen.

Source: https://www.atlasscope.dev/prompts/screens-showing-a-change-that-was-refused