fix(mobile): keep queued follow-ups visible in the thread#25297

Approvability

Verdict: Approved at abe43ee

Macroscope's review found this PR approvable — Queued follow-ups remain visible in the mobile thread with clear Queued labels. The change uses existing queue state for presentation without altering message execution or persistence.

^{You can add or adjust custom eligibility rules. Learn more.}

Thread transfer impact

⚠️ The latest CI run did not produce a thread transfer result for ad115ac.

This comment will update automatically after the next completed run.

Review in Change Stack →

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

@shivamhwp, kept your implementation and commits: the server queue fills the gap after outbox acknowledgement, while preserving message IDs, metadata, order and duplicate suppression.

Merged current main (daa720a986ca) into the original branch and preserved both regression cases in the test conflict. Added one small correction: the feed now uses its existing nullable detail reference for the queue subscription. This prevents queued thread creation from fetching a missing thread and caching it as deleted. Final head: 0bd894cc8140877a9f00d0baf9c62229fd83a1aa.

Verification this run:

• Four existing feed regressions failed with current main's feed helper.
• Blacksmith vp run check:changed passed format, lint, both knip passes, typechecks for seven packages, and all 123 adjacent tests on the final code.
• Two independent source reviews have no remaining in-scope findings.

Unverified: iOS, native queued-to-running interaction, and fresh before/after mobile captures. The device service returned "Agent device access is turned off for this environment" and adb had no attached device. The web dev server started successfully and was stopped; web screenshots would not verify this mobile behavior. Existing PR media are prior evidence, not verification from this run.

Known nonblocking limit for @shivamhwp: legacy queued runs that already have transcript rows keep those rows without the new Queued badge. This predates the disappearance fix and was left outside its scope.

All 30 reported checks passed on this head. Macroscope approved it and CodeRabbit's new review found no actionable comments. Its description warning asks for scope documentation; this is the focused, reproducible disappearance bug tracked in https://github.com/pingdotgg/t3code/issues/25282, with no execution or queue-control changes.

Handoff: waiting on native device access for the requested interaction evidence. No replacement PR, labels, rebases, force-pushes or merges. No task-owned processes remain running.

Verified in a real dev environment

No changed runtime behavior could be verified on this Linux Boat VM. Result: unverifiable.

Read the description, discussion, reviews and full diff for head 0bd894cc8140877a9f00d0baf9c62229fd83a1aa (pingdotgg:issue-watch/25282). The PR is open and none of its listed commit authors match @juliusmarminge or @t3dotgg. The matching GitCafe PR is also #25297. Existing CI reports 30 successful checks, zero failing and zero pending. These checks were not reproduced this run.

The change renders server-queued follow-ups in the native mobile feed after outbox acknowledgement. Web does not render these changed mobile components.

Device discovery returned Agent device access is turned off for this environment. Local timeout 20 adb devices -l returned an empty device list. The mobile verification skill requires stopping when device access is unavailable. No development server was started, no source changed, and no commits or pushes were made.

Not verified

• Original bug on github/main and queued-message visibility on this head.
• Native composer -> server queue -> Codex gpt-6.1-sol -> running turn handoff.
• Nearby cancellation/editing, duplicate suppression, attachments/context and attributed queued rows.
• Android and iOS rendering, accessibility and interaction evidence.

No captures are attached because the required client flow could not be exercised. Existing PR media were not adopted as evidence from this run. Worktree installation and server startup were not attempted after confirming the native-device blocker. Verification needs an available native device and the supported Device service. No task-owned processes remain running.

Verified on Android emulator (API 35) against a real dev server

Verified head 0bd894cc8140877a9f00d0baf9c62229fd83a1aa on the t3 x86_64 emulator, API 35. Installed the matching native dev client from the shared cache (fingerprint ed36a9cc9856c84a322bb71e6d67744f0a00877d), served this head through Metro, and paired it to an isolated backend on port 13773 using .t3/userdata. Used the real server project and created a thread through the Android composer. All provider turns used Codex gpt-6.1-sol through this VM's local proxy. No mocks, Replay provider, projection fixtures, or demo data.

Sent a first turn that waits, then long-pressed Send and chose Queue for a follow-up. After acknowledgement, the follow-up stayed visible exactly once with Queued and 1 queued. When the first turn completed, the same follow-up remained exactly once, changed from Queued to a timestamp, and started its real Codex turn. The provider returned QUEUED FOLLOW-UP COMPLETE. Reopening the thread preserved the follow-up and response without duplication. A neighboring queue-sheet interaction promoted another queued message to steer; the feed changed to Steer, and the active Codex turn acknowledged it. Read-only inspection of the isolated database confirmed completed Codex runs and one persisted user message for the primary follow-up.

Before its run starts:

Android follow-up remains visible with Queued and one queued count

After its run starts:

The same Android follow-up has a timestamp and its real Codex turn is thinking

Queue selection, acknowledgement, queued-to-running handoff, and provider reply:

Android queue-to-running interaction against real Codex

The screenshots show two states on the PR head, not a main-versus-head comparison. Inspected the captures and checked uploaded video playback and seeking. No source changes, commits, or pushes were needed. GitHub reports 22 successful and 8 skipped checks, zero failing or pending; those checks were not rerun during this runtime-only verification. GitCafe renders the external uploads above as links; direct uploaded-video playback and seeking were verified. All task-owned backend, Metro and emulator processes have been stopped, and the disposable mobile connection was removed.

Not verified

• iOS: this Linux host cannot run iOS simulators.
• Original regression on github/main; this run exercised the exact PR head only.
• Queue cancellation/editing/reordering, attachments/context, attributed agent/automation rows, queued /compact, accessibility speech, dark theme, physical Android devices, and relay/tunnel connections. The attempted cancellation tap promoted the message to steer, so it is not claimed as cancellation proof.

merged main (b42adff3d77f) into the existing head without rebasing. resolved five conflicts, preserved main's removal of queue reordering, and used its queued-run message field to retain attribution. the resulting diff is seven files, 226 additions and 13 deletions against that main commit, smaller than the starting pr.

head: fed33b4c404bae1ff2d704c76bc5fdf9a43a6188.

blacksmith vp run check:changed b42adff3d77f01f5e0f5edfb5a071dabb535710b passed format, lint, both knip checks, seven package typechecks, 127 adjacent tests, and eight selected react compiler checks. the worker's shallow snapshot needed its comparison ancestry restored before this run. two independent read-only reviews approved this head with no findings. the earlier collapsed queued-label finding remains addressed.

fresh native interaction is unverified: device discovery returned "Agent device access is turned off for this environment." earlier android evidence in this discussion is prior evidence, not a fresh verification of the merge. no dev servers were started, and the task's testbox is stopped. new ci is pending; no failing checks reported yet.

merged current main into this branch in 306168a983 without rebasing. resolved both conflicts by preserving main's attachment layout and thread-family lifecycle changes, while retaining the queued feed hook and the queued label on the moved agent header. scope remains 7 files, 261 additions and 34 deletions against main.

blacksmith vp run check:changed 54c5f25249961a1aa0b61932329092eadbd9d6fc passed format, lint, both knip checks, seven package typechecks, 129 adjacent tests and nine selected compiler checks. the worker needed explicit base history because its source snapshot is shallow.

both prior bot findings are already addressed. fresh native verification remains unverified: device access is disabled and this vm has no connected android device. existing android evidence remains in the description. waiting for the new head's ci and independent source reviews.

306168a983 now has all checks completed with no failures. github confirms mergeable with no conflicts, and both review threads are resolved. two independent source reviewers approved this exact head with no blocker or should-fix findings. blacksmith scoped verification passed, including 129 tests.

fresh native verification remains unverified because device access is disabled in this environment. the queue-to-start interaction still needs a real mobile client check. no new visual behavior was introduced in this pass; the existing android evidence covers an earlier head. no further code changes are proposed.