description: "The installable single-package FreeCodeGo composition for DeepSeek Harness: install channel, release tagging, and the bundled Agent Teams composition."
kind: "package-bundle"
FreeCodeGo Harness Bundle
English | 中文
Summary
Installable single-package FreeCodeGo composition for DeepSeek Harness freecodego@0.1.6-alpha.2, targeting Harness baseline 0.1.6-alpha.2. The npm artifact contains the compiled Host plugin, browser client, session-event prerequisite, native worker entrypoints, and the bundled Harness Agent Teams composition. A release publishes on npm's next dist-tag, and its plugin version intentionally matches the Harness version it targets exactly; for a reproducible install, name the version (freecodego@0.1.6-alpha.2) instead of the channel. Official Codex and Claude runtime binaries remain optional platform downloads — the package does not embed every platform's native binary.
Table of Contents
Install
Install the release for the Harness baseline you run; each release carries one tarball, named after the baseline it mounts on:
dsh plugin --profile web add --save-exact \
https://github.com/XiangSu-ce/dsh-plugin-freecodego/releases/download/freecodego-v0.1.6-alpha.2/freecodego-0.1.6-alpha.2.tgz
freecodego-0.1.6-alpha.2.tgz is the bundle for Harness 0.1.6-alpha.2: substitute the version you run, which the settings page shows beside the installed plugin version. The asset name is the naming contract in packages/freecodego/AGENTS.md.
The dsh command is provided by the Harness CLI, not this bundle. In a normal terminal install it first with npm install --global @deepseek-ai/dsh (and ensure pnpm is available). Desktop launches the same command through its private shims and passes the active DSH_HOME, so Web and Desktop use one Profile data directory when they select the same Harness home.
Maintainers release from a tag. pnpm run release:freecodego <version> bumps the bundle and creates the freecodego-v<version> tag, and the workflow is dispatched from that tag:
pnpm run release:freecodego <version>
gh workflow run release-freecodego.yml --ref freecodego-v<version>
The workflow verifies the family, builds, packs, and creates the GitHub release for that tag. It refuses to publish unless the packed file already carries the asset name an update check looks for, and it re-reads the published release the way the plugin does before the run is allowed to pass. The family publishes only from a freecodego-v* tag that names the version the workspace carries, so a dispatch from a branch fails before the build rather than after it.
Agent Teams
The bundle enables Harness Agent Teams with same-engine child sessions. A DeepSeek parent creates DeepSeek teammates, a Codex parent creates Codex teammates, and a Claude parent creates Claude teammates; the child route is inherited from the parent session rather than selected from the process default. Team roster, mailbox, task-board, and teammate Session records remain owned by Harness. The Web Chat renders the live delegated-Agent progress tree inside the parent conversation, including each task label, current tool, status, and tool-use count.
Model Experience
Indirectly, through the packages the bundle mounts; each inserted row's package owns its own model-facing behavior.
KV Cache effect
The bundle adds no request text of its own, so the cached prefix is whatever the composed rows produce.
Known Limitations and Deferred Work
- The artifact is assembled, not authored —
prepack rebuilds the Host plugin, browser client, native worker entrypoints, and the Agent Teams composition; nothing in the tarball is edited by hand.
- The version matches the Harness baseline exactly — a hotfix keeps the tag precise while the release asset keeps the baseline in its name.
- Official runtime binaries stay optional platform downloads — the package does not embed every platform's native binary.
- Install is pinned by version — a reproducible install names the baseline rather than a channel.
Dev Note
Working context for maintainers — click to expand
No invariant companion is published because the bundle is static composition metadata with no runtime registry relationship of its own.
The plugin version tracking the Harness version exactly is deliberate: a bundle assembled against one baseline composes the rows of that baseline, so an independent version number would only invite installing a pair that no build ever tested.
Runtime invariant: the bundle declares its composition as data (dsh.bundle.patch); it owns no runtime state.
