opencode-anthropic-fix 2.1.0 → 2.2.0

package/NOTICE

@@ -0,0 +1,53 @@
+opencode-anthropic-fix
+Copyright (C) 2025-2026 Marco Jardim and contributors.
+
+This program is free software: you can redistribute it and/or modify it under
+the terms of the GNU General Public License as published by the Free Software
+Foundation, either version 3 of the License, or (at your option) any later
+version. The full text is in LICENSE.
+
+This project is a fork of the original OpenCode Anthropic auth plugin by
+AnomalyCo (https://github.com/anomalyco/opencode-anthropic-auth) and contains
+modifications by the maintainers of this repository. GPL notices in this file,
+in LICENSE, and in source headers must never be removed, including during a
+dependency rollback.
+
+Third-party dependencies
+========================
+
+@tormentalabs/claude-code-wire-compat
+  Runtime-neutral Claude Code Messages wire compatibility primitives.
+  License: GPL-3.0-or-later
+  Copyright (C) claude-code-wire-compat contributors.
+  Upstream: https://github.com/marco-jardim/claude-code-wire-compat
+  Distributed with its own LICENSE and NOTICE inside the published artifact.
+
+  This package builds the outgoing Anthropic Messages request. Its npm `latest`
+  specifier is resolved to an exact version and integrity hash by package-lock.json;
+  the protocol profile is explicitly pinned in lib/mimicry/wire-compat.mjs.
+  Provenance and rollback instructions are in docs/shared-package-provenance.md.
+
+@ai-sdk/anthropic (3.0.111)
+@ai-sdk/provider
+@ai-sdk/provider-utils
+  AI SDK Anthropic provider and supporting interfaces/utilities.
+  License: Apache-2.0
+  Upstream: https://github.com/vercel/ai
+  Copyright 2023 Vercel, Inc. (from the provider packages' notices).
+  The complete Apache-2.0 text is supplied in licenses/Apache-2.0.txt.
+  Transitive versions are recorded in package-lock.json. The provider-utils
+  package also contains an ISC-licensed zod3-to-json-schema implementation;
+  its vendored copyright notice and license are included in standalone builds.
+  The Anthropic provider is used by the OpenCode v2 compatibility adapter.
+
+The npm source package publishes its runtime entrypoints, lib/**/*.mjs, user
+documentation, licenses/, LICENSE and this NOTICE. Its dependencies retain their own
+license files in node_modules; development-only dependencies are not included
+by the package's files allowlist.
+
+Standalone builds inline runtime dependencies. scripts/build.mjs collects
+the dependency packages actually present in esbuild's input metadata and
+includes their available LICENSE/NOTICE files and the complete Apache-2.0
+text in THIRD_PARTY_NOTICES. That
+document ships beside the dual-host bundle and is also embedded as comments
+in each standalone JavaScript file so legacy single-file copies retain it.

package/README.md

@@ -2,6 +2,17 @@
 
 Use your Claude Pro or Max subscription with [OpenCode](https://github.com/anomalyco/opencode). Supports multiple accounts with automatic rotation when you hit rate limits.
 
+## Supported Hosts
+
+The plugin supports **both OpenCode v1 (1.x) and OpenCode v2 (2.x)** through separate host entries sharing the same OAuth, account rotation, and request runtime.
+
+| Host              | Supported entry and validated versions                                                                                                   |
+| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
+| OpenCode v1 (1.x) | Legacy `index.mjs` factory and the recent-v1 `server()` entry. Host loading and registration tested on **1.2.27, 1.18.29, and 1.18.34**. |
+| OpenCode v2 (2.x) | `setup()` server adapter and `./tui` entry. The compatibility target starts at **2.0.21**, with **2.0.21 and 2.0.22** tested.            |
+
+These are validated versions, not a claim that every intervening or newer host release has been tested. The v2 smoke tests use a local Anthropic simulator; real OAuth login, real Anthropic inference, and interactive TUI rendering still require manual validation. See the [v2 compatibility guide](docs/opencode-v2.md) for the exact scope and limitations.
+
 ## Background
 
 [AnomalyCo](https://github.com/anomalyco/opencode-anthropic-auth) originally published this as a built-in plugin shipped with OpenCode itself. The repo was archived following a legal request from Anthropic. Before it was archived, [rmk40](https://github.com/rmk40/opencode-anthropic-auth) — a frequent contributor unrelated to AnomalyCo — had developed multi-account support that never made it upstream.
@@ -32,6 +43,9 @@ If a document or comment claims this plugin branches on the provider, that claim
 
 **Prerequisites:** [OpenCode](https://github.com/anomalyco/opencode) installed, a Claude Pro or Max subscription, Node.js 18+.
 
+The commands below install the **OpenCode v1** entry. For **OpenCode v2**, use the
+[v2 package installation](#opencode-v2-package-installation) below instead.
+
 ```bash
 # 1. Clone and install
 git clone https://github.com/marco-jardim/opencode-anthropic-fix.git
@@ -88,7 +102,15 @@ The [original plugin](https://github.com/anomalyco/opencode-anthropic-auth) prov
 
 ### From npm (recommended)
 
-Add to your `opencode.json`:
+For OpenCode v1, add to your `opencode.json`:
+
+```json
+{
+  "plugin": ["opencode-anthropic-fix@latest"]
+}
+```
+
+For OpenCode v2 (tested on 2.0.21 and 2.0.22), use the `plugins` key:
 
 ```json
 {
@@ -98,7 +120,53 @@ Add to your `opencode.json`:
 
 OpenCode will install and load the plugin automatically on next start.
 
-### Development (symlink)
+The `./server` and `./tui` exports let modern hosts select their entrypoints;
+older v1 loaders retain `index.mjs`. OpenCode v2 loads the package's `./tui` entry
+alongside its server entry; do not install `tui.mjs` as a legacy standalone plugin.
+The v2 `/anthropic` command calls the server through RPC and shows results in
+a dialog and does not add administrative output or OAuth codes to model history.
+See [the v2 guide](docs/opencode-v2.md) for the explicit package installer,
+programmatic RPC interface, cancellation behavior and current validation limits.
+
+The explicit package installer (`node scripts/install.mjs link --host=v2`,
+`copy --host=v2`, or `uninstall --host=v2`) only replaces or removes CLI entries
+it owns: links into its installed package or wrappers with its installer marker.
+It refuses unrelated CLI files and symlinks before changing the package. Add
+`--force` to deliberately replace/remove a foreign CLI entry, for example:
+
+```bash
+node scripts/install.mjs copy --host=v2 --force
+```
+
+`--force` never deletes CLI directories or unmanaged package directories and is
+only supported with `--host=v2`.
+
+### OpenCode v2 Package Installation
+
+From a checkout with dependencies installed, choose a development link or a standalone copy:
+
+```bash
+# Development: link the dual-host package (directory junction on Windows)
+node scripts/install.mjs link --host=v2
+
+# Or: build and copy the standalone package, including server and TUI entries
+npm run build
+node scripts/install.mjs copy --host=v2
+```
+
+Both modes install under `$XDG_CONFIG_HOME/opencode/node_modules/opencode-anthropic-fix`,
+falling back to `~/.config/opencode/node_modules/opencode-anthropic-fix`, rather than
+the legacy `plugin/` discovery directory. The copy needs no dependencies installed
+at its destination. The installer prints the exact `plugins` configuration to add
+to `opencode.json` and does not change your configuration. Remove old standalone
+plugin entries it reports before enabling the package to avoid duplicate loading.
+Restart OpenCode after installing or changing the plugin.
+
+To uninstall the managed v2 package, run `node scripts/install.mjs uninstall --host=v2`
+and remove its `plugins` configuration entry. See [the v2 guide](docs/opencode-v2.md)
+for RPC commands, transport details, and validation limits.
+
+### OpenCode v1 Development (symlink)
 
 Best for active development. Edits to source files take effect immediately.
 
@@ -111,7 +179,7 @@ This creates:
 - **Plugin:** `~/.config/opencode/plugin/opencode-anthropic-auth-plugin.js` → `./index.mjs`
 - **CLI:** `~/.local/bin/opencode-anthropic-auth` → `./cli.mjs`
 
-### Stable (copy)
+### OpenCode v1 Stable (copy)
 
 Bundles the plugin and CLI into self-contained single files (via esbuild) and copies them. No symlinks, no `node_modules` needed at the destination.
 
@@ -124,7 +192,7 @@ This creates:
 - **Plugin:** `~/.config/opencode/plugin/opencode-anthropic-auth-plugin.js` (standalone, ~50KB)
 - **CLI:** `~/.local/bin/opencode-anthropic-auth` (standalone, ~35KB)
 
-### Uninstall
+### OpenCode v1 Uninstall
 
 ```bash
 npm run uninstall

package/docs/opencode-v2-architecture.md

@@ -0,0 +1,148 @@
+# Decision: dual host adapters with one OAuth executor
+
+## Context and decision
+
+OpenCode 2.0.21 uses a definition object, registration APIs, a separate TUI
+plugin, and different provider/message schemas. The existing v1 factory cannot
+be loaded unchanged by that host. Preserve `index.mjs` as the legacy factory;
+expose `server.mjs` with v1 `server` and v2 `setup`, and a separate `tui.mjs`.
+
+Move the existing implementation into `createAnthropicRuntime()` rather than
+maintaining two OAuth pools or wire implementations. Mutable metrics, config,
+retry state, refresh flights and telemetry belong to each runtime. Disposal
+aborts requests, refresh waits and backoff, and flushes pending account writes.
+Disk account format and the cross-process refresh lock remain shared.
+
+## Transport options
+
+The native HTTP hooks do not expose a continuation that can own the existing
+multi-account retry loop. Directly assigning a custom fetch to provider or model
+settings was also rejected by the real 2.0.21 host: its overlay decoder requires
+JSON values and fails on `settings.fetch`. A mocked hook test cannot detect this
+constraint, which is why the binary smoke is part of validation.
+
+Use the package spec `aisdk:@ai-sdk/anthropic@3.0.111` with a process-local HTTP
+bridge. The versioned spec prevents the host from rewriting the unversioned
+Anthropic SDK to its native provider, while remaining resolvable by the host's
+built-in dynamic package loader. The
+public `http.request` hook associates a request with its session and redirects
+it to the bridge. A single-use random ticket identifies the original request;
+the bridge invokes the existing executor and streams its response to the host.
+No function is stored in provider/model settings. The SDK hook retains the
+host's middleware fetch, and the executor remains the only retry owner for
+managed OAuth requests. Other providers and explicitly selected foreign
+connections retain their own settings.
+
+The pin also makes Core's option/metadata key `anthropic@3.0.111`, whereas the
+SDK reads and emits `anthropic`. A language-model boundary remaps incoming
+provider options (including replay parts) and outgoing stream/non-stream metadata
+(including reasoning signatures and finish metadata). An unversioned specifier
+is not safe: `aisdk-native.ts:resolve` rewrites even the explicit `aisdk:` route
+to the native provider. The host's dynamic SDK hook may install the pinned
+package first; our later hook replaces that SDK with the plugin's pinned copy.
+
+The bridge binds only to IPv4 loopback on an ephemeral port. It accepts only
+issued request tickets, never accepts a caller-supplied destination, and strips
+its private correlation data before the executor. Plugin unload closes it.
+The public session-interruption event cancels pending requests because the
+2.0.21 AI SDK call does not itself receive the host's abort signal. Losing that
+event subscription aborts active requests and rejects new requests.
+
+This is immediate cancellation for primary execution events, not a guarantee
+for auxiliary fiber interruption. 2.0.22 and inspected HEAD `f74512b` still omit
+the interruption signal from `doStream`. Supplied SDK signals and loopback
+disconnects propagate upstream. Otherwise `generate` and `title` tickets have a
+10-minute total deadline, including pre-header waits and streaming, to bound
+orphaned requests. Slow primary/compaction streams are exempt. Upstream must pass
+the Effect interruption signal to `doStream` as `abortSignal` for immediate
+auxiliary cancellation; no plugin hook currently exposes that fiber lifetime.
+
+Managed provider settings disable `timeout`, `headerTimeout` and `chunkTimeout`.
+2.0.22 already has HEAD's 300-second default header/chunk limits. These conflict
+with an executor that bounds attempts but not total wall time (uncapped
+Retry-After waits and repeated transient 429s). The auxiliary deadline remains
+independent of those host defaults. 2.0.21 ignores the new header option and
+uses `chunkTimeout: 0`, because its public schema rejects `false` for that field
+(its fetch wrapper activates the timer only for positive numbers).
+
+## Credentials, commands and history
+
+The plugin registers its own OAuth method ID. Host credential values are copies;
+the pool on disk is authoritative for rotation, removal and refresh. A foreign
+OAuth method or an explicit API-key/environment connection must not be replaced.
+Only managed models receive zero costs across every tier and configured limits.
+
+Administrative commands use a typed RPC definition and a local TUI slash layer.
+They return bounded, sanitized dialog content; no prompt endpoint carries the
+arguments or output. The server command name is reserved and returns guidance
+for clients that have no administrative result channel.
+
+V2 message policies operate on a temporary view and replace only pruned results.
+Tool aliases are request-local and reversible. Summary compaction is selected
+explicitly. Normal host history loading skips incompatible native checkpoints
+and re-expands the original transcript; a new session is not required, and no
+history is corrupted, although context can grow substantially. The defensive
+adapter guard rejects opaque checkpoint parts only if explicitly passed to it.
+The optional Haiku rolling-summary hook remains a v1
+fork capability and emits a diagnostic when configured on v2.
+
+## Consequences and validation boundary
+
+One extra pinned production dependency is required for a known parser/provider
+contract. The standalone dual-package build bundles it; the host's dynamic
+provider loader may also populate its own cache on first use. The loopback bridge adds
+one local streaming hop; disposal, backpressure, request authentication,
+interruption and non-replay after streamed bytes must be covered by tests.
+
+Keep regression tests for the v1 exports and wire fixtures, deterministic v2
+SDK/transport tests, isolated installer and bundle tests, and real host smoke
+scripts. Smoke runs use temporary configuration roots and fake credentials.
+They prove host integration; they do not prove an authenticated Anthropic session
+or future host releases. See [support and usage](opencode-v2.md) for the recorded
+validation matrix.
+
+## Host-contract review sources
+
+Inspected `v2.0.21`, `v2.0.22` and upstream `f74512b` without changing the host:
+
+- **Options and SDK loading:** `packages/core/src/provider.ts:30-34` strips
+  only `aisdk:`. In `v2.0.21`, `aisdk.ts:429-442` derives the option key,
+  `:362-367` assigns the same metadata key and `:690-700` nests request options.
+  `session/runner/publish-llm-event.ts:120,421-436` persists reasoning state only
+  under that key. `aisdk-native.ts:57,135-143` maps the unversioned Anthropic SDK
+  to the native provider, including explicit `aisdk:` specs. This behavior is
+  unchanged in the inspected 2.0.22/HEAD sources. `aisdk.ts:280-288,324-347` runs
+  SDK hooks in registration order and caches their final SDK; the dynamic hook
+  (`plugin/provider/dynamic.ts:10-15`) installs only when `evt.sdk` is empty.
+  Installation is inside that hook, not an independent prerequisite:
+  `plugin/provider/sdk-factory.ts:5-16` calls `npm.add(packageName)` and resolves
+  `installed.name` in its installed directory. With the built-in hook first it
+  can install before our replacement, so retaining the resolvable pin matters.
+  `plugin/internal.ts:213-226` puts provider plugins in the pre-list;
+  `plugin/supervisor.ts:138-155` places that list before external plugins.
+- **Cancellation:** `session.ts@v2.0.21:405-411` invokes auxiliary generation
+  directly, not a primary execution. `aisdk.ts@v2.0.21:715-718`,
+  `@v2.0.22:733-736` and `@f74512b:729-732` call `language.doStream(options)`
+  without the `Effect.tryPromise` signal. Auxiliary generation also uses this
+  streaming route, not a separate `doGenerate` cancellation path.
+- **Timeouts:** `provider.ts@v2.0.22:149-164` (HEAD `:151-166`) supplies the
+  300,000 ms defaults; `aisdk.ts@v2.0.22:130-170` applies them around the
+  middleware fetch. `model-resolver.ts:373` merges provider settings after
+  removing model/variant transport settings. `packages/schema/src/provider.ts@v2.0.21:49-50`
+  permits `timeout: false` but only numeric `chunkTimeout`; `aisdk.ts:137-149`
+  treats zero as disabled. The executor's real budgets are in
+  `lib/host/runtime.mjs:2873,2912-2928,4278-4312,4393-4448`, not a total five-minute
+  deadline; `lib/backoff.mjs:11` caps account cooldowns, not whole requests.
+- **History:** `session/history.ts@v2.0.21:23-26,99-107` filters incompatible
+  checkpoints and retains the original transcript for re-expansion.
+
+The 2.0.21 → 2.0.22 diff contains no change to the consumed loader, OAuth
+methods, SDK-hook, RPC or TUI-command interfaces. The plugin Promise/Effect
+session APIs add `remove` and `compact`; the Core host adds parent-aware session
+creation and metadata updates. Model capability overlays now merge instead of
+replacing fields. None requires an adapter change here. The transport timeout
+defaults and the expanded timeout schema are the relevant breaking behavior;
+the new bounded host timeout retry policy does not supersede our managed retry
+hook. Core also preserves HTTP options when rebuilding a session request and
+adds content-filter explanations to published errors; neither changes our hook
+shapes. Provider-specific Azure/DigitalOcean changes do not affect this route.

package/docs/opencode-v2.md

@@ -0,0 +1,198 @@
+# OpenCode v2 adapter
+
+## Validation recorded on 2026-09-30
+
+Local validation used Windows and Node 24.21.0, plus each official OpenCode
+release's own runtime. Host binaries were downloaded from npm with SHA512
+integrity verification. All smoke configurations and credentials were temporary.
+
+| Host    | Result | Scope                                                                                                                                                                                    |
+| ------- | ------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 1.2.27  | Passed | Legacy loader, OAuth registration, command registration, 23 OAuth models with zero costs.                                                                                                |
+| 1.18.29 | Passed | Dual entry, OAuth registration, one administrative command, 16 OAuth models with zero costs.                                                                                             |
+| 1.18.34 | Passed | Dual entry and public provider model hook, OAuth/command registration, 19 OAuth models with zero costs.                                                                                  |
+| 2.0.21  | Passed | Server load, OAuth registration, 19 models, RPC without model invocation, chat, auxiliary generation, title, summary compaction, cancellation before response headers and plugin reload. |
+| 2.0.22  | Passed | Same local Windows smoke scope as 2.0.21, including managed timeout settings and plugin reload.                                                                                          |
+
+The original complete automated suite passed **2,286 tests across 113 files**, with two
+platform skips on Windows. Build, ESLint, formatting and invariant checks passed;
+the invariant check retains the existing warning about differing reverse-engineering
+documentation baselines. Installer and standalone package tests run in temporary
+directories. The v2 host smoke uses a local Anthropic simulator and blocks direct
+Anthropic API access. The v1 host smoke checks loading and registration, not inference.
+
+The v2 host-contract review reran both 2.0.21 and 2.0.22 Windows smokes with the
+option/metadata adapter and host timeout fixes. Auxiliary orphan bounds are
+tested with interrupted Effect fibers and loopback HTTP, not claimed as immediate
+auxiliary cancellation by those host binaries.
+
+Review verification: `npm test` and `npm run coverage` passed **2,057 tests in
+103 files**, with the same two platform skips. Coverage thresholds were unchanged;
+the new language adapter had 100% statement/branch/function/line coverage.
+ESLint, formatting, build and invariants passed (the existing baseline warning
+remains). Negative controls temporarily removed the language wrapper, auxiliary
+deadline and timeout settings and restored the inaccurate checkpoint wording:
+six regression cases failed, then passed after restoring the fixes.
+
+Run a pinned host again with `node scripts/run-host-smoke.mjs 2.0.21` or
+`node scripts/run-host-smoke.mjs 2.0.22` (or one of the v1 versions above).
+CI runs these five hosts on Linux and Windows; the
+Linux jobs have not been run locally. Real OAuth login, real Anthropic inference
+and interactive TUI rendering still require manual validation before release.
+The TUI behavior is covered by deterministic tests, and its RPC runs in the real
+v2 server smoke. See the [architecture decision](opencode-v2-architecture.md).
+
+## Installation
+
+The npm package exposes separate `./server` and `./tui` entries for recent v1
+and v2 hosts, and keeps the root `index.mjs` entry for legacy v1 loaders. Existing
+`index.mjs`, `cli.mjs` and `lib/*` imports remain available. Use the v2 `plugins`
+configuration key when loading the package in OpenCode 2.0.21.
+
+For development or a standalone bundle, run:
+
+```sh
+node scripts/install.mjs link --host=v2
+# or
+npm run build
+node scripts/install.mjs copy --host=v2
+```
+
+The explicit v2 mode installs the package in
+`$XDG_CONFIG_HOME/opencode/node_modules/opencode-anthropic-fix`, falling back to
+`~/.config/opencode/node_modules/opencode-anthropic-fix`. Development links use
+a directory junction on Windows. The copy contains bundled server, TUI, RPC,
+legacy plugin and CLI entries and requires no `npm install` at its destination.
+The copy also contains a local SDK factory; initializing a managed model does
+not resolve or download another AI SDK package into the host's cache.
+The installer prints the exact configuration to add and leaves existing
+configuration untouched. It reports old standalone plugin entries that could
+cause duplicate loading; remove those entries before enabling the new package.
+
+Use `node scripts/install.mjs uninstall --host=v2` to remove a managed package.
+The installer refuses to replace or remove an unrecognized package directory or
+one with additional files. Without `--host=v2`, installation keeps the legacy
+standalone v1 behavior.
+
+## Transport and version boundary
+
+The adapter targets the public OpenCode **2.0.21 and 2.0.22** contracts. It routes managed
+Anthropic models through `aisdk:file://…/v2-sdk.mjs`;
+the shipped factory and public SDK hook use the pinned `@ai-sdk/anthropic`
+**3.0.111** provider. The local specifier prevents the native-provider rewrite
+and avoids a redundant registry install by the host's built-in dynamic hook,
+which runs **before** external plugin hooks. This is also true in the standalone
+bundle, where `v2-sdk.mjs` is self-contained. Core now uses `anthropic` for both
+options and persisted metadata, matching the SDK. The language adapter still
+accepts the former `anthropic@3.0.111` input key for signed reasoning replay.
+See [the cold-initialization investigation](opencode-v2-sdk-initialization.md)
+for the host npm failure, mitigation, negative control and repeated smoke results.
+The shared plugin executor keeps account rotation,
+wire construction, backoff and the response compatibility shim on the same
+path as v1. Explicitly selected API-key or unrelated OAuth connections retain
+their own provider settings. A connection owned by this plugin is disabled
+when its account pool has no enabled account; it cannot fall back to a stale
+credential cached by the host.
+
+OpenCode 2.0.21 accepts only JSON data in provider/model settings, so an injected
+`settings.fetch` function is unavailable. On first use, the adapter opens an
+HTTP bridge bound to `127.0.0.1` on an ephemeral port. The public HTTP request
+hook redirects the host request to that bridge with a single-use random ticket.
+The bridge retrieves the original destination from its own ticket map, invokes
+the shared executor and streams the response back. It does not accept an
+arbitrary target URL from incoming HTTP requests. The host's normal HTTP
+middleware remains in place; no functions are stored in model settings.
+
+Neither host forwards its fiber cancellation signal to the AI SDK call (also
+verified in upstream revision `f74512b`).
+The adapter therefore associates tickets with session IDs and listens
+for the public `session.execution.interrupted` event. Interrupting a session or
+unloading the plugin aborts its requests; a lost event stream aborts outstanding
+requests and prevents new ones. A disconnected loopback request also cancels
+its upstream operation. An SDK `abortSignal`, when supplied by a caller, reaches
+the upstream through that disconnect path. **Auxiliary `session.generate` fiber
+interruption alone does not emit a primary-execution event or disconnect HTTP.**
+The bridge bounds `generate` and `title` requests to **10 minutes total**, starting
+at the HTTP hook, including retries and streaming. This is an orphan-work bound,
+not immediate cancellation; a legitimately long auxiliary call can also hit it.
+Primary and compaction streams do not have this auxiliary deadline. Immediate
+auxiliary cancellation requires upstream to pass the Effect interruption signal
+as `abortSignal` into `doStream` and preserve it through fetch/middleware.
+The correlation header is removed before the shared
+executor sends a request to Anthropic. Plugin cleanup closes the local listener.
+
+OpenCode 2.0.22 (and inspected HEAD) defaults `headerTimeout` and `chunkTimeout`
+to 300,000 ms. Managed provider settings set those and `timeout` to `false` so
+host timers cannot cut off the shared executor's retry/rotation waits. The
+executor has attempt budgets, not a finite total retry deadline: account slots
+are bounded by the pool, service errors normally get two retries, forced
+`x-should-retry` normally gets three, but Retry-After waits and repeated transient
+429s can exceed five minutes. Primary cancellation/disconnect/disposal remain
+available; auxiliary work has the separate bound above. 2.0.21 ignores the new
+header setting; its number-only chunk schema requires `chunkTimeout: 0` to
+disable that timer, while `timeout: false` is accepted on both hosts.
+
+The compatibility route uses summary compaction. When switching from a native
+provider, the host skips incompatible native checkpoints and re-expands the
+original transcript (`session/history.ts:23-26,99-107` at `v2.0.21`). A new session
+is not required and history is not corrupted, but context may grow substantially.
+The adapter's rejection guard applies only if opaque checkpoint parts are
+explicitly supplied to it; it does not describe normal host history loading.
+Validation against other OpenCode versions is required before widening the
+support claim. Host smoke tests exercise boot, RPC, streaming
+generation and cancellation using a local mock upstream. They do not constitute
+an authenticated end-to-end certification against Anthropic.
+
+## Administrative commands and the TUI
+
+On OpenCode v2, the `./tui` entry registers `/anthropic` as a local TUI command.
+The TUI calls the server through the plugin's RPC method and shows the result in
+a dialog. Failures appear as toast notifications. Output is not inserted into
+the conversation and the command does not submit a model prompt. OpenCode v1
+continues to use the existing server slash-command hook.
+
+Run the usual commands, for example `/anthropic usage`, `/anthropic switch 2`,
+or `/anthropic set debug true`. OAuth keeps the same two-step flow:
+
+1. Run `/anthropic login` or `/anthropic reauth 1` and open the authorization URL.
+2. Complete authorization in the browser.
+3. Run `/anthropic login complete <code#state>` or
+   `/anthropic reauth complete <code#state>` in the same session.
+
+When invoked from the home screen, the TUI creates an empty session before
+running the command. That session holds the pending OAuth flow; it contains no
+administrative output or authorization code. Commands entered through the
+plugin's TUI layer are intercepted before the host's server command dispatch.
+
+The RPC method is available to other OpenCode v2 clients. Use an existing
+session and the location where the plugin is loaded:
+
+```js
+import { anthropicCommandRpc } from "opencode-anthropic-fix/rpc";
+
+const commands = client.rpc(anthropicCommandRpc);
+const { output } = await commands.execute(
+  { sessionID, arguments: "usage" },
+  { location, signal: abortController.signal },
+);
+```
+
+The server also reserves the `anthropic` slash-command name. Clients that call
+the server command endpoint directly receive an error directing them to the TUI
+or RPC, because that endpoint cannot return administrative output. This avoids
+starting an OAuth flow whose URL could not be displayed and prevents command
+arguments from falling through to a model prompt.
+
+The RPC ID is `opencode-anthropic-fix`; its method is `execute`. Input is
+`{ sessionID, arguments }` and successful output is `{ output }`. The server
+verifies that the session exists before executing a command. Arguments must be
+a single CLI-style line of at most 8,192 characters. Responses are bounded to
+65,536 UTF-16 code units, with grapheme-safe truncation. The server removes
+terminal escape sequences, token-shaped credentials and submitted OAuth
+completion codes from responses and errors. Authorization URLs remain intact.
+
+The plugin declares `command_failed` and `invalid_session` RPC errors. The host
+can additionally return its standard `rpc.*` errors for unavailable services or
+invalid requests. Unloading the TUI aborts outstanding RPC calls; disposing the
+server registration propagates cancellation to its command executor and removes
+the method. Neither RPC nor TUI requires an additional runtime SDK dependency.