/goal command on mobile sets goal but agent doesn't start until user sends a follow-up

Summary

On Claude mobile (iOS), invoking \/goal <description>\ sets the goal but does not trigger the agent to begin work. The agent only starts after the user sends any subsequent message (e.g. "Are you working on the goal?"). This adds a friction step that isn't present on desktop and defeats most of the value of set-and-walk-away goals.

Environment

• Platform: iOS, Claude mobile app
• Version: v1.260604.0 (build 27047400567)
• Date observed: 2026-06-07

Reproduction

1. Open any active project in the mobile app.
2. Type \/goal <natural-language goal description>\ and send.
3. App replies with "Goal set: ..." (echo only).
4. Observed: no agent activity, no tool calls, indefinite idle.
5. Send any follow-up message (e.g. "Are you working on the goal?").
6. Agent then starts executing the goal as expected.

Expected behavior

Step 3 should immediately kick off agent execution against the goal, matching desktop behavior where \/goal\ triggers the run inline.

Actual behavior

The \/goal\ command is treated as a goal-setter only; no kickoff trigger is dispatched until the user sends a second message.

Impact

Mobile users:

1. Lose the ability to set-and-walk-away from a goal — must remain in the conversation to send a nudge before the agent will start.
2. Waste a round-trip on every goal.
3. Practically: defeats much of the value of \/goal\ over a normal prompt on mobile.

Likely a missing/extra-step dispatch trigger when the goal-creation path completes on mobile vs. desktop.