Skip to content

Fix slash command skills bypassing cloud mode in old UI#9978

Draft
harryalbert wants to merge 1 commit intomasterfrom
oz-agent/REMOTE-1544
Draft

Fix slash command skills bypassing cloud mode in old UI#9978
harryalbert wants to merge 1 commit intomasterfrom
oz-agent/REMOTE-1544

Conversation

@harryalbert
Copy link
Copy Markdown
Contributor

Description

Fix slash command skills bypassing cloud mode in the old cloud mode UI.

When a user typed a skill command (e.g. /some-skill) in the old cloud mode UI (i.e., when the CloudModeInputV2 feature flag is disabled), the command was routed through execute_skill_command which enters the local agent view and sends the request locally—bypassing cloud mode entirely.

The V2 UI already handled this correctly by returning false from maybe_handle_enter_for_slash_command when is_cloud_mode_input_v2_composing was true, letting the flow fall through to submit_ai_queryspawn_agent (the cloud mode path).

The fix introduces is_composing_cloud_mode_prompt, which checks CloudMode + is_configuring_ambient_agent without requiring the V2 flag. The SkillCommand guards in both maybe_handle_enter_for_slash_command and maybe_handle_cmd_or_ctrl_shift_enter_for_slash_command now use this broader check, so skill commands in cloud mode setup are correctly submitted through the cloud agent spawn path regardless of which input UI is active.

Linked Issue

Resolves REMOTE-1544

  • The linked issue is labeled ready-to-spec or ready-to-implement.
  • Where appropriate, screenshots or a short video of the implementation are included below (especially for user-visible or UI changes).

Testing

  • Verified compilation passes with cargo check -p warp.
  • Verified cargo fmt passes.
  • The change is minimal and follows the exact pattern already used by the V2 UI for the same scenario.

Agent Mode

  • Warp Agent Mode - This PR was created via Warp's AI Agent Mode

Conversation: https://staging.warp.dev/conversation/fada95ad-b0b0-4153-a682-747e44e28a0a
Run: https://oz.staging.warp.dev/runs/019dee48-2851-73a7-923f-1c4da590b296
This PR was generated with Oz.

When a skill command (e.g. /some-skill) was typed in the old cloud mode
UI (CloudModeInputV2 flag disabled), it was routed through
execute_skill_command which enters the local agent view and sends the
request locally, bypassing cloud mode entirely.

The V2 UI already handled this correctly by returning false from
maybe_handle_enter_for_slash_command when is_cloud_mode_input_v2_composing
was true, letting the flow fall through to submit_ai_query which handles
the cloud mode spawn_agent path.

This fix broadens the guard from is_cloud_mode_input_v2_composing (which
requires the V2 flag) to is_composing_cloud_mode_prompt (which only
checks CloudMode flag + is_configuring_ambient_agent), covering both old
and new cloud mode UIs.

Co-Authored-By: Oz <oz-agent@warp.dev>
@cla-bot cla-bot Bot added the cla-signed label May 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant