↓Pull to sync
uickBeak
Beak it. Tidy it. Track it.
New
Tap to pick, or paste / drop an image here
Move to Trash?

This bug moves to Trash (with its screenshots). You can restore it later, or empty the Trash to delete it for good.

Projects
Trash

Deleted items stay here and stay recoverable. They are purged automatically 30 days after deletion.

Filter & sort

Filter by status using the All / Open / W.I.P. / Done chips above.

🔒 Unlock keys

Enter your passphrase to unlock your saved API key and sync secret.

If you forget this passphrase, the stored keys can't be recovered — you'd just paste them again. Your bugs are never affected.

Settings
⚙ Using local Ollama? Fix the “Network/CORS blocked” error
A web page opened from a file has origin null. By default Ollama refuses calls from it, which shows as “Network/CORS blocked.” To allow it:
  1. Windows: in PowerShell run setx OLLAMA_ORIGINS "*" — then fully quit Ollama from the system tray and reopen it (a plain restart of the window isn't enough; the value only reaches newly-started processes).
  2. macOS: launchctl setenv OLLAMA_ORIGINS "*", then quit & reopen Ollama.
  3. Linux: systemctl edit ollama.service → add Environment="OLLAMA_ORIGINS=*" under [Service] → systemctl daemon-reload && systemctl restart ollama.
Most reliable (any OS): stop Ollama, then in a terminal run
OLLAMA_ORIGINS=* ollama serve
(PowerShell: $env:OLLAMA_ORIGINS="*"; ollama serve) and leave that window open — that window is the server, with origins allowed for sure. A web page can't start Ollama for you.
Still failing?
  • “Provider error (HTTP 404)” = server reached, but the model name is wrong. Run ollama list and put the exact name (incl. the :tag, e.g. qwen3.5:9b) in the Models field.
  • “…wasn't valid JSON” = the model added extra text. Try a plain instruct model like llama3.2:3b (also faster); retrying often helps.
  • Use http://localhost:11434/v1 as the Base URL, and only on the same computer Ollama runs on — a phone can't reach your PC's localhost.
Bug