@kody-ade/kody-engine 0.2.21 → 0.2.26

package/dist/executables/fix/profile.json

@@ -60,6 +60,9 @@
       {
         "script": "parseAgentResult"
       },
+      {
+        "script": "requireFeedbackActions"
+      },
       {
         "script": "verify"
       },

package/dist/executables/fix/prompt.md

@@ -17,22 +17,29 @@ You are Kody, an autonomous engineer. Apply the feedback below to the existing P
 ```
 
 # Required steps
-1. Read the feedback carefully. It takes precedence over the original issue spec. If feedback says "remove X", remove X even if the issue asked for it.
-2. Research ONLY what's needed to address the feedback. Make the minimum edits required.
-3. Run each quality command with Bash. Fix the root cause of any failure you introduced by this round of edits.
-4. Final message format (or a single `FAILED: <reason>` line on failure):
+1. **Extract** every actionable item from the feedback. A structured review uses headings like `### Concerns`, `### Suggestions`, and `### Bugs`; each bullet under those headings is a distinct item. `### Strengths`, `### Summary`, and `### Bottom line` are NOT items — skip them. If the feedback has no headings (plain inline feedback), treat the whole feedback as one item.
+2. **Number each item** internally (Item 1, Item 2, …). You will account for every one of them in your final message below.
+3. **Research** — read only what's needed to act on the items. Make the minimum edits required to implement each one.
+4. **Verify** — run each quality command with Bash. Fix the root cause of any failure you introduced by this round of edits.
+5. Your FINAL message MUST use this exact format (or a single `FAILED: <reason>` line on failure). The `FEEDBACK_ACTIONS:` block is REQUIRED — omitting it or leaving it empty makes your DONE invalid.
 
    ```
    DONE
+   FEEDBACK_ACTIONS:
+   - Item 1: "<short restatement of the item>" — <fixed: <what you edited> | declined: <specific reason>>
+   - Item 2: "<short restatement>" — <fixed: ... | declined: ...>
+   - (one line per extracted item; do NOT omit any)
    COMMIT_MSG: <conventional-commit message for this round of fixes>
    PR_SUMMARY:
    <2-4 bullets describing what changed in THIS fix round — not the whole PR>
    ```
 
 # Rules
-- **Treat the feedback as a concrete change request, not a code review to argue with.** If feedback says "add an X branch", you must add an X branch — not document that the existing Y branch already covers the case. "Already handles it in a different way" is NOT an acceptable reason to skip an edit.
-- **Your DONE is only valid if your edits produce a diff that materially implements the requested change.** A diff that only adds tests asserting the *current* behavior, or only tweaks comments/docs, does NOT count as addressing a change request. If the feedback asks for a new code path, the diff MUST contain that new code path.
-- **"Already satisfied" is only allowed when the code already does exactly what the feedback asks for, verifiable by reading the implementation.** If in doubt, make the edit.
+- **The feedback is the scope.** You are here to address the extracted items — nothing else. Do NOT make unrelated refactors, rename variables the reviewer did not flag, or "tighten" types that were not called out. Every edit in your diff must trace back to a specific Item in `FEEDBACK_ACTIONS`.
+- **Default to `fixed`.** `declined` is only acceptable when (a) the item is factually wrong about the code, or (b) it is explicitly out of scope per the issue body. In both cases the `declined: <reason>` line must point to concrete evidence (a file:line that contradicts the item, or a specific issue-body clause).
+- **Treat each item as a concrete change request, not a code review to argue with.** "Add an X branch" means add an X branch — not document that Y already covers the case. "Already handles it in a different way" is NOT an acceptable reason to decline.
+- **Your DONE is only valid if your diff materially implements each `fixed` item.** A diff that only adds tests asserting the current behavior, or only tweaks comments/docs, does NOT count as addressing a change request. If an item asks for a new code path, the diff MUST contain that new code path.
+- **"Already satisfied" (i.e. skipping the edit because the code already does what's asked) is only allowed when you can cite the exact file:line that already implements it.** If in doubt, make the edit — under `fixed`.
 - Do NOT run git/gh commands. The wrapper handles it.
 - Stay on `{{branch}}`.
 - Do not modify files under `.kody/`, `.kody-engine/`, `.kody2/`, `node_modules/`, `dist/`, `build/`, `.env`, `*.log`.

package/dist/executables/plan/profile.json

@@ -51,6 +51,9 @@
       {
         "script": "persistArtifacts"
       },
+      {
+        "script": "postPlanComment"
+      },
       {
         "script": "writeRunSummary"
       },

package/dist/executables/types.ts

@@ -87,6 +87,8 @@ export interface ClaudeCodeSpec {
   permissionMode: "default" | "acceptEdits" | "plan" | "bypassPermissions"
   /** null = unbounded. */
   maxTurns: number | null
+  /** Extended-thinking token budget. null = SDK default. */
+  maxThinkingTokens: number | null
   /** Text appended on top of Claude Code's baseline system prompt. */
   systemPromptAppend: string | null
   /** SDK built-in tools this executable is allowed to use (capability pack). */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kody-ade/kody-engine",
-  "version": "0.2.21",
+  "version": "0.2.26",
   "description": "kody2 — autonomous development engine. Single-session Claude Code agent behind a generic executor + declarative executable profiles.",
   "license": "MIT",
   "type": "module",
@@ -12,6 +12,18 @@
     "templates",
     "kody.config.schema.json"
   ],
+  "scripts": {
+    "kody2": "tsx bin/kody2.ts",
+    "build": "tsup && node scripts/copy-assets.cjs",
+    "test": "vitest run tests/unit tests/int --no-coverage",
+    "test:e2e": "vitest run tests/e2e --no-coverage",
+    "test:all": "vitest run tests --no-coverage",
+    "typecheck": "tsc --noEmit",
+    "lint": "biome check",
+    "lint:fix": "biome check --write",
+    "format": "biome format --write",
+    "prepublishOnly": "pnpm build"
+  },
   "dependencies": {
     "@anthropic-ai/claude-agent-sdk": "0.2.92"
   },
@@ -31,16 +43,5 @@
     "url": "git+https://github.com/aharonyaircohen/kody-engine.git"
   },
   "homepage": "https://github.com/aharonyaircohen/kody-engine",
-  "bugs": "https://github.com/aharonyaircohen/kody-engine/issues",
-  "scripts": {
-    "kody2": "tsx bin/kody2.ts",
-    "build": "tsup && node scripts/copy-assets.cjs",
-    "test": "vitest run tests/unit tests/int --no-coverage",
-    "test:e2e": "vitest run tests/e2e --no-coverage",
-    "test:all": "vitest run tests --no-coverage",
-    "typecheck": "tsc --noEmit",
-    "lint": "biome check",
-    "lint:fix": "biome check --write",
-    "format": "biome format --write"
-  }
-}
+  "bugs": "https://github.com/aharonyaircohen/kody-engine/issues"
+}

package/templates/kody2.yml

@@ -1,9 +1,13 @@
 # Drop this file at .github/workflows/kody2.yml in your repo.
 #
-# Triggers: @kody2 comment on an issue or PR, or manual workflow_dispatch.
-# Everything else (install deps, set up LiteLLM, run the agent, open the PR)
-# is handled inside the @kody-ade/kody-engine package. This template should
-# rarely need editing — future kody2 capabilities ship via npm publish.
+# Two triggers, two modes:
+#   - issue_comment / workflow_dispatch with issue_number → `kody2 ci`
+#     (the @kody2 issue/PR automation flow)
+#   - workflow_dispatch with sessionId                    → `kody2 chat`
+#     (dashboard-driven Gemini chat session)
+#
+# All orchestration lives in the kody2 npm package; future capabilities ship
+# via `npm publish`, not by editing this file.
 #
 # Required repo secrets: at least one model provider key (e.g. MINIMAX_API_KEY,
 # ANTHROPIC_API_KEY). kody2 reads any *_API_KEY secret automatically via
@@ -12,10 +16,8 @@
 # Recommended: KODY_TOKEN secret — a fine-grained PAT or GitHub App token
 # with `repo` + `read:org` scopes. Without it, kody2's commits/PR-creation
 # still work via github.token, but two things degrade:
-#   1. PR body updates fail with "token lacks read:org scope" (cosmetic,
-#      surfaces as warnings in logs; the PR itself is still created/updated).
-#   2. Pushes from kody2 won't trigger downstream workflows (github.token
-#      pushes are deliberately blocked from re-triggering CI).
+#   1. PR body updates fail with "token lacks read:org scope" (cosmetic).
+#   2. Pushes from kody2 won't trigger downstream workflows.
 # Set KODY_TOKEN in repo Settings → Secrets → Actions.
 
 name: kody2
@@ -24,16 +26,30 @@ on:
   workflow_dispatch:
     inputs:
       issue_number:
-        description: "GitHub issue number"
-        required: true
+        description: "GitHub issue number (agent mode)"
+        type: string
+        default: ""
+      sessionId:
+        description: "Chat session ID (chat mode, from Kody-Dashboard)"
+        type: string
+        default: ""
+      message:
+        description: "Initial chat message (optional)"
         type: string
+        default: ""
+      model:
+        description: "Model override (optional, e.g. anthropic/claude-haiku-4-5-20251001)"
+        type: string
+        default: ""
+      dashboardUrl:
+        description: "Dashboard event ingest URL with inline ?token=... (chat mode)"
+        type: string
+        default: ""
   issue_comment:
     types: [created]
 
 jobs:
   run:
-    # Skip bot-authored comments (e.g. kody2-bot's own status posts) so we
-    # don't loop the workflow on our own output.
     if: >-
       ${{ github.event_name == 'workflow_dispatch' ||
           (github.event_name == 'issue_comment' &&
@@ -41,7 +57,10 @@ jobs:
             github.event.comment.user.login != 'kody2-bot' &&
             github.event.comment.user.type != 'Bot') }}
     runs-on: ubuntu-latest
-    timeout-minutes: 60
+    timeout-minutes: 360
+    concurrency:
+      group: kody2-${{ inputs.sessionId || inputs.issue_number || github.event.issue.number || github.sha }}
+      cancel-in-progress: false
     permissions:
       issues: write
       pull-requests: write
@@ -56,10 +75,24 @@ jobs:
         with:
           node-version: 22
 
+      - name: Write pip cache key for LiteLLM
+        run: echo "litellm[proxy]" > "$RUNNER_TEMP/kody2-pip-requirements.txt"
+
       - uses: actions/setup-python@v5
         with:
           python-version: "3.12"
+          cache: "pip"
+          cache-dependency-path: ${{ runner.temp }}/kody2-pip-requirements.txt
 
       - env:
-          ALL_SECRETS: ${{ toJSON(secrets) }}
-        run: npx -y -p @kody-ade/kody-engine@latest kody2 ci
+          ALL_SECRETS:   ${{ toJSON(secrets) }}
+          SESSION_ID:    ${{ inputs.sessionId }}
+          INIT_MESSAGE:  ${{ inputs.message }}
+          MODEL:         ${{ inputs.model }}
+          DASHBOARD_URL: ${{ inputs.dashboardUrl }}
+        run: |
+          if [ -n "$SESSION_ID" ]; then
+            npx -y -p @kody-ade/kody-engine@latest kody2 chat
+          else
+            npx -y -p @kody-ade/kody-engine@latest kody2 ci
+          fi