Skip to content

Show "Continue locally" button for in-progress cloud Oz runs#12626

Open
vkodithala wants to merge 1 commit into
masterfrom
oz-agent/continue-locally-button-in-progress
Open

Show "Continue locally" button for in-progress cloud Oz runs#12626
vkodithala wants to merge 1 commit into
masterfrom
oz-agent/continue-locally-button-in-progress

Conversation

@vkodithala

@vkodithala vkodithala commented Jun 14, 2026

Copy link
Copy Markdown
Contributor

Description

Show the "Continue locally" button in the side panel for in-progress cloud Oz runs, not just completed ones.

Previously the button was hidden whenever display_status.is_working() returned true (Queued/Pending/Claimed/InProgress/ConversationInProgress). This was inconsistent with /continue-locally, which has no status gate and calls the same underlying fork_ai_conversation path.

The only real prerequisite for the fork to work is a resolvable local AIConversationId (looked up via BlocklistAIHistoryModel::find_conversation_id_by_server_token). The is_working() check was an independent, redundant gate on top of that. Removing it makes the button available for any Oz task — in-progress or finished — as long as the client has a locally-tracked conversation.

Non-Oz harness guard (Claude Code, Gemini, Codex, etc.) is kept since those can't be forked locally.

Linked Issue

  • 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

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

Screenshots / Videos

Quick demo/explainer here! https://www.loom.com/share/6567567370704ad188d0e331360a0c51

Agent Mode

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

Conversation: https://staging.warp.dev/conversation/584a799d-44a4-4b06-abe7-05903da3894c
Run: https://oz.staging.warp.dev/runs/019ec6e1-589b-7c18-931a-5d2769359c44
This PR was generated with Oz.

The button was previously hidden whenever the task display status was
"working" (Queued/Pending/Claimed/InProgress/ConversationInProgress).
This was inconsistent with /continue-locally, which has no status gate
and calls the same fork path.

Since ContinueConversationLocally is just fork_ai_conversation, the
only real requirement is a resolvable local conversation ID. Remove the
is_working() guard so the button shows for any Oz task (in-progress or
finished) as long as the client has a tracked local conversation.

Co-Authored-By: Oz <oz-agent@warp.dev>
@cla-bot cla-bot Bot added the cla-signed label Jun 14, 2026
@vkodithala vkodithala requested a review from ianhodge June 15, 2026 16:20
@vkodithala vkodithala marked this pull request as ready for review June 15, 2026 16:20
@oz-for-oss

oz-for-oss Bot commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

@vkodithala

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

@oz-for-oss oz-for-oss Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overview

This PR removes the task display-status gate from the conversation details panel so the "Continue locally" CTA can appear for in-progress cloud Oz runs when a local conversation mapping exists, while retaining the AI-enabled and non-Oz harness guards.

Concerns

  • No blocking correctness, security, or spec-alignment concerns found in the changed lines.
  • No approved or repository spec context was provided for this PR, so there was no implementation/spec drift to flag.

Verdict

Found: 0 critical, 0 important, 0 suggestions

Approve

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

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