Repository navigation
OpenCode 2.x compatibility restored — team_spawn works again
Every team_spawn on OpenCode 2.0.19+ threw ctx.permission.rules is not a function, making the plugin unusable on current hosts (issues #40, #45). v0.20.0 restores it and hardens the surrounding paths. Fixes from PR #46 by @zudsniper, plus post-merge review fixes; guard analysis from PRs #41 by @Its-Satyajit and #43 by @abcdef8751.
team_spawnno longer throws on hosts withoutpermission.rules(removed in OpenCode 2.0.19) — session.create permissions are honored there because session rules merge last on 2.0.19+- Worktree creation fixed on 2.x: the 2.0.19+ worktree API requires
projectID, which the plugin never sent, so every worktree request failed and teammates silently fell back to the shared directory - Failed branch creation is now logged, falls back to the existing branch on the re-spawn race, and never records an unverified name — a stale same-named branch could otherwise make
team_mergesquash the wrong history and silently lose the teammate's new work - Sessions bind to the worktree directory when workspace binding is unavailable, so the
edit * allowrule is genuinely scoped to the worktree instead of the whole shared tree team_tasks_addatomically rejects unknown or cross-teamdepends_onids, listing the bad ids — a typo'd id used to create a task that was permanently blocked, unclaimable, and uncompletable- The spawn result now warns plainly when worktree isolation did not complete; a TUI toast alone was invisible to leads reading tool output
- Read-only detection generalized via agent introspection (2.0.19+). Note: a customized
plan/exploreagent that reports itself as writable will receive worktrees andbash * allow
Also in this release
- v0.19.0 never reached npm — its publish failed on an expired token, so npm
lateststayed at 0.18.0 and users kept hitting the bugs above. v0.20.0 is the first npm release since 0.18.0, and carries v0.19.0's tool-arg error hints for weak models (issue #39) - solid-js devDependency bumped to 1.9.4 (#38)
- Known issue: stale teammate notifications after a team purge (issue #40 bug 4) remain unfixed, tracked in #48
Full Changelog: v0.19.0...v0.20.0