Repository navigation
v1.1.0
- New: OpenCode 2 hosts are supported, alongside OpenCode 1. The package's default export is now the dual-method object
{ id, server, setup }. OpenCode 1.x keeps callingserver(input, options)exactly as in every earlier release, and OpenCode 2.x calls the newsetup(context)entrypoint, which rebuilds the same plugin — the goal tools, the event-driven continuation engine, persistence and leases, and the sidebar status — on the v2 host API and returns the dispose finalizer the v2 host awaits at shutdown. Both hosts load the same bundled module through the same package exports (.and./server; both host generations resolve./server), the hosts self-select by which method they call, and an install upgraded from 1.0.1 needs no config change and keeps its goals, persisted state and wire identifiers. The v1 hook surface, the 14 tools, the/goalcommand semantics on v1 hosts, the persisted-state format, and themetadata.goalpayload (v: 3) are all unchanged.engines.opencodewidens from>=1.17.15 <2to>=1.17.15 <3: OpenCode 1.x enforces the field at load time, while OpenCode 2 ignores it (verified live), so the widened bound gates 1.x loads and documents the supported span rather than restricting 2.x.- What OpenCode 2 does not provide, and how the plugin fails soft. v2 has no equivalent for a handful of host surfaces, and every affected call site is individually guarded, so each gap degrades that one surface and nothing else — none of them fails the plugin or interrupts a running goal. No
command.execute.beforeequivalent: v2 has no pre-execution command interception and no noReply-style suppression of the command turn's assistant echo. A typed/goal …still reaches the plugin as prompt text — the v2 adapter re-runs the v1 command handler for its state side effects (set, pause, resume, stop, clear, ledger, persistence) inside the prompt hook, on by default and disableable with the v2-sidev2CommandTextBridgeplugin option — but the deterministic framed reply cannot be injected into the turn, so thegoal_*agent tools remain the surface whose result reaches the model verbatim, with an exact tool equivalent for every state change/goalperforms. No TUI toast orapp.logroutes: the lifecycle and audit advisories that route throughclient.tui.showToastandclient.app.logfail soft (the dispatch is advisory and swallows the failure), and notices still reach the user through the session title and tool results. Nosession.todo,session.children,session.statusorconfig.providersroutes: the<existing_todos>offer is skipped,noContinueWhileChildrenActivefails open (continuation proceeds when the host cannot report children), and the auto-detected context-window ceiling stays off unlesscontextWindowTokensis configured explicitly. The full caveat list, and what "supported" is verified against, is indocs/compatibility.md, rewritten this release from "not supported, and not yet tested" to supported-with-caveats. - The published type declarations carry the new entrypoint.
index.d.ts's default export gains the optionalsetup?: (context: unknown) => Promise<() => Promise<void>>besideserver, with the v2 context kept loose (unknown) like the hook payloads;GoalPluginHooks,GoalPluginOptions, and both payload-schema version strings (GoalSidebarStatus.v,GOAL_PANEL_PAYLOAD_VERSION) are unchanged.npm run type:check's consumer fixture andnpm run smoke:packed-hostnow require all three export keys —id,serverand a callablesetup— so a build that drops the v2 entrypoint fails the gate instead of a v2 host. - Docs follow the widened claim.
README.mdand thedocs/reference.mdcompatibility table now state>=1.17.15 <3with the 1.x-and-2.x span;docs/providers.mdmarks its matrix as 1.x evidence records and points 2.x rows at the compatibility policy; the install specs throughoutdocs/reference.mdandexamples/pinv1.1.0. The five-step "what a supported v2 claim would require" checklist indocs/compatibility.mdis retired — its conditions are the release's own bar now.
- What OpenCode 2 does not provide, and how the plugin fails soft. v2 has no equivalent for a handful of host surfaces, and every affected call site is individually guarded, so each gap degrades that one surface and nothing else — none of them fails the plugin or interrupts a running goal. No
Install: opencode-goal-pro-max-complete-plugin@github:sblattj/opencode-goal-pro-max-complete-plugin#v1.1.0 (see docs/reference.md).