Only Agent Manager settings messages now bump the settings generation,
so unrelated Settings-panel requests carrying a requestId can no longer
invalidate an in-flight projects or branches response. The handler also
no longer retargets the panel project directory: the settings handler is
project-scoped by projectId, and touching the panel directory expired
config bindings and blocked unsaved config saves when switching the
Agent Manager project.
Route the settings-panel message through the shared project message
handler, build the project settings handler in the project wiring, and
drop the duplicate projectId prop that the merge left in SidebarBody.
Move Agent Manager worktree settings (project, default base branch,
setup script) into the Kilo Settings editor behind a new Agent Manager
tab shown only for panels that opt in. The gear action in the Agent
Manager sidebar now opens that tab pre-scoped to the owning project.
The default base branch picker reuses the existing ProjectBranchDialog
and BranchSelect UI instead of a Settings-specific popover. Settings
requests are generation-guarded so stale responses from a previously
selected project cannot switch the visible repository state.
Drop KiloClaw from the mobile app capabilities and screenshots, the Cloud Agent
triggers comparison, and the ChatGPT and xAI cloud-feature notes. Contributor
architecture pages keep their KiloClaw entries because that code still exists.
Add a shared kiloclaw-eol partial and render it on every KiloClaw page, and
remove the KiloClaw card, hero CTA, quick links, and terminal tab from the docs
homepage plus the pointer link in the architecture Related list. The top-level
nav entry stays so existing users can still reach the docs.
* fix: avoid unnecessary project plugin dependencies
Fixes#12778
* test: move config plugin-dependency tests onto the Effect 4 API
zipRight, Effect.fork and Fiber.poll are gone in effect 4.0.0-beta.83, so
typecheck failed on this file. Uses andThen, forkChild and a bounded join.
* refactor: move plugin dependency logic into kilo-owned helper
Per review, extract the local plugin dependency install out of the upstream
config.ts and into packages/opencode/src/kilocode/config/plugin-deps.ts so the
upstream file keeps a minimal call and future merges have less to conflict on.
needsLocalPluginDependency owns the file:// specifier test and
installLocalPluginDependency owns the npm install effect, taking the npm
service, dir, version and local flag as parameters. Behavior is unchanged: the
plugins accumulator still collects both the file-loaded specs and the
ConfigPlugin.load results before the check, and the resulting fiber is still
pushed onto deps.
---------
Co-authored-by: Matt Van Horn <455140+mvanhorn@users.noreply.github.com>
marius-kilocode