Not tagged yet; this is the v2.9.0 changeset landing on main.
Added
- agent-browser + a Playwright-managed headless Chromium in the base (~625 MB
after deleting the redundant chromium_headless_shell build), so an agent can
drive a real browser and VERIFY front-end work instead of assuming it renders.
Ported from pi-devbox. AGENT_BROWSER_EXECUTABLE_PATH points at the stable
symlink /usr/local/bin/agent-chrome, which the Dockerfile resolves with `find`
rather than hardcoding: Playwright's browser dir is per-version AND per-arch
(chrome-linux on arm64, chrome-linux64 on amd64), and the headless shell binary
is named chrome-headless-shell so `-name chrome` skips it.
- opencode-devbox-version: a reader for the build manifest. The image has baked
ground truth to /etc/opencode-devbox/build-manifest.json for several releases,
but nothing read it and nothing printed it — so "which image am I running?"
meant knowing the path by heart. Three modes (--json/--quiet/human), plus a
live-vs-baked drift check, because NPM_CONFIG_PREFIX points at the persistent
config volume and a user `npm install -g opencode` can shadow the baked binary.
entrypoint-user.sh prints it as its first output.
- ENV COLORTERM=truecolor, completing a true-colour story the image already
half-shipped (terminfo entries + Neovim termguicolors, but no capability
advertisement, so bat/delta fell back to 256 colours).
- Smoke assertions for agent-browser, that agent-chrome resolves to an
executable (catches a Playwright layout change, not just a dangling symlink),
COLORTERM, the manifest's release_tag, and all three version-command modes.
Changed
- opencode 1.17.20 -> 1.18.13. Verified by diffing upstream source, not release
notes: core config.ts, config/provider.ts and schema.json are byte-identical,
so generate-config.py needs no change. 1.18.13 (published mid-audit) was
re-verified separately — 249 files in the compare payload, under GitHub's
300-file cap, so the list is complete rather than truncated; content is the
Electron app plus localisation; the five contract-surface files hash identical
at both tags. The bg-subagents removal trigger has NOT fired: runtime-flags.ts
still gates the flag behind OPENCODE_EXPERIMENTAL at all three tags.
- yq: dropped Debian's apt package (the unrelated Python kislyuk/yq — jq syntax,
3.x line) for mikefarah's Go yq v4 from GitHub. The cloud-init repo's
provision.sh/deploy.sh need v4 syntax, and THIRD_PARTY.md already credited
"yq (mikefarah)" while the image shipped the Python one, so this also closes a
documented-vs-shipped mismatch. Smoke pins the contract to mikefarah v4.
BEHAVIOUR CHANGE for any in-image script calling yq with jq-style syntax.
- mempalace pin 3.5.0 -> 3.6.0, in lockstep with pi-devbox (5724302). Reviewed
for MCP tool-schema changes before bumping — none, and nothing touches
diary_write.
- Default models -> claude-opus-5 (anthropic, and bedrock's
global.anthropic.claude-opus-5) and openai/gpt-5.6. gpt-5.4 had gone stale:
gpt-5.6 shipped four days before the v2.8.0 cut. Affects only new containers
with no OPENCODE_MODEL and no existing config.
- Smoke size thresholds +650 MB (base 2950->3600, omos 3650->4300), sized to
keep the same ~250 MB headroom so the guardrail still catches runaway growth
rather than routine apt drift. Do NOT copy pi-devbox's number: it sums
`docker history`, this repo uses `docker image inspect .Size`.
Documentation
- New README section "Choosing a provider and model", making explicit that the
baked defaults are only defaults and nobody is locked to Anthropic/Bedrock,
including the three real gotchas: defaults seed only a NEW config, an existing
opencode.jsonc on the persistent volume is never rewritten, and switching
model needs no rebuild.
- New README section "Browser automation (agent-browser)"; opencode-devbox-version
documented under Build provenance; COLORTERM under Terminal compatibility.
- README Build Args table drift fixed — FOUR missing args added
(AGENT_BROWSER_VERSION, PLAYWRIGHT_VERSION, YQ_VERSION and GITLEAKS_VERSION,
the last of which had existed as an ARG but was never listed), plus rows for
the two pinned args absent entirely (MEMPALACE_VERSION, DEBIAN_VERSION), plus
a refreshed stale OPENCODE_VERSION example. Third consecutive release to find
drift in this table.
- AGENTS.md: the stale MemPalace anyOf convention rewritten. It described a perl
RUN block already DELETED at the 3.5.0 bump and asserted "PyPI latest is 3.4.0
(== our pin), no release contains the fix yet, the workaround must stay" — all
three false. Replaced with a pin-review rule. Two new conventions added: the
agent-browser/Chromium size coupling, and the yq identity trap.
- THIRD_PARTY.md: agent-browser, Playwright, Chromium.
Verified locally with the CI-pinned hadolint 2.14.0 and actionlint 1.7.7, the
shell guard, DOCKER_HUB.md sync, bash -n, py_compile, and by generating the
config for all three providers.
pi
37960186c6