Loading...
Loading...
Common issues and their solutions. Most problems have a quick fix.
Windows Defender may quarantine the app on first run. Go to Windows Security → Virus & threat protection → Protection history and allow WindOp.
Right-click WindOp in the Start Menu and select "Run as administrator". Some Windows configurations require elevated permissions for first launch.
Ensure you're on Windows 10 or 11, 64-bit. WindOp requires the Visual C++ Redistributable (usually pre-installed on modern Windows).
Go to openrouter.ai → Keys and confirm your key is active. Keys start with "sk-or-". Copy the full key — partial keys won't work.
OpenRouter free tier has limits. Go to openrouter.ai → Credits to check your balance. Some models require a positive balance.
Press Ctrl+M and switch to a different model. Some models may be temporarily unavailable or rate-limited.
If you're on Pro, go to Settings → Account and verify your subscription is active. Expired subscriptions fall back to BYOK mode.
WindOp needs a stable internet connection for AI model access. Test at fast.com. Latency to OpenRouter's servers matters more than raw bandwidth.
Large models (Claude Opus, GPT-5.4) are slower than smaller ones. For quick tasks, try Gemini Flash, GPT-5.4-mini, or DeepSeek V3.2.
Long conversations send more context to the model, which takes longer. Start a new conversation (Ctrl+N) for unrelated tasks.
Visit openrouter.ai/status to check if there are any ongoing outages or degraded performance.
Ensure the file isn't read-only and you have write permissions. Right-click → Properties → uncheck Read-only.
If the file is open in VS Code, Notepad++, or another editor, it may be locked. Close it and try again.
WindOp uses fuzzy matching for edits. If the exact text isn't found, it tries 9 different matching strategies. You can also ask WindOp to show you the file first, then make the edit.
WindOp creates backups before edits. If something goes wrong, ask WindOp to restore from backup.
Some commands require a specific execution policy. Run `Get-ExecutionPolicy` in PowerShell. If it's "Restricted", you may need to run `Set-ExecutionPolicy RemoteSigned` as Administrator.
Tools you're trying to use must be in your system PATH. Run `where <tool>` to check. If not found, add the tool's directory to PATH.
If auto-detection picks the wrong shell, explicitly ask WindOp to use PowerShell, CMD, or WSL: "Run this in PowerShell: ..."
For Linux commands, WSL must be installed. Run `wsl --list` in CMD to verify. Install with `wsl --install` if needed.
Some Windows configurations block screen capture. Ensure WindOp has permission to capture your screen in Windows Settings → Privacy → Screen capture.
Full-screen exclusive mode games/apps may block screen capture. Run those apps in windowed or borderless windowed mode.
On high-DPI displays, click coordinates may be offset. This is a known issue — WindOp's vision model accounts for scaling, but very high DPI (200%+) may cause inaccuracies.
Apps that draw overlays (Discord overlay, game bars, screen recorders) can interfere with screen capture. Try closing them.
Memory is stored in WindOp's data directory (Settings → Memory shows the path). Verify the MEMORY.md file exists and has content.
WindOp saves memory automatically when it learns important things, but you can explicitly ask: "Remember that we use PostgreSQL" or "Save this to memory".
If you set `WINDOP_DATA_DIR`, ensure the path exists and is writable. The default is your app data directory.