Qulierm/orbital-agents

Orbital Agents is a native DeepSeek Harness plugin distributed on npm as dsh-orbital-agents and developed in the public repository Qulierm/orbital-agents, with the predecessor package dsh-endeavour now superseded and deprecated on the registry. It targets DSH Desktop v2.0.14 running the Cordis 4.0.4 runtime family on DeepSeek Harness v0.1.7-rc.1, and ships as one global bundle row that exposes only the durable orchestration service plus a scoped dsh-orbital-agents/tools row nested inside the Endeavour preset that registers the four model-facing tools. Two ordinary user presets — Endeavour (planner: endeavour_plan, endeavour_verify) and Challenger (executor: challenger_start_task, challenger_report) — are delivered as bundle patches inside the package, so no preset directory is written to ~/.dsh/.agent-presets; older ownership-marked directories are retired on upgrade. The community integration requires composition rows and Workspace-owned session navigation, so earlier Harness releases are not supported, and the project explicitly states it is not an official DeepSeek product.

In normal use an operator builds the package with pnpm install --frozen-lockfile && pnpm run build && pnpm pack, or simply runs npm pack dsh-orbital-agents@0.2.7 to fetch the published tarball, then installs it with node scripts/install-local.mjs --tarball ./dsh-orbital-agents-0.2.7.tgz; the installer backs up the desktop profile and any existing user preset, preserves the current plugin order, and is idempotent across re-runs. After quitting and reopening DSH Desktop with osascript -e 'quit app "DSH Desktop"' and open "/Applications/DSH Desktop.app", the user starts a New Chat with the Endeavour preset, picks the planning model through the composer, configures Challenger through a single icon-only unified model control that opens Model/Thinking rows for both peers, and sends the task in ordinary language — the only step that needs provider credentials. Endeavour writes the plan and verifies it, while its persistent Challenger peer — a second ordinary chat created once and reused for every later plan — executes it through a durable protocol and reports back; the paired sessions stay in the same Workspace, expose reciprocal Challenger and Endeavour view tabs, and surface exactly four task states (Waiting, Working, Finished, Confirmed, Failed) with live timers on the running row and frozen duration after verification. Only Endeavour may record terminal success or failure after a quick acceptance check, so the Challenger can never authorize success on its own.

Dependencies are limited to pnpm, Node, and DSH Desktop itself; the npm tarball is MIT-licensed and can be inspected with npm view dsh-orbital-agents version. Operational limits include latched admission once the pair is first seen, a locally unavailable/retry state when a model's directory is briefly unreachable, no promotion of an existing Challenger row by reselecting Endeavour (the runtime repairs the Challenger selection instead), and no overwrite of an existing non-owned preset unless --force is passed after the automatic backup. Lifecycle is managed through --list-backups, --rollback <timestamp>, and --uninstall, with backups stored under ~/.dsh/backups/endeavour/<timestamp>/ as profile/, preset/, and state.json; an installation also runs a read-only legacy-plan preflight that aborts before any mutation if a NONTERMINAL childId-only plan is detected, reporting the affected session ids and remediation steps before proceeding.