You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Mobile queues steers for ACP agents without native steering (e.g. Devin); web steers them #40560
🤖 Claude Opus 5.5 (via Devin) on behalf of @j-gaertig. Root cause from reading main @ 1a9a858; the symptom is reproduced daily on real devices.
Before submitting
I searched existing issues and did not find a duplicate.
I included enough detail to reproduce or investigate the problem.
Area
apps/mobile
Steps to reproduce
Follow-up behavior is Steer (the default) in the mobile app.
Open a thread on an ACP Registry agent that has no native steering, e.g. Devin (agentId: devin).
Send a prompt that keeps the agent busy for a while.
While the turn is running, send a follow-up from the mobile app. The send button says Steer; the result is the same with the explicit "Steer now" menu option.
Expected behavior
The follow-up steers the running turn, as it does when sent from web/desktop for the same thread (interrupt-and-restart for ACP agents).
Actual behavior
The follow-up is queued behind the running turn. It only reaches the agent after the turn ends, or after promoting it with "Steer now" in the queue.
Cause
Mobile maps the user's steer to the auto delivery intent, while web sends steer:
apps/mobile/src/state/use-thread-composer-state.ts (~L872–890): followUpAction === "steer" → dispatchMode: "auto" ("Steering uses "auto" so an ended turn queues a run instead of restoring the draft.").
apps/web/src/components/ChatView.logic.ts (turnDispatchMode) passes "steer" through, which becomes deliveryIntent: "steer" in packages/client-runtime/src/operations/commands.ts.
On the server, resolveDeliveryIntent in apps/server/src/orchestration-v2/CommandPolicy.ts only steers an auto message when the session reports supportsActiveSteering; otherwise, with supportsQueuedMessages, it returns queue_after_active (covered by CommandPolicy.test.ts). An explicit steer resolves to steer_active and runs as interrupt-and-restart.
Generic ACP sessions report supportsActiveSteering: false, supportsSteeringByInterruptRestart: true, supportsQueuedMessages: true (AcpProviderCapabilitiesV2), so on mobile every steer to them is queued. Mobile still shows Steer because canPromoteToSteer (threadWorkflows.ts) accepts interrupt-restart.
Affected: ACP Registry and Local ACP agents without steersWithPrompt / steering (Devin, CodeBuddy, Droid, GLM, Vibe, Kimi, ...). Not affected: Codex, Claude, Cursor, OpenCode, Pi, Grok, Kiro, Muse, Antigravity (native steering). Copilot queues on every client by design (#26715).
A likely fix is sending "steer" from mobile like web. One thing to check: an explicit steer right after Stop is refused while auto queues (Orchestrator.ts, stopReachedRun); web already behaves that way.
Related: #31336 (proposal that restart-only providers queue by default; not current behavior), #39344, #25749, #34267.
Impact
Major degradation or frequent failure
Version or commit
Server: t3 v0.1.12-nightly.20261121.5051 (code read on main @ 1a9a858)
Environment
T3 Code mobile app on iPad Air (M4, iPadOS) and Samsung Galaxy A55 (Android 16); server on Linux (CachyOS); provider: ACP Registry → Devin. Web/desktop on the same server steers correctly.
Workaround
Send, then open the queue and press "Steer now" on the queued message.
Activity