The desktop build seems to enable telemetry by default. Regular `dsh web` only has telemetry for explicit user feedback. Hmm :/
If like me you're mildly bothered by this, add these lines to $DSH_HOME/cordis.patch.yml before first startup ($DSH_HOME is ~/.dsh by default):
On-topic: I like DeepSeek Harness quite a bit, but the problem with "Everything Is A Plugin" is that when this includes core functionality, you still have to maintain downstream patches for those core plugins if you want to tweak existing behaviour. I currently have ~25 downstream commits and 0 new plugins.
not surprising. their approaches are generally leaning on gathering as much user data as possible, e.g. the paid API can't opt out training. I'd always double-check before using any service from them.
Yeah, I am actually ok with this. I'm selective about what goes into it, and the training goes into better open-weight models. From what I've seen the DSH desktop telemetry is actually telemetry (like VS Code), not uploading all your files.
Might have been unclear from what I posted originally, but the `session-log-deepseek` is attaching session transcripts to DeepSeek API inference requests, so it's just a full version of what already needs to go in the messages array, with compaction expanded etc.
If you run `dsh web` against a local model then nothing goes to DeepSeek by default (except the web_search tool uses their API, but there has to be a backend somewhere). I think that's commendable. The regression on the desktop app is disappointing.
wren6991 · · focus · HN ↗
If like me you're mildly bothered by this, add these lines to $DSH_HOME/cordis.patch.yml before first startup ($DSH_HOME is ~/.dsh by default):
On-topic: I like DeepSeek Harness quite a bit, but the problem with "Everything Is A Plugin" is that when this includes core functionality, you still have to maintain downstream patches for those core plugins if you want to tweak existing behaviour. I currently have ~25 downstream commits and 0 new plugins.jimmydoe · · focus · HN ↗
declan_roberts · · focus · HN ↗
wren6991 · · focus · HN ↗
Might have been unclear from what I posted originally, but the `session-log-deepseek` is attaching session transcripts to DeepSeek API inference requests, so it's just a full version of what already needs to go in the messages array, with compaction expanded etc.
If you run `dsh web` against a local model then nothing goes to DeepSeek by default (except the web_search tool uses their API, but there has to be a backend somewhere). I think that's commendable. The regression on the desktop app is disappointing.