Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[P0][Bug]: Native Store Gateway onboarding requires manual clawctl setup before the wizard can continue

Open
  • Is something wrong?
#1,672 4 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
desktop

Research direction

Start with NativeGatewaySetupService.CreateDraftAsync and PrepareAsync in src/OpenClaw.SetupEngine/NativeGatewaySetupService.cs, then trace the automatic setup call in src/OpenClaw.SetupEngine.UI/NativeGatewaySetupHost.cs. Reproduce with an installed supported package whose isolated-session helper needs staging, and inspect the existing regression tests for credential-handoff checks. Done means onboarding prepares the Gateway or presents an actionable readiness failure without requiring manual clawctl setup.

Written by the indexing model from the issue text.

Description

clawsweeper:needs-maintainer-review clawsweeper:no-new-fix-pr impact:ux-release-blocker issue-rating: 🦪 silver shellfish P0

Bug

Requested priority: P0. Native Store onboarding blocks users until they run an external repair command.

Microsoft Store Companion native Gateway onboarding stops at Prepare your Gateway profile with an unsupported isolated-session contract error. Running the installed Store Gateway's clawctl setup --json manually, then clicking Retry setup, allows the wizard to continue using the same installed package versions.

The wizard should prepare the supported Gateway automatically. A user should not need to leave onboarding and run a terminal command.

Reproduction

Observed once on October 7, 2026:

  1. Uninstall the existing developer Companion package and back up the previous Companion profile.
  2. Install Companion from Microsoft Store, product 9NFPR3BGDRR5, and launch with a fresh Companion profile.
  3. Select Install a local native gateway, the recommended option on this host.
  4. Let the wizard install Gateway from Microsoft Store, product 9NV70LV3D6XC.
  5. Observe that Check device support and Install or verify Gateway package complete, but Prepare your Gateway profile shows Needs attention. Start and verify the Gateway remains waiting.

This was an existing development machine with a fresh Companion profile. Gateway/session state was not deliberately reset before the test. A factory-clean machine and a current-main build have not been tested for this failure.

Expected behavior

The wizard initializes or safely repairs the supported native Gateway and continues without a manual clawctl setup invocation. If preparation cannot proceed, it surfaces the actual readiness problem with an actionable recovery path.

Actual behavior

The wizard displays:

The installed Gateway MSIX does not expose Companion's isolated-session contract. Update the Gateway MSIX, then retry setup. Credentials were not sent.

The installed Gateway CLI, invoked in the signed-in Windows user's interactive session, reported that the isolated-session helper had not been staged for this package version and directed the user to run clawctl setup again.

Environment

Component Observed version
Companion MSIX OpenClawFoundation.OpenClaw, 2026.9.520.0, ARM64
Gateway MSIX OpenClawFoundation.OpenClawGateway, 2026.9.701.0, ARM64
Package provenance Both SignatureKind=Store, Status=Ok
Windows Windows 11 Enterprise Insider Preview, 26H1, ARM64, 28120.3151
GPU NVIDIA RTX Spark N1X, 6144-core Blackwell RTX GPU
NVIDIA driver 616.00

Companion package family: OpenClawFoundation.OpenClaw_rfcbke2p71se2.
Gateway package family: OpenClawFoundation.OpenClawGateway_rfcbke2p71se2.

The wizard's native device-support check passed on this Windows build. The observed failure occurred later during Gateway profile preparation, and the workaround succeeded without a Windows update.

No source build, developer MSIX replacement, or WSL fallback was used for the successful run.

Workaround and observed recovery

Ran the installed Store Gateway's package-qualified alias with setup --json in the signed-in user's interactive Windows session. Equivalent PowerShell:

$package = Get-AppxPackage -Name OpenClawFoundation.OpenClawGateway
$clawctl = Join-Path $env:LOCALAPPDATA ('Microsoft\WindowsApps\' + $package.PackageFamilyName + '\clawctl.exe')
& $clawctl setup --json

The command reported success, a ready isolated session, and integration isolated-session version 1. Clicking Retry setup then allowed native onboarding to continue. Neither MSIX was updated between failure and recovery.

Completed Local AI installation through the wizard. It reached Your AI is ready with verified model llamacpp/qwen3.6-35b-a3b-mtp-ud-iq4-xs. After the setup-driven app restart, Chat showed Owner Connected, and Qwen 3.6 correctly answered 56 for 7 × 8. The app, native Gateway, and Local AI were left running.

Evidence

Original wizard failure:

Native Store onboarding fails at Gateway profile preparation

Wizard success after the manual command and retry:

Local AI wizard succeeds after native Gateway repair

Working local Chat after setup and restart:

Local Qwen 3.6 replies with the test nonce and 56 while Owner is connected

These are original screenshots from the observed run. A terminal screenshot of the repair command was not captured; the workaround above records the command that was invoked. The first failing package JSON response was not retained.

Investigation lead

The inspected source checks the package contract before preparing the package:

This ordering is consistent with an initialization/readiness failure stopping onboarding before automatic setup can repair it. It is an investigation lead, not a confirmed root cause. Regression coverage should include an installed supported package whose helper needs staging, and should preserve the existing credential-handoff checks.

Related merged work: #1553 (fix: Companion cannot onboard with an isolated Gateway), openclaw/openclaw-windows-packaging#134 (fix: Companion cannot configure an isolated Gateway), and #1649 (fix: Companion fails to reconnect after isolated session replacement). None was confirmed as an exact duplicate of this first-run failure.

Dominant language
C#
Stars
2.1k
Forks
315
Avg merge
2d 1h
Merged PRs (30d)
127

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openclaw/openclaw-windows-node

All issues in openclaw/openclaw-windows-node

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.