@khalilgharbaoui/opencode-claude-code-plugin 0.60.1 → 0.61.0

package/dist/index.d.ts

@@ -473,6 +473,8 @@ interface ClaudeCodeConfig {
     bridgeSkipNativeSkills?: boolean;
     /** Append a one-line cost / duration / cache footer to each finished turn. */
     turnStats?: boolean;
+    /** Turn Claude Code's todo tools on for every model (`CLAUDE_CODE_ENABLE_TODO_TOOLS=1`). */
+    enableTodoTools?: boolean;
     /** Branch a forked opencode session off the parent's Claude conversation. */
     forkSessions?: boolean;
     /** Resume a conversation's Claude session after opencode restarts. Default true. */
@@ -992,6 +994,19 @@ interface ClaudeCodeProviderSettings {
      * `permission_denials` always reach `providerMetadata`.
      */
     turnStats?: boolean;
+    /**
+     * Start every `claude` with `CLAUDE_CODE_ENABLE_TODO_TOOLS=1`, so the CLI
+     * offers its todo tools (`TaskCreate` and family) whatever the model.
+     * Claude Code offers them on its own only to Claude 3.x, Opus 4.0 to 4.7,
+     * Sonnet 4.0 to 4.6 and Haiku 4.5; on Opus 4.8, the 5.x models and Fable
+     * no todo list reaches opencode without this (h #g259).
+     *
+     * Off by default, because the CLI turned the tools off for those models on
+     * purpose. Fills a gap only: a `CLAUDE_CODE_ENABLE_TODO_TOOLS` already in
+     * opencode's environment, `0` included, is passed through and decides.
+     * Never on a compaction spawn, which runs no tools.
+     */
+    enableTodoTools?: boolean;
     /**
      * When a new opencode session turns out to be a fork of one this provider
      * already served, branch the parent's Claude conversation with
@@ -1634,22 +1649,22 @@ declare class ClaudeCodeLanguageModel implements LanguageModelV3 {
      * switch, and outside `runModelChain` on purpose: an account switch starts
      * that account's own model chain from the top.
      *
-     * Anything but `"auto"` is `runModelChain` and one `await`, so `"off"` and
-     * `"ask"` are exactly what they were. With `"auto"`, the attempt that failed
-     * decides the switch itself (`completeResult` sets `run.switchTo` and closes
-     * its stream without a `finish`), and the next attempt's prologue makes the
-     * switch the form's pick would have made. This only splices the attempts
-     * into one caller turn: one `stream-start`, and the `finish` of whichever
-     * attempt did not switch.
+     * Anything but `"auto"` is `runModelChain` behind `stopOnCancel`. With
+     * `"auto"`, the attempt that failed decides the switch itself
+     * (`completeResult` sets `run.switchTo` and closes its stream without a
+     * `finish`), and the next attempt's prologue makes the switch the form's pick
+     * would have made. This only splices the attempts into one caller turn: one
+     * `stream-start`, and the `finish` of whichever attempt did not switch.
      *
      * The bound is `run.tried`, as it is `tried` for the model chain: every
      * account spawned or switched to goes in, and none in it is picked again.
      *
-     * Cancelling the returned stream is a stop, for every attempt: this loop is
-     * the plugin starting more work on the caller's behalf, so a caller that
-     * has gone away must reach all of it. Each attempt gets a signal that the
-     * caller's own `abortSignal` and a `cancel()` both abort, and the loop
-     * starts no further account once either has happened.
+     * Cancelling the returned stream is a stop, in every mode: a caller that has
+     * gone away must reach the turn it started, or the CLI runs it to the end
+     * and bills it. Each attempt gets a signal that the caller's own
+     * `abortSignal` and a `cancel()` both abort, so a cancel takes the turn's
+     * ordinary abort path, and with `"auto"` the loop starts no further account
+     * once either has happened. Until (h #g257) only `"auto"` did this.
      */
     private runAccountFailover;
     /**