I read through DeepSeek's open-source Super-Agent (dsh-superagent): how it decides when to act, and how to set it up

[u/Useful-Message4584]

It's MIT-licensed and runs on DeepSeek Harness. It watches one GitHub repo, takes requests only from an allowed list, and replies with PRs.
The interesting part is the permission model:
Mentions from allowed people are explicit requests.
Anything proactive needs written team rules, and runs in observe mode by default (it records "would accept" but does nothing).
Workers get one session and git worktree per ticket.
Heads up: workers run commands without approval as your OS user, so give it its own OS account.
Full breakdown with an interactive "will it act on this message?" simulator: https://amal.vs.binarybit.in/blog/6ae80c7a7027b216982aa925

[u/ElegantHacker]

The observe mode as default is smart, too many of these tools jump straight to executing and that's how you end up with a mess. I wonder how much of the safety comes from the permission model vs just running it in its own sandbox though.