@vincemakes/kiso-core 0.16.6 → 0.16.8

package/dist/kernel/loop.d.ts

@@ -146,7 +146,27 @@ export interface LoopConfig {
     /** P3: the session's id — carried to tools via ToolContext.sessionId. */
     readonly sessionId?: string;
 }
-export declare const DEFAULT_MAX_TURNS = 10;
+/**
+ * R3e (owner ruling, 2026-08-28) — there is NO default turn limit.
+ *
+ * `maxTurns` stays: a caller that wants a bound sets one, and the
+ * `max_turns` terminal is unchanged. What is retired is the DEFAULT.
+ *
+ * The reasoning, from the incident that found it: a real session read a
+ * doc, listed a directory, read four files and ran four commands — 43
+ * calls — and stopped at 20 turns, mid-task, saying nothing. A guardrail
+ * for "you set it running and walked away" was firing on someone sitting
+ * at the keyboard, where esc, the context window and the balance are
+ * already the bounds. Both reference implementations agree: neither puts
+ * a turn limit on an interactive session, and the one that has the
+ * mechanism spends it on forked subagents and non-interactive SDK calls,
+ * where nobody is watching.
+ *
+ * `Number.POSITIVE_INFINITY` rather than deleting the check: the
+ * comparison, the terminal and every test that sets a limit stay exactly
+ * as they were, and one line says what changed.
+ */
+export declare const DEFAULT_MAX_TURNS: number;
 export declare const DEFAULT_MAX_RETRIES = 2;
 export declare function loop(config: LoopConfig): AsyncGenerator<Event>;
 /**

package/dist/kernel/loop.js

@@ -41,7 +41,27 @@ import { NoOpHooks } from "./hooks.js";
 import { resolveModeProfile } from "./mode.js";
 import { denialResult } from "./permission.js";
 import { messagesToEvents, MICROCOMPACTABLE, DO_NOT_COMPACT, projectMessages } from "./project.js";
-export const DEFAULT_MAX_TURNS = 10;
+/**
+ * R3e (owner ruling, 2026-08-28) — there is NO default turn limit.
+ *
+ * `maxTurns` stays: a caller that wants a bound sets one, and the
+ * `max_turns` terminal is unchanged. What is retired is the DEFAULT.
+ *
+ * The reasoning, from the incident that found it: a real session read a
+ * doc, listed a directory, read four files and ran four commands — 43
+ * calls — and stopped at 20 turns, mid-task, saying nothing. A guardrail
+ * for "you set it running and walked away" was firing on someone sitting
+ * at the keyboard, where esc, the context window and the balance are
+ * already the bounds. Both reference implementations agree: neither puts
+ * a turn limit on an interactive session, and the one that has the
+ * mechanism spends it on forked subagents and non-interactive SDK calls,
+ * where nobody is watching.
+ *
+ * `Number.POSITIVE_INFINITY` rather than deleting the check: the
+ * comparison, the terminal and every test that sets a limit stay exactly
+ * as they were, and one line says what changed.
+ */
+export const DEFAULT_MAX_TURNS = Number.POSITIVE_INFINITY;
 export const DEFAULT_MAX_RETRIES = 2;
 export async function* loop(config) {
     const log = config.log ?? new EventLog();

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@vincemakes/kiso-core",
-	"version": "0.16.6",
+	"version": "0.16.8",
 	"description": "kiso (foundation) core — protocol, event log, loop, hooks, modes, permissions, compaction, delivery truth. The 2,000-line kernel at the bottom of the kiso framework.",
 	"type": "module",
 	"license": "MIT",
@@ -33,7 +33,7 @@
 		"openai"
 	],
 	"devDependencies": {
-		"@vincemakes/kiso-evals": "0.16.6",
+		"@vincemakes/kiso-evals": "0.16.8",
 		"@types/node": "^26.1.2",
 		"typescript": "^5.7.2",
 		"vitest": "^3.0.0"