vibehacker
Discuss
Priya Nair
10 hours ago

Deepseek Harness Desktop: shipped a PR, then burned 1.4GB idle

#vibe-coding#agents#tooling
Deepseek Harness Desktop
Electron desktop client for DeepSeek Harness workflows

Tried Deepseek Harness Desktop on Win11 Tuesday night because I was tired of bouncing between browser + terminal for DeepSeek workflows.

Git commit from the app actually worked. Browser preview of localhost:3000 showed my Next diff. Then the installer ate 1.4GB of RAM sitting idle and the frosted-glass theme made the tool-call panel unreadable on my cheap Dell monitor.

Still faster than my old "copy from chat, paste into PowerShell" loop. Anyone got a sane default for the approval prompts so it stops asking twice for git status?

5

5 comments

Join the discussion

Log in to comment.

Log in
  • Pixel Quill

    the approval UX is doing too much. i watched mine ask for git status then ask again for the same shell session because the pane scrolled and lost focus.

    readable themes: force dark + opaque. frosted glass looks cool in screenshots and dies on TN panels.

    • Jules Park

      repro on my side (mac, deepseek harness 0.4.x):

      1. open approval pane
      2. approve git status
      3. scroll the tool log so the pane loses focus
      4. same shell session asks again for git status

      if focus loss re-queues the grant, that's a state bug not "extra safety". i filed similar on another electron agent last month — they fixed it by keying grants on (session_id, tool, cwd) instead of the visible pane.

  • Lena Park

    I set "auto-approve read-only" in the MCP/plugin prefs and left write+git on manual. Cut the double prompts a lot.

    Did you wire a real model key through their providers panel or are you still proxying? Mine hung for ~40s the first time DeepSeek rate-limited and the usage heatmap just showed a blank strip.

  • Mason

    1.4GB idle is not a bug, it's the electron tax. i killed the renderer once and RSS dropped to ~380MB, then the tray icon respawned a second process and climbed back.

    on the double git status thing: mine was asking once for shell, once for "workspace read" even though status is read-only. i ended up whitelisting git status/git diff/git log and leaving commit+push manual. less friction, still catches the scary ones.

    win11 or are you also on a cheap panel? the frosted glass on my old dell looks like wet fog.

  • Jade

    Curious what your approval policy looks like now after the whitelist.

    I tried "auto-approve read-only" like Lena and it still double-prompted me when the agent wrapped git status inside a bash -lc call. Does Harness treat shell wrappers as write-capable by default?

    Also — did the 1.4GB climb happen with one workspace open or did you leave a preview tab + chat history overnight?

More like this

View all