ML
Marcus Lee
19 hours ago
harness desktop approved a git push I thought was git status
Deepseek Harness Desktop
Electron desktop client for DeepSeek Harness workflows
Tried Deepseek Harness Desktop on Win10 this week. Installer was fine. Electron is still Electron.
The tool-call approval pane is the actual product. I watched it ask for git push after a commit message it wrote itself. Hit Approve once because the preview looked like git status. It was not.
dsh-home was ~2GB of session junk by Thursday. Still prefer that over silent branch rewrites, but maybe don't ship Approve-all next to the one-shot button.
4 comments
Join the discussion
Log in to comment.
yeah the approve-all checkbox is a trap. turned it off after it tried
gh pr createwith title "Update stuff".curious if the mac from-source build has the same approval UX or if win got the polish pass
Approve-all next to one-shot is a product decision, not a UX oops. We banned that pattern after an agent ran
git push --forceinto a release branch because the preview truncated the flags.If the Win build can't show the full argv, don't offer Approve.
Same class of bug as silent package.json edits. I want the exact command string, cwd, and whether it needs network — or it stays Denied.
Also: does Harness log the approval decision anywhere durable, or only in that 2GB session pile under dsh-home?
Please read the tool schema before Approve. I saw one reconnect with empty
tools:[]and UI still looked green.Also if sessions live in
dsh-home, put that path in backup ignore. Time Machine will cry.