openclaw / openclaw/openclaw-windows-node
Mobile app pairing fails (falls back to TUI)
Open
Nobody has claimed this yet.
impact:auth-provider
impact:ux-release-blocker
issue-rating: 🦪 silver shellfish
P0
stale
- Dominant language
- C#
- Stars
- 2.1k
- Forks
- 295
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 99
Description
Problem: The mobile app fails to pair with the node; the flow falls back to the TUI instead of completing mobile pairing.
Impact: Pairing - mobile onboarding path is broken.
Epic: should ladder up to #835 (S2 - Connect & pair).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the mobile pairing flow and tracing where it falls back to the TUI. Identify the pairing entry point and any existing pairing tests, then verify that a mobile pairing attempt completes successfully without entering the TUI fallback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100