# feat\(mobile\): show when an existing thread has a message waiting in the outbox · pingdotgg/t3code

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

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

Visibility: public

Requested revision: ef21dce3642fe6e3cea840d59fa7fbc0cb4604ee

Requested commit: ef21dce3642fe6e3cea840d59fa7fbc0cb4604ee

Commit: ef21dce3642fe6e3cea840d59fa7fbc0cb4604ee

Tree: 2f78df942518a25b328640912e192b39420e8690

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
feat(mobile): show when an existing thread has a message waiting in the outbox

A follow-up queued offline for an existing thread was invisible from the
thread list: the row looked idle and, if the server had settled the
thread, sat collapsed in the Settled shelf. Only opening the thread showed
"1 queued message will send automatically".

Threads with a queued message now read "Sends on reconnect" in the v2
status slot (same wording as a queued new task) and a neutral "Pending"
pill with the same subtitle in the v1 grouped list. A settled thread with
queued work is pulled back into the active block, and the v1 recency
window never trims it. Reorder planners see the same active set so Move
up/down stays consistent. Live states (approval, input, working, failed)
still outrank the queued one.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

```

## Parents

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

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