Choose by workflow · checked 2026-11-07
DSHREM vs OpenCode: choose by workflow and evidence
Choose Anomaly OpenCode for a ready coding agent and documented scripted worktree runs. Consider DSHREM for the already controlled AIOS workflow, keeping deployment acceptance separate from upstream features.
own evidence
DSHREM
- Layer
- Adapter / control layer
- Version
- Unreported
- License
- Unreported
- Connection
- Existing AIOS adapter; public connection contract unreported.
- Verified capability
- Isolated read/write/test and budget receipts are verified. A bounded native DSH → Luna → Terra task completed with both predeclared checks.
- Limitation
- Systemwide activation remains blocked. Private acceptance receipts are not a public replication or a matched performance comparison.
Checked 2026-11-07
external evidence
OpenCode (anomalyco/opencode)
- Layer
- ready coding agent / harness
- Version
- v2.2.6
- License
- MIT
- Connection
- Official release documents MCP server connections and provider/model configuration; latest release adds optional connection pooling.
- Verified capability
- CLI supports scripted runs and worktree execution; the release notes describe archived runs for scripted and CI sessions.
- Limitation
- Worktree runs cannot be combined with --continue or --session, according to the release notes.
Checked 2026-11-07
Decision and its limits
Study OpenCode’s scripted interface and defer another integration. There are no matched head-to-head quality or time measurements, and the current control plane already handles dispatch and accounting.
No matched head-to-head run establishes a quality, time or cost advantage here. Freeze model, provider, inputs, approvals and budgets before testing; count failed attempts and human review.
Terra: scoped native/code and public-source checks; human editorial moderation pending · Review by 2026-12-07