At a glance
What it does
A DeepSeek Harness bundle that adds the controlled `agent_browser` automation tool.
Web Profile
Tested with @deepseek-ai/dsh 0.1.5-rc.2; future DSH releases are not declared compatible
Evidence-verified
Checked Sep 13, 2026, 2:15 PM UTC
Code-evidenced contributions
What it adds to DSH
Provides controlled browser automation through BrowserAutomationService and the agent-browser CLI.
Mechanism evidence ↗Before you choose it
This community package adds BrowserAutomationService and `agent_browser` to a DeepSeek Harness profile. It routes commands through agent-browser to Chromium, Chrome, or CDP and is independent of the companion Orbit orchestration package.
Best for
DeepSeek Harness users who need scripted, agent-driven browser interaction as part of an engineering workflow.
Common tasks
- Open a URL, inspect an interactive snapshot, click a referenced element, and take a new snapshot.
- Add browser capability to a Harness profile without installing the Orbit orchestration package.
- Use browser automation only in declared Orbit plan steps when both packages are installed.
Permissions and data
Controls a local or CDP-connected browser session and may handle the web content visible in that session.
Permissions- Browser automation via agent-browser and Chromium, Chrome, or CDP.
- Configured-domain access is constrained by the documented `allowedDomains` control.
- The documentation describes credential redaction and protected browser-state blocking.
- Orbit is documented separately as storing durable state in `<project>/.cx/state.json`; this browser package is described as a shared capability.
- Websites opened through the automated browser.
- agent-browser CLI and a Chromium, Chrome, or CDP browser runtime.
- No credential requirement is declared for the package itself; websites being automated may require their own authentication.
Limitations
- Requires Node.js 22.19.0 or later and peer dependencies including Cordis 4.0.2 and DSH tools.
- The package was tested with DSH 0.1.5-rc.2, not every future DSH release.
- No npm distribution was found for the recorded version; use the verified Git-bundle route.
- Browser runtime behavior was not executed during this curation.
What DSHub checked
- The package manifest, Cordis bundle patch, and immutable Git distribution structure were verified.
- The manifest declares no lifecycle scripts.
- The repository documents controls including stale-reference blocking, tab-drift recovery, allowed-domain containment, credential redaction, and no CAPTCHA/OTP/2FA bypass.
What DSHub did not check
- Installation, browser execution, and the documented safeguards were not independently run for this record.
- Compatibility beyond the documented tested versions was not verified.
Pinned install
Install DSH Browser
This plugin bundle does not have a DSH Plugin install action. Use its source documentation for the delivery method.
Maintainer source
Project README
DSH Orbit + Browser Plugins
Community plugins for DeepSeek Harness (DSH). Not affiliated with or endorsed by DeepSeek.
This monorepo publishes two independent Cordis plugins:
| Package | Role |
|---|---|
@kasenri/dsh-orbit |
Deterministic engineering orchestration (orbit_controller tool + OrbitService). |
@kasenri/dsh-browser |
Controlled browser automation (agent_browser tool + BrowserAutomationService). |
Orbit is a deterministic engineering orchestration runtime for DeepSeek Harness. It coordinates planning, execution, evaluation, bounded correction, runtime recovery and durable state through a minimal Commander / Executor / Smart Watchdog architecture. Orbit 强调的是一个“有界、自我收敛的工程执行轨道”:
PLAN → EXECUTE → EVALUATE → CORRECT / RECOVER → SUCCESS
Orbit is not a timer loop, an infinite auto-continue, a pure reviewer, a pure planner, or an agent swarm. It is a deterministic supervisor plus Commander, Executor, Smart Watchdog, durable state and bounded recovery.
The two packages are decoupled: the browser plugin is a shared capability and
Orbit works without it. Only a plan step that declares the browser capability
needs the agent_browser tool to be registered.
DeepSeek Harness
│
├─ Native infrastructure: agents / subagents / tools / sessions
│
├─ @kasenri/dsh-orbit
│ ├─ OrbitService (durable state in <project>/.cx/state.json)
│ ├─ Deterministic Supervisor
│ ├─ Commander / Executor / Smart Watchdog
│ └─ Recoverable guards
│
└─ @kasenri/dsh-browser
└─ agent_browser → agent-browser CLI → Chromium / Chrome / CDP
Requirements
| Component | Tested with |
|---|---|
@deepseek-ai/dsh |
0.1.5-rc.2 |
@deepseek-ai/cordis |
4.0.2 |
agent-browser (browser plugin) |
0.33.2 |
| Node.js | >= 22.19.0 |
DSH is in developer preview; the plugins are tested with the versions above, not with every future DSH release.
Install
The stable install source is the dedicated GitHub distribution repository for
each plugin. DSH can lock the resolved Git commit and the market can compare it
with repository HEAD; this project does not use the npm Registry as a
publication source. pnpm must be on PATH.
# Orbit plugin only (Git source, tracks repository HEAD)
dsh plugin --profile web add github:KasenRi/dsh-orbit
# Browser plugin only (Git source, tracks repository HEAD)
dsh plugin --profile web add github:KasenRi/dsh-browser
# Both (Orbit browser-capability steps may then use the browser plugin)
dsh plugin --profile web add github:KasenRi/dsh-orbit
dsh plugin --profile web add github:KasenRi/dsh-browser
Each package declares a dsh.bundle manifest, so dsh plugin add installs it
and registers it as a profile layer automatically. See the package READMEs for
configuration:
The source monorepo's versioned GitHub Release tarballs remain available for
manual, offline, or fallback installation. They are not the Market's primary
source because a fixed Release asset has no Git HEAD to compare for updates.
Quick start
The most deterministic way to start Orbit is the slash command:
/agent-orbit 修复当前项目的 TypeScript 错误并运行测试
Orbit supports three activation styles:
/agent-orbit <goal>— deterministic slash-command activation (Web GUI slash menu, or a genuine user message gesture on headless/CLI surfaces).orbit模式— recommended natural-language activation.cx模式— legacy compatibility; still resolves to Orbit.
In the Web GUI an Orbit model control sits immediately left of the native model seat: Commander/Watchdog persist into DSH settings, and the Executor follows the current session model through the same shared model directory. Each new run snapshots the three effective routes; resumes keep their frozen routes.
# Orbit (typed tool, the same entry the slash command activates)
orbit_controller { "action": "run", "goal": "…", "approved_loop_count": 4 }
orbit_controller { "action": "status" }
# Browser
agent_browser { "args": ["open", "https://example.com"] }
agent_browser { "args": ["snapshot", "-i"] }
agent_browser { "args": ["click", "@e2"] }
agent_browser { "args": ["snapshot", "-i"] }
Safety
- Orbit: read-only allowlists for Commander and Watchdog, a writer allowlist for Executors, browser tools only for steps that declare the capability, single-mutation-owner fencing, bounded corrections and loop budget, and recoverable guard denials that stop one tool call instead of the run.
- Browser: page-scoped refs and stale-ref blocking, tab-drift detection with a
single deterministic recovery, artifact verification, protected browser
state blocking, credential redaction, strict
allowedDomainscontainment, and no CAPTCHA/OTP/2FA bypass.
Migrating from CX
See packages/orbit/README.md.
In short: dsh-cx → dsh-orbit, cx_controller → orbit_controller,
CX mode → Orbit mode, ctx.cx → ctx.orbit. .cx/state.json remains
unchanged, legacy cx模式 remains supported, and existing durable runs do not
need migration.
Development
npm install
npm run typecheck
npm test # unit tests
npm run test:e2e # real Cordis host end-to-end
npm run test:smoke # real Chromium / CDP / Orbit browser smokes
npm run build # emit lib/ for both packages
The test suite covers unit, runner-integration, real-Cordis-host end-to-end and
real-Chromium smoke levels. The DeepSeek Orbit smoke (npm run smoke:deepseek)
requires real model credentials and is not part of the default suite.
Distribution mirrors
This repository is the canonical source monorepo. The installable Git sources
are the generated release mirrors KasenRi/dsh-orbit
and KasenRi/dsh-browser. Do not develop
features in the mirrors. After the release tests and npm run build pass, sync
an explicit stable version with:
npm run sync:distribution -- 0.5.0 --push
The script copies only each package's package.json, cordis.patch.yml,
README.md, LICENSE, and prebuilt lib/. It updates mirror main and creates
a missing package-version tag; ordinary development commits never publish to a
mirror automatically. Versioned tarballs in this repository's GitHub Releases
remain available for manual or offline fallback.
License
MIT
Operate deliberately
Install and manage
Prerequisites and target Profile
Target: Web Profile
Delivery: Dsh Bundle Git — KasenRi/dsh-orbit-browser-plugins#66574f29661f71fa75ac3ce9ea7c45a78f671691。
Verify, update, and remove
Show lifecycle commands
dsh plugin --profile web listCompatibility and access
Tested with DSH 0.1.5 Rc.2 and Cordis 4.0.2: Tested with @deepseek-ai/dsh 0.1.5-rc.2; future DSH releases are not declared compatible。
Review compatibility evidence ↗
Risk facts
Can automate Chromium, Chrome, or CDP-connected browser sessions.
Evidence ↗Documentation claims credential redaction and blocks CAPTCHA, OTP, and 2FA bypass.
Evidence ↗Evidence and editorial reviewManifest, Bundle patch, distribution and freshness
Immutable evidence
Review status and source activity
Community software; the repository states it is not affiliated with or endorsed by DeepSeek.
AI reviewed Sep 13, 2026, 2:16 PM UTC。GitHub facts last checked Sep 13, 2026, 2:16 PM UTC。
No material source change has been recorded since this evidence baseline.