Repository navigation
Documentation only: no module changed, so convert and deploy behave exactly as
in 0.2.1. Two questions the README left a reader to work out are now answered, and
one of its claims was out of date.
Why not just hermit convert?
A new section, measured on 2026-11-08 against hermit-harness 0.2.0 (still the
latest on PyPI) and upstream main at e79cbff:
$ hermit convert --adapter <adapter> --target opencode --output out/
hermit convert: error: argument --target: invalid choice: 'opencode'
(choose from claude-code, codex, pi, hermes)
Those four are EMITTERS in hermit/plugins/__init__.py, a hardcoded map with
TARGETS = tuple(EMITTERS) and no entry point, so a fifth host cannot be added
from outside hermit. The section also states what the standalone route costs: the
hermit-harness 0.2.0 floor, opencode 1.1.2 as the version the output was
load-checked on, and that deploy wants a workspace you already have.
The README said #42 was open. It is closed.
Relation to hermit's own OpenCode work described pull request #42 as "open and
conflicting when this was written". Read 2026-11-08, it is CLOSED and unmerged,
so the route inside hermit's core does not exist and this package is what remains
of it rather than a parallel option. The warning about both writing one workspace
is kept, because it is still the thing to avoid if a core route returns.
Install
pip install https://github.com/argszero/hermit-opencode/releases/download/0.2.2/hermit_opencode-0.2.2-py3-none-any.whl
Still needs hermit-harness 0.2.0 or later from PyPI to serve the embedded adapter.
Assets
hermit_opencode-0.2.2-py3-none-any.whl
sha256 4df2583a7d1000e5c27a96481e8b42d317efcb5f5b922a8671dd9102ae3f7090
hermit_opencode-0.2.2.tar.gz
sha256 5cd77c82d8d8eeb4c615e98125ea9ffd291616131f0cfcac99c7794e6d61c81d
26 tests pass with PYTHONPATH cleared; the deploy-then-opencode agent list
chain was re-run on 0.2.2 with the same result as 0.2.1.