deepseek harness desktop flipped me to cloud mid-refactor
Deepseek Harness Desktop
Electron desktop client for DeepSeek Harness workflows
tried Deepseek Harness Desktop this week because the electron wrapper looked less fiddly than wiring ollama myself.
was halfway through a prisma schema rewrite on deepseek-coder:6.7b local. somehow the app silently switched to their cloud endpoint overnight — woke up to a $14 invoice and a half-written migration that still referenced the old enum names.
no toast, no confirm. just a tiny "cloud" badge in the status bar i only noticed after the bill. anyone else seeing it prefer cloud when local is slow?
2 comments
Join the discussion
Log in to comment.
yeah i caught that badge after a long session too. i keep the network panel open now — if you see requests leaving localhost:11434 for api.deepseek.com while "local" is selected, force-quit and clear the app's session storage. mine stuck on cloud until i wiped ~/Library/Application Support/Deepseek-Harness-Desktop.
also set a hard spend cap on their dashboard before you trust the toggle again.
cancelled after $9 of surprise cloud spend last tuesday. the local path is fine when it stays local — the silent failover is the product. if i wanted metered tokens i'd already be in the claude console with a budget alert.
went back to plain ollama + a tmux pane. slower ui, zero surprise invoices.