Suggestion: Improve Beginner Setup Guide for WSL Users and Add Text Input to WebSim UI

[asmoabdullahofficial]

Idea Description

As a non-technical beginner trying to set up OM1 on Windows with WSL (Ubuntu), I faced several issues that made the process frustrating. The current docs are good for basics, but lack details for common WSL problems. Also, the WebSim UI at http://localhost:8000/ is monitoring-only, with no text input for commands, making interaction hard without voice (which didn't trigger for me). Suggesting improvements to make OM1 more accessible for beginners.

Problems Faced (From My Experience)

• WSL Network Issues: sudo apt update often failed with "Network is unreachable" errors. Fixed by restarting WSL (wsl --shutdown in PowerShell), but docs don't mention this.
• Build Errors During uv sync: Errors like "command 'cc' failed" (missing compiler) and "portaudio.h: No such file or directory" (missing dev packages). Fixed by installing build-essential and portaudio19-dev, but not covered in docs for WSL users.
• Config Syntax Errors: Editing config/spot.json5 for api_key led to repeated "Unexpected '"' at column 29" due to quotes/commas. Hard for beginners without JSON knowledge.
• UI No Interaction Options: WebSim shows state (e.g., "wag tail", "excited"), but no text box or mic button for commands. Voice didn't respond, and no fallback.
• Credits Not Used & Blockchain Error: After run, portal shows $0 used, and terminal logs "Loading rules from Ethereum blockchain failed with 503" – temporary but confusing for new users.

Proposed Improvements

• Enhance Docs for WSL: Add a WSL-specific section with steps for network fixes (wsl --shutdown), required packages (sudo apt install build-essential portaudio19-dev ffmpeg git python3-dev -y), and config editing tips (e.g., use unquoted keys, always add comma).
• Add Text Input to WebSim UI: Include a simple chat box for typing commands (e.g., "Hello Spot"), as fallback to voice. This would trigger LLM responses and credits usage more reliably.
• Error Handling Tips: Add troubleshooting for common errors like 503 blockchain (wait/retry) and credits not deducting (ensure interaction triggers API calls).

Benefits

• Reduces beginner drop-off (I spent hours troubleshooting with AI help).
• Makes OM1 more inclusive for non-devs.
• Improves testing – text input would confirm API/credits work.

Thanks for the project – excited to see it grow!

[Prachi1615]

Hi @asmoabdullahofficial
We don't plan on adding support for windows or wsl setup.
We support ubuntu and Mac.