Test: Convert a Codex Quick Chat into a workspace session

[sandy081]

Refs: #334250, #335008, #335247, #335253, #335255, #335337

• anyOS Aiday Marlen Kyzy (@aiday-mar)
• anyOS Dmitriy Vasyura (@dmitrivMS)

Complexity: 5

Authors: Sandeep Somavarapu (@sandy081)

Create Issue

---

Set up

• Open the Agents Window and start a workspace-less Quick Chat using the Codex Agent Host harness.
• Use Interactive mode with Default Permissions.
• Have at least two local project folders available.

Convert a Codex Quick Chat into a workspace session

1. Start with a useful request so the workspace-less Codex chat has conversation history. For example:
   Add a short welcome paragraph to the README in my vscode-tools project.
2. Verify Codex asks for the workspace and isolation choices using the structured question UI.
3. Select the target workspace and choose whether the work should use isolation.
4. Approve the workspace change when prompted.
5. Verify the same chat and native Codex thread become workspace-backed without losing the title, history, current request, selected model, or permission mode.
6. Verify Codex continues the original request after conversion and can inspect and modify files in the selected workspace.

Applied workspace and isolation

1. Repeat the conversion with isolation disabled and verify the session uses the selected project folder.
2. Repeat with isolation enabled and verify the session uses the created worktree rather than the original project folder.
3. Verify the UI and session metadata show the workspace that Codex actually applied, without temporarily reverting to the scratch directory or another folder.
4. Verify scratch ownership is released only after Codex confirms that the workspace update was applied.

Failure, cancellation, and unsupported states

1. Start another workspace-less Codex chat and cancel the workspace/isolation question or deny the workspace change.
2. Verify the chat remains workspace-less and usable, with its original history and permissions intact.
3. Try conversion while the Codex chat is busy, resuming, or otherwise not eligible.
4. Verify the conversion is rejected clearly without changing the working directory or losing the conversation.
5. If available, try a multi-root or unsupported target and verify it fails explicitly rather than reporting a successful conversion.

Switching, reload, and exploratory testing

1. Switch away from a converted Codex session and return, then reload the Agents Window.
2. Verify the selected workspace, isolation/worktree, title, history, permission mode, and model remain correct.
3. Try conversion before and after the Quick Chat has produced files, attachments, or tool results.
4. Exploratorily test different local projects, repeated conversion attempts, timeouts, and cancellation during the workspace update.
5. Verify ordinary Codex workspace sessions and Codex Quick Chats that are never converted continue to behave normally.

[aiday-mar]

I assume here isolation means using a worktree instead of working directly in the folder.

[aiday-mar]

Verified it works correctly