# fix\(web,mobile\): replies show an overwritten image's current bytes · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/e8cf0c6193aed83173435541a9822b52deac9b3c)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: e8cf0c6193aed83173435541a9822b52deac9b3c

Requested commit: e8cf0c6193aed83173435541a9822b52deac9b3c

Commit: e8cf0c6193aed83173435541a9822b52deac9b3c

Tree: 916af65d570d45733243ed004403050e536d53b4

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(web,mobile): replies show an overwritten image's current bytes

An agent can overwrite a local image at the same path and embed it in a
new reply. The new reply reused the cached signed URL from the earlier
reply, so the browser showed the previous bytes until a reload.

Key each reply's media-file URL by a client-only cache revision (the
reply's message id). It is stripped before the RPC, so a new reply mints
its own URL while the existing atom TTL bounds the cache.

Fixes #15676

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

```

## Parents

- [b5a226e49c52ecab4ddc2d678a7012d97e651a6a](https://git.cafe/pingdotgg/t3code/commit/b5a226e49c52ecab4ddc2d678a7012d97e651a6a?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/e8cf0c6193aed83173435541a9822b52deac9b3c?format=markdown)