Skip to content

fix: propagate --conversation to SpawnAgentRequest for run-cloud#10524

Draft
liliwilson wants to merge 1 commit intomasterfrom
oz-agent/fix-run-cloud-conversation-propagation
Draft

fix: propagate --conversation to SpawnAgentRequest for run-cloud#10524
liliwilson wants to merge 1 commit intomasterfrom
oz-agent/fix-run-cloud-conversation-propagation

Conversation

@liliwilson
Copy link
Copy Markdown
Contributor

Description

The --conversation flag on agent run-cloud was parsed but never propagated to the SpawnAgentRequest. The conversation_id field was hardcoded to None in ambient.rs, so the server never received the conversation context.

Fix: pass args.conversation through to SpawnAgentRequest.conversation_id.

Linked Issue

  • REMOTE-1633

  • 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

Added a CLI-level test (agent_run_cloud_accepts_conversation_flag) that verifies --conversation parses correctly for run-cloud.

  • I have manually tested my changes locally with ./script/run

Agent Mode

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

Conversation: https://staging.warp.dev/conversation/02bfb4e3-783a-4ded-bb6a-52792364f74c
Run: https://oz.staging.warp.dev/runs/019e09ad-52e8-774e-afb0-0a561b8aa219
This PR was generated with Oz.

conversation_id was hardcoded to None in the run-cloud path,
so the flag was parsed but never sent to the server.

Co-Authored-By: Oz <oz-agent@warp.dev>
@cla-bot cla-bot Bot added the cla-signed label May 8, 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