mini-coder 0.0.12 → 0.0.13

package/docs/configs.md

@@ -65,7 +65,7 @@ Custom subagents are configured in `.agents`:
 - `./.agents/agents/*.md`
 - `~/.agents/agents/*.md`
 
-(There is no `.claude` compatibility path for agents.)
+(There is no `.claude` compatibility path for agents. Claude doesn't have custom subagents)
 
 ## Precedence and conflicts
 

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "mini-coder",
-	"version": "0.0.12",
+	"version": "0.0.13",
 	"description": "A small, fast CLI coding agent",
 	"module": "src/index.ts",
 	"type": "module",

package/hanging-bug.md

@@ -1,79 +0,0 @@
-# Hanging Bug Investigation
-
-## Symptoms
-
-After a shell tool call completes successfully, **SOMETIMES** the app hangs indefinitely instead of
-returning to the prompt. Two observed states:
-
-```
-  $ $ rm src/session/db.ts && bun run test
-⠇ shell
-```
-
-Stayed spinning with shell label for well over the timeout time. I had to kill the app.
-
-Another example with a different shell command:
-```
-  $ $ git diff
-    ✔ 0
-    │ diff --git a/src/cli/tool-render.ts b/src/cli/tool-render.ts
-    │ index f8d33af..e224932 100644
-    │ --- a/src/cli/tool-render.ts
-    │ +++ b/src/cli/tool-render.ts
-    │ @@ -148,21 +148,25 @@ export function renderToolResultInline(
-    │   }
-    │
-    │   if (toolName === "glob") {
-    │ -         const r = result as { files: string[]; truncated: boolean };
-    │ -         const n = r.files.length;
-    │ -         writeln(
-    │ -                 `${indent}${G.info} ${c.dim(n === 0 ? "no matches" : `${n} file${n === 1 ? "" : "s"}${r.truncated ? " (capped)" : ""}`)}`,
-    │ -         );
-    │ -         return;
-    │ +         const r = result as { files?: string[]; truncated?: boolean };
-    │ +         if (Array.isArray(r.files)) {
-    │ +                 const n = r.files.length;
-    │ +                 writeln(
-    │ +                         `${indent}${G.info} ${c.dim(n === 0 ? "no matches" : `${n} file${n === 1 ? "" : "s"}${r.truncated ? " (capped)" : ""}`)}`,
-    │ +                 );
-    │ … +150 lines
-⠦ thinking
-```
-User also had to kill the app.
-
-Only seen with Gemini/Google models.
-Only happens after shell tool calls.
-Other tools calls worked just fine during the same session with the same model and mini-coder version.
-There are no shell tool related hooks configured anywhere.
-
-The expectation was the turn to continue as normal since the tool calls succeded.
-
-Find the root cause, show proof.
-
-## Findings:
-
-Here is the concrete proof I just ran, no edits:
-- I executed renderTurn with an event stream that does:
-  1) tool-call-start(shell)
-  2) tool-result(shell success)
-  3) then never yields again
-- Result: the promise did not resolve within 700ms (timed_out_700ms).
-Then I ran the same sequence but added turn-complete:
-- Result: it resolved immediately (resolved).
-So this is now proven in your codepath:
-- renderTurn waits forever when the upstream async stream goes silent after a shell tool result.
-- This exactly matches the visible hang states.
-
-### Root Cause 1: Hangs spinning on `"shell"`
-**Proof in code:** `src/tools/shell.ts`
-*   When a command times out, `proc.kill("SIGTERM")` only kills the parent process (e.g., `bash`). Any child processes (e.g., `bun`) become orphaned but stay alive, holding the write end of the `stdout`/`stderr` pipes open. 
-*   Because the pipe never closes, `await reader.read()` inside `collectStream()` hangs indefinitely. 
-*   Because `collectStream()` never resolves, the tool execution never finishes, `tool-result` is never yielded, and the stream goes completely silent while the spinner stays stuck on "shell".
-   - **FIXED**
-
-### Root Cause 2: Hangs spinning on `"thinking"`
-**Proof in code:** `src/llm-api/turn.ts`
-*   After `git diff` completes, the tool resolves and `renderTurn` switches the spinner to `"thinking"`.
-*   The AI SDK automatically makes a new HTTP request to the Gemini API containing the tool result to generate the next step.
-*   Gemini's API occasionally hangs indefinitely or silently drops connections when receiving certain payloads (like large tool outputs or ANSI color codes, which `git diff` outputs).
-*   Because there is no timeout configured on the `streamText` call in `runTurn` (unless the user manually aborts), the underlying fetch request waits forever. The `result.fullStream` never yields the next chunk, but also never closes or errors.