koneck 2.25.62 → 2.25.64

package/dist/ink-chat.js

@@ -2,7 +2,7 @@ import { jsx as _jsx, Fragment as _Fragment, jsxs as _jsxs } from "react/jsx-run
 import React, { useState, useEffect, useRef } from 'react';
 import { Box, Static, Text, render, useApp, useInput, useStdin } from 'ink';
 import { execa } from 'execa';
-import { createAgentSession, buildClient, resolveAgentConcurrency, toolsUnsupportedNotice } from './engine.js';
+import { createAgentSession, buildClient, resolveAgentConcurrency, toolsUnsupportedNotice, isLocalRuntime } from './engine.js';
 import { estimateCost, formatCost } from './pricing.js';
 import { generateSessionId, saveSession, listSessions, loadSession, relativeAge, renameSession, forkSession, archiveSession, findSession, } from './session.js';
 import { loadMemory } from './memory.js';
@@ -766,7 +766,24 @@ Keyboard:
   Shift+Tab             Cycle mode (auto → plan → code)
   Ctrl+C                Cancel task / exit if idle
 `.trim();
-function App({ config: initialConfig }) {
+/**
+ * Whether to own the screen, when nothing has been configured either way.
+ *
+ * Only on a real terminal. A pipe has no cursor to move and no rows to fill, and writing the
+ * enter-alternate-screen sequence into a log file is how a captured session becomes unreadable.
+ */
+export function defaultAltScreen(stdout = process.stdout, env = process.env) {
+    if (!stdout.isTTY)
+        return false;
+    if (env['CI'])
+        return false;
+    // A terminal too short to hold the interface has nothing to gain: the transcript would be
+    // clipped to a row or two, and the terminal's own scrollback is more use than that.
+    if ((stdout.rows ?? 24) < 14)
+        return false;
+    return true;
+}
+function App({ config: initialConfig, clearFrame }) {
     const { exit } = useApp();
     const [cfg, setCfg] = useState(initialConfig);
     // Live activity accumulates in a ref and is painted by the 100 ms ticker. Mutating a ref
@@ -1014,6 +1031,18 @@ function App({ config: initialConfig }) {
             toolsWarnedRef.current = model;
             addSystem(toolsUnsupportedNotice(model));
         },
+        onLooping: (copies) => {
+            // The loop itself is the symptom. On a local model the cause is almost always the window:
+            // Ollama serves 4096 tokens unless told otherwise, whatever the model was trained for, and
+            // a conversation that no longer fits is exactly what makes a model start repeating.
+            const local = isLocalRuntime(cfg.provider);
+            addSystem(`${cfg.model} repeated the same text ${copies} times, so the reply was cut short.` +
+                (local
+                    ? `\n\nThis is usually the context window rather than the model. Ollama serves 4096 ` +
+                        `tokens by default however large the model is — set ` +
+                        `\`OLLAMA_CONTEXT_LENGTH=32768\` and restart it, then \`/context\` to confirm.`
+                    : ''));
+        },
         onThinking: (text, totalChars) => {
             thinkingRef.current = { chars: totalChars, at: Date.now() };
             // The text was discarded before this, so the model's reasoning was never visible — only a
@@ -1067,9 +1096,21 @@ function App({ config: initialConfig }) {
      * and what Codex does by default, offering --no-alt-screen to opt out.
      *
      * The cost is real: the alternate screen has no scrollback of its own, so history has to be
-     * scrolled from inside the application. That is why this is a choice rather than the default.
+     * scrolled from inside the application. It was a choice rather than the default for that
+     * reason, and the default has changed because the reason on the other side turned out to weigh
+     * more.
+     *
+     * Inline mode depends on Ink counting the lines it wrote so it can erase them, and that count is
+     * the number of newlines in the frame — not the number of rows the terminal used to show it. Any
+     * line the terminal wrapped makes the count too small, the erase falls short, and a whole copy
+     * of the interface is stranded on screen. Three separate reports of exactly that: a prompt
+     * floating mid-screen, two composers with the transcript between them, and a working prompt at
+     * the top with a dead one below. Here the frame is the whole screen, redrawn at fixed
+     * coordinates, so there is nothing to count and nothing to strand.
+     *
+     * /altscreen off, or `altScreen: false` in config, goes back to the terminal's own scrollback.
      */
-    const [altScreen, setAltScreen] = useState(cfg.altScreen ?? false);
+    const [altScreen, setAltScreen] = useState(cfg.altScreen ?? defaultAltScreen());
     /**
      * How many rows back from the newest the viewport is looking, in alt-screen mode.
      *
@@ -1435,12 +1476,16 @@ function App({ config: initialConfig }) {
     function redrawScreen() {
         if (!process.stdout.isTTY)
             return;
-        // Clear the screen, clear the scrollback with it — a stranded frame that has scrolled out of
-        // view is still in the buffer, and leaving it there means it reappears on the next scroll —
-        // then home the cursor so Ink's next frame starts from a known position.
+        // Ink's own clear first. It erases the frame using its own count of it and then resets that
+        // count to zero, which is the part that matters: after this Ink believes nothing is on screen,
+        // which is about to be true.
+        clearFrame?.();
+        // Then the screen, and the scrollback with it — a stranded frame that has scrolled out of view
+        // is still in the buffer, and leaving it there means it comes back on the next scroll — and
+        // home the cursor, which is where Ink will now draw.
         process.stdout.write('\u001b[2J\u001b[3J\u001b[H');
-        // Ink writes a frame only when its content differs from the last one, and the content has
-        // not changed — the screen it was drawn on has. Bumping this forces the write.
+        // Ink writes a frame only when its content differs from the last one, and the content has not
+        // changed — the screen it was drawn on has. Bumping this forces the write.
         setRepaint(n => n + 1);
     }
     async function doSave() {
@@ -3405,7 +3450,7 @@ function App({ config: initialConfig }) {
      * by <Static> in inline mode, and re-rendered every frame inside a clipped viewport in
      * alt-screen mode. Two copies of this markup would drift apart within a release.
      */
-    const renderRow = (row, index) => (row.role === 'header' ? (_jsxs(Box, { flexDirection: "column", children: [_jsxs(Box, { flexDirection: "column", alignItems: "center", marginTop: 1, marginBottom: 1, children: [logoFor(uiWidth, G.ascii).map((line, i) => (_jsx(Text, { color: CYAN, bold: true, children: line }, i))), _jsx(Text, { color: CYAN, bold: true, children: "KONECK  /  SOFTWARE DELIVERY SYSTEM" }), _jsx(Text, { color: MUTED, children: "Deliberate engineering, with control at every change." })] }), _jsx(Panel, { width: barWidth, color: CYAN, title: "KONECK", children: [`MODEL: \`${modelShort}\`   PROVIDER: \`${cfg.provider}\`   WORKSPACE: \`${workspace}\``] })] }, index)) : row.role === 'user' ? (
+    const renderRow = (row, index) => (row.role === 'header' ? (_jsxs(Box, { flexDirection: "column", children: [_jsxs(Box, { flexDirection: "column", alignItems: "center", marginTop: 1, marginBottom: 1, children: [logoFor(uiWidth, G.ascii).map((line, i) => (_jsx(Text, { color: CYAN, bold: true, children: line }, i))), _jsx(Text, { color: CYAN, bold: true, children: "KONECK  /  SOFTWARE DELIVERY SYSTEM" }), _jsx(Text, { color: MUTED, children: "Deliberate engineering, with control at every change." }), altScreen && (_jsx(Text, { color: DIM, children: "PageUp scrolls \u00B7 /altscreen off to use the terminal's scrollback instead" }))] }), _jsx(Panel, { width: barWidth, color: CYAN, title: "KONECK", children: [`MODEL: \`${modelShort}\`   PROVIDER: \`${cfg.provider}\`   WORKSPACE: \`${workspace}\``] })] }, index)) : row.role === 'user' ? (
     // Painted as a filled bar so the user's own words are the most findable thing
     // on screen when scrolling back through a long session.
     _jsx(Box, { marginTop: 1, flexDirection: "column", children: wrapPreserving(row.text ?? '', barWidth - 2).map((line, li) => (_jsx(Text, { backgroundColor: USER_BG, color: USER_FG, bold: li === 0, children: (li === 0 ? `${G.caret} ` : '  ') + fitCells(line, barWidth - 2) }, li))) }, index)) : row.role === 'plan' ? (() => {
@@ -3732,7 +3777,15 @@ export async function runInkChatMode(config) {
     // overshot — the banner ended up at the bottom with empty screen above it and a gap still
     // below. Starting at the top and growing downward is worse only until the screen fills, and
     // being wrong in a way that moves the whole interface is worse than that.
-    const app = render(_jsx(App, { config: config }), { exitOnCtrlC: false, patchConsole: false });
+    // `clear` is handed to the app because a repaint has to go through Ink, not around it. Ink
+    // tracks how many lines it last wrote and erases exactly that many; writing escape codes to the
+    // same terminal without telling it leaves that count describing a screen that no longer exists,
+    // and the next frame is drawn in the wrong place and pinned there. Reported as the prompt
+    // appearing at the top with a dead copy of the interface below it — caused by the first version
+    // of this repaint, which did exactly that.
+    let inkClear;
+    const app = render(_jsx(App, { config: config, clearFrame: () => inkClear?.() }), { exitOnCtrlC: false, patchConsole: false });
+    inkClear = app.clear;
     await app.waitUntilExit();
 }
 //# sourceMappingURL=ink-chat.js.map