Uh oh!
There was an error while loading. Please reload this page.
Configure DeepSeek Harness through Requesty - #20
Merged
Conversation
Co-Authored-By: Daniel Trugman <daniel@requesty.ai>
ContributorAuthor
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
AI CostNo spend detected for branch Updated 2026-08-15T20:12Z · last 30 days · data from Requesty |
Uh oh!
There was an error while loading. Please reload this page.
Co-Authored-By: Daniel Trugman <daniel@requesty.ai>
requesty-ditti
approved these changes
Aug 15, 2026
Uh oh!
There was an error while loading. Please reload this page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds DeepSeek Harness (
dsh) as a sixth harness.DeepSeekHarnessfollows the Hermes pattern (YAML, merge and overwrite, shared backup helpers), with two differences worth knowing:Two files. The harness settings file cannot hold a key, only a credential name, so the key goes to a second file the harness reads by that name:
The credentials file is merged, never replaced, including on the overwrite path, so a user's
DEEPSEEK_API_KEYsurvives. The harness rejects that file if any group or other permission bit is set, which the existing0o600write already satisfies.Statusrequires the stored key as well as the provider, since settings alone do not authenticate.Config directory follows
DSH_HOME.DefaultConfigDirDeepSeekreturns$DSH_HOMEwhen set and~/.dshotherwise, matching where the harness itself looks. Every other harness has a fixed directory.baseURLkeeps the/v1suffix because the provider speaksopenai-completions. Unlike Pi and Hermes there is no Anthropic Messages path here: that protocol works against the router without the suffix, but the harness sends no cache hint, so it buys nothing and costs the OpenAI-format model coverage.Verified against the real harness rather than only in tests:
Configurewrote aDSH_HOME, anddsh --profile headlessthen ran a task end-to-end through the router on that exact generated config.Docs page: requestyai/docs#161.
Link to Devin session: https://app.devin.ai/sessions/41af85ae3a0e49dabf09aaa96532d04e
Requested by: @requesty-ditti