Config Wizard: configuring the Teams channel times out

[Stevenic]

To setup the Teams channel, OpenClaw needs to first download and install the plugin and then run you through a configuration process. Selecting the Teams Channel timed out for me (I think it said it had a 60 second timeout.) The bigger issue is that I then had to skip the wizard so I lost all of my other settings.

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed June 2, 2026, 6:00 PM ET / 22:00 UTC.

Summary
Keep open: current main still has a plausible wizard timeout path for slow channel/plugin steps, and I did not find a merged fix or canonical replacement for the Teams-specific failure and settings-loss report.

Reproducibility: no. high-confidence live reproduction was established. Source inspection does show that slow non-login wizard.next steps use a short timeout and then move to an error/skip path, which matches the reported failure shape.

Ways to help us reproduce this

• Add a screenshot or short recording showing the behavior.
• Add expected vs actual behavior.

Next step
A focused repair PR can investigate the wizard timeout/recovery path in the Windows setup host while leaving gateway-side Teams plugin behavior unchanged unless source evidence shows a required interface adjustment.

Review details

Best possible solution:

Fix the setup wizard host so slow channel/plugin install steps can complete or recover without forcing users to abandon prior wizard answers, and coordinate with the gateway only if its own timeout is the limiting path.

Do we have a high-confidence way to reproduce the issue?

No high-confidence live reproduction was established. Source inspection does show that slow non-login wizard.next steps use a short timeout and then move to an error/skip path, which matches the reported failure shape.

Is this the best way to solve the issue?

Unclear until the exact Teams gateway behavior is checked, but the narrowest repo-local repair is to improve SetupEngine UI/shared wizard timeout and recovery handling for slow channel/plugin/progress steps before adding Teams-specific logic.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• The Teams-specific gateway/plugin implementation is not in this checkout, so a complete fix may need coordination if the gateway itself enforces the reported 60-second timeout.
• I did not run a live Teams setup flow in this read-only review; the current-main evidence is source-level timeout and recovery behavior rather than an end-to-end reproduction.

Codex review notes: model gpt-5.5, reasoning high; reviewed against db30e6089125.

Label changes

Label changes:

• add P2: The report describes a setup wizard failure with limited blast radius but real first-run configuration impact.
• add impact:data-loss: The user reports losing previously-entered setup settings after the timeout forced them to skip the wizard.
• add issue-rating: 🐚 platinum hermit: Current issue advisory state selects this label.
• add clawsweeper:needs-live-repro: Current issue advisory state selects this label.

Label justifications:

• P2: The report describes a setup wizard failure with limited blast radius but real first-run configuration impact.
• impact:data-loss: The user reports losing previously-entered setup settings after the timeout forced them to skip the wizard.

Evidence reviewed

Acceptance criteria:

• ./build.ps1
• dotnet test ./tests/OpenClaw.SetupEngine.Tests/OpenClaw.SetupEngine.Tests.csproj --no-restore
• dotnet test ./tests/OpenClaw.Shared.Tests/OpenClaw.Shared.Tests.csproj --no-restore
• dotnet test ./tests/OpenClaw.Tray.Tests/OpenClaw.Tray.Tests.csproj --no-restore

What I checked:

• Issue report: The issue body says the Teams channel setup timed out during plugin download/install/configuration and that skipping the wizard caused previously-entered settings to be lost.
• Repository policy: AGENTS.md was read fully; its onboarding and connection guidance directed the review to the setup wizard, gateway wizard RPC, and gateway credential/client flow. (AGENTS.md:1, db30e6089125)
• Wizard contract: The onboarding docs describe the gateway setup page as server-defined wizard RPC via wizard.start and wizard.next, with progress steps and recovery choices when the connection is lost. (docs/ONBOARDING_WIZARD.md:29, db30e6089125)
• Current UI timeout path: WizardPage sends wizard.next through SendWizardRequestAsync using TimeoutForCurrentStep, which only extends to 300 seconds for device/authorize/login/sign-in/oauth wording and otherwise uses 30 seconds. (src/OpenClaw.SetupEngine.UI/Pages/WizardPage.xaml.cs:430, db30e6089125)
• Timeout exception source: The shared gateway client removes the pending wizard response and throws TimeoutException when a wizard response does not arrive before the supplied timeout. (src/OpenClaw.Shared/OpenClawGatewayClient.cs:489, db30e6089125)
• Skip-after-error path: After an error, WizardPage offers Start wizard again or Skip wizard; skipping navigates onward to permissions/complete rather than preserving an in-progress wizard session. (src/OpenClaw.SetupEngine.UI/Pages/WizardPage.xaml.cs:629, db30e6089125)

Likely related people:

• Régis Brid: Current blame for the SetupEngine UI wizard timeout, error, skip, and shared wizard request code points to commit 7d9152f on the current release line. (role: current implementation provenance; confidence: medium; commits: 7d9152f427a3; files: src/OpenClaw.SetupEngine.UI/Pages/WizardPage.xaml.cs, src/OpenClaw.Shared/OpenClawGatewayClient.cs, src/OpenClaw.SetupEngine/SetupWizardRunner.cs)
• Ranjesh Jaganathan: Recent history includes setup wizard restart recovery and setup-managed WSL follow-up work, both adjacent to the reported timeout/recovery behavior. (role: recent setup wizard recovery contributor; confidence: high; commits: 623427cead04, f4d4793f744f; files: src/OpenClaw.SetupEngine.UI/Pages/WizardPage.xaml.cs, docs/ONBOARDING_WIZARD.md)
• Mike Harsh: Earlier V2 setup conversion work and the prior none-channel wizard hang fix are adjacent to channel-selection wizard behavior, though the current file has since moved to SetupEngine UI. (role: adjacent setup flow contributor; confidence: medium; commits: 58315446796e, 679f21cea559; files: src/OpenClaw.Tray.WinUI/Onboarding/GatewayWizard/GatewayWizardPage.cs, src/OpenClaw.Tray.WinUI/Services/LocalGatewaySetup/LocalGatewaySetup.cs)

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.