docs: dsh 0.1.2-rc.1 adds HTTP proxy support for outbound traffic - #18
Open
github-actions[bot] wants to merge 1 commit into
Open
docs: dsh 0.1.2-rc.1 adds HTTP proxy support for outbound traffic#18github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
docs/sync
branch
from
August 28, 2026 22:26
f804802 to
19eff56
Compare
github-actions
Bot
force-pushed
the
docs/sync
branch
from
August 30, 2026 16:46
19eff56 to
319f702
Compare
github-actions
Bot
force-pushed
the
docs/sync
branch
from
August 30, 2026 21:13
319f702 to
45dc86b
Compare
github-actions
Bot
force-pushed
the
docs/sync
branch
from
August 31, 2026 05:45
45dc86b to
d1da29c
Compare
github-actions
Bot
force-pushed
the
docs/sync
branch
from
August 31, 2026 14:01
d1da29c to
35b553e
Compare
github-actions
Bot
force-pushed
the
docs/sync
branch
from
August 31, 2026 22:55
35b553e to
79a0d8b
Compare
github-actions
Bot
force-pushed
the
docs/sync
branch
from
September 1, 2026 05:18
79a0d8b to
a27ef90
Compare
github-actions
Bot
force-pushed
the
docs/sync
branch
from
September 1, 2026 11:46
a27ef90 to
3f6b960
Compare
github-actions
Bot
force-pushed
the
docs/sync
branch
from
September 1, 2026 16:45
3f6b960 to
fd55fb9
Compare
github-actions
Bot
force-pushed
the
docs/sync
branch
from
September 1, 2026 21:07
fd55fb9 to
ee1a405
Compare
github-actions
Bot
force-pushed
the
docs/sync
branch
from
September 2, 2026 04:43
ee1a405 to
cc8e0aa
Compare
github-actions
Bot
force-pushed
the
docs/sync
branch
from
September 2, 2026 11:27
cc8e0aa to
c504889
Compare
github-actions
Bot
force-pushed
the
docs/sync
branch
from
September 2, 2026 16:40
c504889 to
d1a6bca
Compare
github-actions
Bot
force-pushed
the
docs/sync
branch
from
September 3, 2026 11:23
d1a6bca to
b6f0e9d
Compare
github-actions
Bot
force-pushed
the
docs/sync
branch
from
September 3, 2026 16:32
b6f0e9d to
07d76da
Compare
DSH now honors standard HTTP(S) proxy environment variables for its outbound traffic — model calls, web search, page fetches, and MCP servers — shipped in new npm release `0.1.2-rc.1` (the `next` tag moved from `0.1.1-rc.2`). A new user guide documents the behavior, and the module/config catalogs show a new shared `http-proxy` util package extracted to centralize it. This matters because dsh is a developer preview that makes interface changes without migration paths, and proxy support changes how every network-facing tool in dsh behaves inside a locked-down or corporate network. - New npm release `0.1.2-rc.1` (2026-09-03); `latest` stays `0.1.1-rc.2`, `next` now points at the rc. - New guide page "Run DSH behind a network proxy" (`dsh/docs/user/guide/network-proxy.md`): proxy is read from `HTTP_PROXY`/`HTTPS_PROXY`/`NO_PROXY`/`ALL_PROXY` at launch; documented limits include no SOCKS support, CIDR ranges ignored in `NO_PROXY`, TLS-intercepting proxies needing `NODE_EXTRA_CA_CERTS`, and credentials-in-URL reaching model-written child tools. A project's own `.env` cannot set proxy vars (refused at startup). - Module graph adds `http-proxy` (`packages/util/http-proxy`); `e2b`, `subprocess`, `web-fetch-http`, `session-snapshot`, and `loader-smoke` now depend on it — proxy handling was refactored into one shared package rather than per-tool code. - `config-catalog.md` lists `@deepseek-ai/dsh-http-proxy` as a new library package (imported as a library, not loadable as a `cordis.yml` plugin). - Index churn (`llms.txt`, `.metadata.json`): the new page is registered, and two old news entries (`news1226`, `news250120`) now resolve to real titles instead of being flagged "served fallback shell" — content itself unchanged, fetcher metadata corrected.
github-actions
Bot
force-pushed
the
docs/sync
branch
from
September 3, 2026 21:07
07d76da to
6db8f8b
Compare
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 free
to 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.
DSH now honors standard HTTP(S) proxy environment variables for its outbound traffic — model calls, web search, page fetches, and MCP servers — shipped in new npm release
0.1.2-rc.1(thenexttag moved from0.1.1-rc.2). A new user guide documents the behavior, and the module/config catalogs show a new sharedhttp-proxyutil package extracted to centralize it. This matters because dsh is a developer preview that makes interface changes without migration paths, and proxy support changes how every network-facing tool in dsh behaves inside a locked-down or corporate network.0.1.2-rc.1(2026-09-03);lateststays0.1.1-rc.2,nextnow points at the rc.dsh/docs/user/guide/network-proxy.md): proxy is read fromHTTP_PROXY/HTTPS_PROXY/NO_PROXY/ALL_PROXYat launch; documented limits include no SOCKS support, CIDR ranges ignored inNO_PROXY, TLS-intercepting proxies needingNODE_EXTRA_CA_CERTS, and credentials-in-URL reaching model-written child tools. A project's own.envcannot set proxy vars (refused at startup).http-proxy(packages/util/http-proxy);e2b,subprocess,web-fetch-http,session-snapshot, andloader-smokenow depend on it — proxy handling was refactored into one shared package rather than per-tool code.config-catalog.mdlists@deepseek-ai/dsh-http-proxyas a new library package (imported as a library, not loadable as acordis.ymlplugin).llms.txt,.metadata.json): the new page is registered, and two old news entries (news1226,news250120) now resolve to real titles instead of being flagged "served fallback shell" — content itself unchanged, fetcher metadata corrected.