@khalilgharbaoui/opencode-claude-code-plugin 0.27.1 → 0.27.2

package/dist/index.d.ts

@@ -953,67 +953,21 @@ declare class ClaudeCodeLanguageModel implements LanguageModelV3 {
     private toFinishReason;
     /**
      * Whether this call only names the session, which gets the synthetic stub
-     * rather than a `claude` spawn. opencode 1.x sends a title request with no
-     * tools, and that is the whole test there. opencode 2 sends its tool set
-     * along with it (measured on 2.0.11: `scope: "tools"`, agent `title`), so
-     * every new V2 session paid for a second `claude` process just to title
-     * itself; for a V2 model the request kind, carried as the `title` agent,
-     * decides instead.
+     * rather than a `claude` spawn. See `isTitleRequest` in title.ts.
      */
     private isTitleRequest;
     private requestScope;
     /**
      * Build the combined `--mcp-config` list and return both the list and the
-     * hash of the bridged opencode MCP block (or null when bridging is off /
-     * yields nothing). The hash is used to detect mid-session config changes
-     * and respawn the underlying claude process.
-     *
-     * `runtimeStatus` is a snapshot of opencode's `client.mcp.status()`. When
-     * provided it overlays opencode's UI-toggled state on top of disk config
-     * so `/mcps` toggles propagate without a config file write.
+     * hash of the bridged opencode MCP block. See `effectiveMcpConfig` in
+     * spawn-planning.ts.
      */
     private effectiveMcpConfig;
     /** Resolve ProxyToolDef[] for the configured proxyTools names. */
     private resolvedProxyTools;
-    /**
-     * Resolve ProxyToolDef[] for opencode's MCP-backed tools so they go
-     * through the in-process proxy instead of being bridged into Claude CLI's
-     * `--mcp-config`. Routing through the proxy keeps a single execution site
-     * (opencode), so the call is permission-prompted and rendered as an
-     * opencode tool call.
-     *
-     * Opt-in (`proxyOpencodeMcpTools: true`) and off by default. It used to
-     * default to true while finding nothing, because it discovered tools via
-     * `client.tool.list()`, which enumerates opencode's `ToolRegistry` and not
-     * the MCP tools merged into the model's tool set afterwards. Discovery now
-     * reads that merged set, the `tools` array opencode passes `doStream`, so
-     * the option does what it says. Turning it on by default at the same time
-     * would have silently moved every existing user's MCP traffic off the
-     * working direct bridge, so the default went to false instead: today's
-     * behaviour is preserved exactly and crossing over is the operator's call.
-     *
-     * Returns null when the feature is off or nothing matched, which leaves
-     * every server on the direct bridge.
-     */
+    /** Resolve ProxyToolDef[] for opencode's MCP-backed tools. */
     private resolvedProxyMcpTools;
-    /**
-     * Live tool info derived from a single `client.tool.list()` fetch:
-     *
-     * - `taskDescription`: opencode's `task` tool description exactly as the
-     *   registry renders it for native models, including the "Available
-     *   agent types" list. Overlaid onto the static `task` proxy def so
-     *   Claude sees the same subagent catalog native models see, instead
-     *   of hunting through config files.
-     * - `questionDescription` / `hasQuestion`: opencode's `question` tool
-     *   description and whether the registry has the entry at all. Older
-     *   builds lack it, in which case a `mcp__opencode_proxy__question`
-     *   call resolves to `⚙ invalid`; the version gate drops the def.
-     *
-     * Returns undefined/false when the SDK client is unavailable (direct
-     * AI-SDK use, tests) so the static defs stand. `resolved` distinguishes
-     * "the registry answered and has no `question` entry" from "nobody
-     * answered": only the former is a real version-gate signal.
-     */
+    /** One `client.tool.list()` fetch, shaped for this turn's gates. */
     private fetchLiveToolInfo;
     /**
      * Whether dcp-style context reminders should be stripped from this turn's
@@ -1024,8 +978,7 @@ declare class ClaudeCodeLanguageModel implements LanguageModelV3 {
     /**
      * Arguments the skill bridge needs beyond `cwd` / `cliPath`: which
      * `CLAUDE_CONFIG_DIR` this spawn reads its native skills from, and whether
-     * to drop the ones it already loads. A failover moves the spawn to another
-     * account, and therefore to that account's config dir.
+     * to drop the ones it already loads.
      */
     private skillBridgeSpawn;
     /** Share one lazy registry request within a turn without making it stale. */
@@ -1042,17 +995,6 @@ declare class ClaudeCodeLanguageModel implements LanguageModelV3 {
      * The process lifecycle owns the server lifecycle via session-manager.
      */
     private ensureProxyServer;
-    private extractPendingProxyResult;
-    /**
-     * The result opencode produced for a pending proxy call, if the prompt
-     * carries it. For `task_batch` that means every child's result gathered
-     * back onto the parent: opencode runs the children in one step and hands
-     * all their results to the next call together, so a partial set is not
-     * expected. If it ever happens the batch still resolves, with the gap
-     * named in the text, because leaving the parent pending would send this
-     * turn down the fresh-envelope path and reject the call as orphaned.
-     */
-    private extractPendingProxyResultForCall;
     /**
      * Resolve the session affinity token for this LLM call. Delegates to the
      * exported `resolveSessionAffinity` helper so the logic is unit-testable.