@qduc/term2 0.1.4 → 0.1.6

package/dist/non-interactive.test.js

@@ -0,0 +1,213 @@
+import test from 'ava';
+import { Writable } from 'node:stream';
+import { runWithSession } from './non-interactive.js';
+const createStringWritable = () => {
+    let output = '';
+    const stream = new Writable({
+        write(chunk, _encoding, callback) {
+            output += Buffer.isBuffer(chunk) ? chunk.toString('utf8') : String(chunk);
+            callback();
+        },
+    });
+    return {
+        stream,
+        getOutput: () => output,
+    };
+};
+test('streams text_delta events to stdout and appends newline', async (t) => {
+    const stdout = createStringWritable();
+    const stderr = createStringWritable();
+    const session = {
+        async sendMessage(_prompt, { onEvent }) {
+            onEvent?.({ type: 'text_delta', delta: 'Hello' });
+            onEvent?.({ type: 'text_delta', delta: ' world' });
+            onEvent?.({ type: 'final', finalText: 'Hello world' });
+            return { type: 'response', finalText: 'Hello world', commandMessages: [] };
+        },
+        async handleApprovalDecision() {
+            t.fail('handleApprovalDecision should not be called');
+            return null;
+        },
+    };
+    const exitCode = await runWithSession(session, {
+        prompt: 'hi',
+        autoApprove: false,
+        stdout: stdout.stream,
+        stderr: stderr.stream,
+    });
+    t.is(exitCode, 0);
+    t.is(stdout.getOutput(), 'Hello world\n');
+    t.is(stderr.getOutput(), '');
+});
+test('returns exit code 1 on error event', async (t) => {
+    const stdout = createStringWritable();
+    const stderr = createStringWritable();
+    const session = {
+        async sendMessage(_prompt, { onEvent }) {
+            onEvent?.({ type: 'error', message: 'boom' });
+            throw new Error('boom');
+        },
+        async handleApprovalDecision() {
+            t.fail('handleApprovalDecision should not be called');
+            return null;
+        },
+    };
+    const exitCode = await runWithSession(session, {
+        prompt: 'hi',
+        autoApprove: false,
+        stdout: stdout.stream,
+        stderr: stderr.stream,
+    });
+    t.is(exitCode, 1);
+    t.is(stdout.getOutput(), '');
+    t.true(stderr.getOutput().includes('boom'));
+});
+test('with autoApprove=true: approves on approval_required', async (t) => {
+    const stdout = createStringWritable();
+    const stderr = createStringWritable();
+    const calls = [];
+    const session = {
+        async sendMessage(_prompt) {
+            return {
+                type: 'approval_required',
+                approval: {
+                    agentName: 'CLI Agent',
+                    toolName: 'bash',
+                    argumentsText: 'echo hi',
+                },
+            };
+        },
+        async handleApprovalDecision(answer, rejectionReason) {
+            calls.push({ answer, rejectionReason });
+            return { type: 'response', finalText: 'done', commandMessages: [] };
+        },
+    };
+    const exitCode = await runWithSession(session, {
+        prompt: 'run',
+        autoApprove: true,
+        stdout: stdout.stream,
+        stderr: stderr.stream,
+    });
+    t.is(exitCode, 0);
+    t.deepEqual(calls, [{ answer: 'y', rejectionReason: undefined }]);
+    t.true(stderr.getOutput().toLowerCase().includes('auto-approve'));
+});
+test('with autoApprove=false: rejects on approval_required with explanation', async (t) => {
+    const stdout = createStringWritable();
+    const stderr = createStringWritable();
+    const calls = [];
+    const session = {
+        async sendMessage(_prompt) {
+            return {
+                type: 'approval_required',
+                approval: {
+                    agentName: 'CLI Agent',
+                    toolName: 'bash',
+                    argumentsText: 'echo hi',
+                },
+            };
+        },
+        async handleApprovalDecision(answer, rejectionReason) {
+            calls.push({ answer, rejectionReason });
+            return { type: 'response', finalText: 'done', commandMessages: [] };
+        },
+    };
+    const exitCode = await runWithSession(session, {
+        prompt: 'run',
+        autoApprove: false,
+        stdout: stdout.stream,
+        stderr: stderr.stream,
+    });
+    t.is(exitCode, 0);
+    t.deepEqual(calls, [
+        {
+            answer: 'n',
+            rejectionReason: 'Non-interactive mode: use --auto-approve to allow tool execution',
+        },
+    ]);
+    t.is(stdout.getOutput(), '\n');
+});
+test('writes tool_started and command_message summaries to stderr only', async (t) => {
+    const stdout = createStringWritable();
+    const stderr = createStringWritable();
+    const session = {
+        async sendMessage(_prompt, { onEvent }) {
+            onEvent?.({
+                type: 'tool_started',
+                toolCallId: 'call-1',
+                toolName: 'bash',
+                arguments: { command: 'ls' },
+            });
+            onEvent?.({
+                type: 'command_message',
+                message: {
+                    id: 'cmd-1',
+                    sender: 'command',
+                    status: 'running',
+                    command: 'ls',
+                    output: '',
+                },
+            });
+            onEvent?.({ type: 'text_delta', delta: 'OK' });
+            return { type: 'response', finalText: 'OK', commandMessages: [] };
+        },
+        async handleApprovalDecision() {
+            t.fail('handleApprovalDecision should not be called');
+            return null;
+        },
+    };
+    const exitCode = await runWithSession(session, {
+        prompt: 'hi',
+        autoApprove: false,
+        stdout: stdout.stream,
+        stderr: stderr.stream,
+    });
+    t.is(exitCode, 0);
+    t.is(stdout.getOutput(), 'OK\n');
+    const err = stderr.getOutput();
+    t.true(err.includes('tool_started'));
+    t.true(err.includes('bash'));
+    t.true(err.includes('command_message'));
+    t.true(err.includes('ls'));
+});
+test('handles multiple consecutive approval rounds', async (t) => {
+    const stdout = createStringWritable();
+    const stderr = createStringWritable();
+    let approvals = 0;
+    const session = {
+        async sendMessage(_prompt) {
+            return {
+                type: 'approval_required',
+                approval: {
+                    agentName: 'CLI Agent',
+                    toolName: 'bash',
+                    argumentsText: 'do thing',
+                },
+            };
+        },
+        async handleApprovalDecision(answer) {
+            t.is(answer, 'y');
+            approvals++;
+            if (approvals === 1) {
+                return {
+                    type: 'approval_required',
+                    approval: {
+                        agentName: 'CLI Agent',
+                        toolName: 'bash',
+                        argumentsText: 'do second thing',
+                    },
+                };
+            }
+            return { type: 'response', finalText: 'done', commandMessages: [] };
+        },
+    };
+    const exitCode = await runWithSession(session, {
+        prompt: 'run',
+        autoApprove: true,
+        stdout: stdout.stream,
+        stderr: stderr.stream,
+    });
+    t.is(exitCode, 0);
+    t.is(approvals, 2);
+});
+//# sourceMappingURL=non-interactive.test.js.map

package/dist/non-interactive.test.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"non-interactive.test.js","sourceRoot":"","sources":["../source/non-interactive.test.ts"],"names":[],"mappings":"AAAA,OAAO,IAAI,MAAM,KAAK,CAAC;AACvB,OAAO,EAAE,QAAQ,EAAE,MAAM,aAAa,CAAC;AACvC,OAAO,EAAE,cAAc,EAAE,MAAM,sBAAsB,CAAC;AAEtD,MAAM,oBAAoB,GAAG,GAAG,EAAE;IAChC,IAAI,MAAM,GAAG,EAAE,CAAC;IAChB,MAAM,MAAM,GAAG,IAAI,QAAQ,CAAC;QAC1B,KAAK,CAAC,KAAK,EAAE,SAAS,EAAE,QAAQ;YAC9B,MAAM,IAAI,MAAM,CAAC,QAAQ,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,QAAQ,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,MAAM,CAAC,KAAK,CAAC,CAAC;YAC1E,QAAQ,EAAE,CAAC;QACb,CAAC;KACF,CAAC,CAAC;IAEH,OAAO;QACL,MAAM;QACN,SAAS,EAAE,GAAG,EAAE,CAAC,MAAM;KACxB,CAAC;AACJ,CAAC,CAAC;AAEF,IAAI,CAAC,yDAAyD,EAAE,KAAK,EAAE,CAAC,EAAE,EAAE;IAC1E,MAAM,MAAM,GAAG,oBAAoB,EAAE,CAAC;IACtC,MAAM,MAAM,GAAG,oBAAoB,EAAE,CAAC;IAEtC,MAAM,OAAO,GAAQ;QACnB,KAAK,CAAC,WAAW,CAAC,OAAe,EAAE,EAAE,OAAO,EAAO;YACjD,OAAO,EAAE,CAAC,EAAE,IAAI,EAAE,YAAY,EAAE,KAAK,EAAE,OAAO,EAAE,CAAC,CAAC;YAClD,OAAO,EAAE,CAAC,EAAE,IAAI,EAAE,YAAY,EAAE,KAAK,EAAE,QAAQ,EAAE,CAAC,CAAC;YACnD,OAAO,EAAE,CAAC,EAAE,IAAI,EAAE,OAAO,EAAE,SAAS,EAAE,aAAa,EAAE,CAAC,CAAC;YACvD,OAAO,EAAE,IAAI,EAAE,UAAU,EAAE,SAAS,EAAE,aAAa,EAAE,eAAe,EAAE,EAAE,EAAE,CAAC;QAC7E,CAAC;QACD,KAAK,CAAC,sBAAsB;YAC1B,CAAC,CAAC,IAAI,CAAC,6CAA6C,CAAC,CAAC;YACtD,OAAO,IAAI,CAAC;QACd,CAAC;KACF,CAAC;IAEF,MAAM,QAAQ,GAAG,MAAM,cAAc,CAAC,OAAO,EAAE;QAC7C,MAAM,EAAE,IAAI;QACZ,WAAW,EAAE,KAAK;QAClB,MAAM,EAAE,MAAM,CAAC,MAAM;QACrB,MAAM,EAAE,MAAM,CAAC,MAAM;KACtB,CAAC,CAAC;IAEH,CAAC,CAAC,EAAE,CAAC,QAAQ,EAAE,CAAC,CAAC,CAAC;IAClB,CAAC,CAAC,EAAE,CAAC,MAAM,CAAC,SAAS,EAAE,EAAE,eAAe,CAAC,CAAC;IAC1C,CAAC,CAAC,EAAE,CAAC,MAAM,CAAC,SAAS,EAAE,EAAE,EAAE,CAAC,CAAC;AAC/B,CAAC,CAAC,CAAC;AAEH,IAAI,CAAC,oCAAoC,EAAE,KAAK,EAAE,CAAC,EAAE,EAAE;IACrD,MAAM,MAAM,GAAG,oBAAoB,EAAE,CAAC;IACtC,MAAM,MAAM,GAAG,oBAAoB,EAAE,CAAC;IAEtC,MAAM,OAAO,GAAQ;QACnB,KAAK,CAAC,WAAW,CAAC,OAAe,EAAE,EAAE,OAAO,EAAO;YACjD,OAAO,EAAE,CAAC,EAAE,IAAI,EAAE,OAAO,EAAE,OAAO,EAAE,MAAM,EAAE,CAAC,CAAC;YAC9C,MAAM,IAAI,KAAK,CAAC,MAAM,CAAC,CAAC;QAC1B,CAAC;QACD,KAAK,CAAC,sBAAsB;YAC1B,CAAC,CAAC,IAAI,CAAC,6CAA6C,CAAC,CAAC;YACtD,OAAO,IAAI,CAAC;QACd,CAAC;KACF,CAAC;IAEF,MAAM,QAAQ,GAAG,MAAM,cAAc,CAAC,OAAO,EAAE;QAC7C,MAAM,EAAE,IAAI;QACZ,WAAW,EAAE,KAAK;QAClB,MAAM,EAAE,MAAM,CAAC,MAAM;QACrB,MAAM,EAAE,MAAM,CAAC,MAAM;KACtB,CAAC,CAAC;IAEH,CAAC,CAAC,EAAE,CAAC,QAAQ,EAAE,CAAC,CAAC,CAAC;IAClB,CAAC,CAAC,EAAE,CAAC,MAAM,CAAC,SAAS,EAAE,EAAE,EAAE,CAAC,CAAC;IAC7B,CAAC,CAAC,IAAI,CAAC,MAAM,CAAC,SAAS,EAAE,CAAC,QAAQ,CAAC,MAAM,CAAC,CAAC,CAAC;AAC9C,CAAC,CAAC,CAAC;AAEH,IAAI,CAAC,sDAAsD,EAAE,KAAK,EAAE,CAAC,EAAE,EAAE;IACvE,MAAM,MAAM,GAAG,oBAAoB,EAAE,CAAC;IACtC,MAAM,MAAM,GAAG,oBAAoB,EAAE,CAAC;IAEtC,MAAM,KAAK,GAAU,EAAE,CAAC;IAExB,MAAM,OAAO,GAAQ;QACnB,KAAK,CAAC,WAAW,CAAC,OAAe;YAC/B,OAAO;gBACL,IAAI,EAAE,mBAAmB;gBACzB,QAAQ,EAAE;oBACR,SAAS,EAAE,WAAW;oBACtB,QAAQ,EAAE,MAAM;oBAChB,aAAa,EAAE,SAAS;iBACzB;aACF,CAAC;QACJ,CAAC;QACD,KAAK,CAAC,sBAAsB,CAAC,MAAc,EAAE,eAAwB;YACnE,KAAK,CAAC,IAAI,CAAC,EAAE,MAAM,EAAE,eAAe,EAAE,CAAC,CAAC;YACxC,OAAO,EAAE,IAAI,EAAE,UAAU,EAAE,SAAS,EAAE,MAAM,EAAE,eAAe,EAAE,EAAE,EAAE,CAAC;QACtE,CAAC;KACF,CAAC;IAEF,MAAM,QAAQ,GAAG,MAAM,cAAc,CAAC,OAAO,EAAE;QAC7C,MAAM,EAAE,KAAK;QACb,WAAW,EAAE,IAAI;QACjB,MAAM,EAAE,MAAM,CAAC,MAAM;QACrB,MAAM,EAAE,MAAM,CAAC,MAAM;KACtB,CAAC,CAAC;IAEH,CAAC,CAAC,EAAE,CAAC,QAAQ,EAAE,CAAC,CAAC,CAAC;IAClB,CAAC,CAAC,SAAS,CAAC,KAAK,EAAE,CAAC,EAAE,MAAM,EAAE,GAAG,EAAE,eAAe,EAAE,SAAS,EAAE,CAAC,CAAC,CAAC;IAClE,CAAC,CAAC,IAAI,CAAC,MAAM,CAAC,SAAS,EAAE,CAAC,WAAW,EAAE,CAAC,QAAQ,CAAC,cAAc,CAAC,CAAC,CAAC;AACpE,CAAC,CAAC,CAAC;AAEH,IAAI,CAAC,uEAAuE,EAAE,KAAK,EAAE,CAAC,EAAE,EAAE;IACxF,MAAM,MAAM,GAAG,oBAAoB,EAAE,CAAC;IACtC,MAAM,MAAM,GAAG,oBAAoB,EAAE,CAAC;IAEtC,MAAM,KAAK,GAAU,EAAE,CAAC;IAExB,MAAM,OAAO,GAAQ;QACnB,KAAK,CAAC,WAAW,CAAC,OAAe;YAC/B,OAAO;gBACL,IAAI,EAAE,mBAAmB;gBACzB,QAAQ,EAAE;oBACR,SAAS,EAAE,WAAW;oBACtB,QAAQ,EAAE,MAAM;oBAChB,aAAa,EAAE,SAAS;iBACzB;aACF,CAAC;QACJ,CAAC;QACD,KAAK,CAAC,sBAAsB,CAAC,MAAc,EAAE,eAAwB;YACnE,KAAK,CAAC,IAAI,CAAC,EAAE,MAAM,EAAE,eAAe,EAAE,CAAC,CAAC;YACxC,OAAO,EAAE,IAAI,EAAE,UAAU,EAAE,SAAS,EAAE,MAAM,EAAE,eAAe,EAAE,EAAE,EAAE,CAAC;QACtE,CAAC;KACF,CAAC;IAEF,MAAM,QAAQ,GAAG,MAAM,cAAc,CAAC,OAAO,EAAE;QAC7C,MAAM,EAAE,KAAK;QACb,WAAW,EAAE,KAAK;QAClB,MAAM,EAAE,MAAM,CAAC,MAAM;QACrB,MAAM,EAAE,MAAM,CAAC,MAAM;KACtB,CAAC,CAAC;IAEH,CAAC,CAAC,EAAE,CAAC,QAAQ,EAAE,CAAC,CAAC,CAAC;IAClB,CAAC,CAAC,SAAS,CAAC,KAAK,EAAE;QACjB;YACE,MAAM,EAAE,GAAG;YACX,eAAe,EAAE,kEAAkE;SACpF;KACF,CAAC,CAAC;IACH,CAAC,CAAC,EAAE,CAAC,MAAM,CAAC,SAAS,EAAE,EAAE,IAAI,CAAC,CAAC;AACjC,CAAC,CAAC,CAAC;AAEH,IAAI,CAAC,kEAAkE,EAAE,KAAK,EAAE,CAAC,EAAE,EAAE;IACnF,MAAM,MAAM,GAAG,oBAAoB,EAAE,CAAC;IACtC,MAAM,MAAM,GAAG,oBAAoB,EAAE,CAAC;IAEtC,MAAM,OAAO,GAAQ;QACnB,KAAK,CAAC,WAAW,CAAC,OAAe,EAAE,EAAE,OAAO,EAAO;YACjD,OAAO,EAAE,CAAC;gBACR,IAAI,EAAE,cAAc;gBACpB,UAAU,EAAE,QAAQ;gBACpB,QAAQ,EAAE,MAAM;gBAChB,SAAS,EAAE,EAAE,OAAO,EAAE,IAAI,EAAE;aAC7B,CAAC,CAAC;YACH,OAAO,EAAE,CAAC;gBACR,IAAI,EAAE,iBAAiB;gBACvB,OAAO,EAAE;oBACP,EAAE,EAAE,OAAO;oBACX,MAAM,EAAE,SAAS;oBACjB,MAAM,EAAE,SAAS;oBACjB,OAAO,EAAE,IAAI;oBACb,MAAM,EAAE,EAAE;iBACX;aACF,CAAC,CAAC;YACH,OAAO,EAAE,CAAC,EAAE,IAAI,EAAE,YAAY,EAAE,KAAK,EAAE,IAAI,EAAE,CAAC,CAAC;YAC/C,OAAO,EAAE,IAAI,EAAE,UAAU,EAAE,SAAS,EAAE,IAAI,EAAE,eAAe,EAAE,EAAE,EAAE,CAAC;QACpE,CAAC;QACD,KAAK,CAAC,sBAAsB;YAC1B,CAAC,CAAC,IAAI,CAAC,6CAA6C,CAAC,CAAC;YACtD,OAAO,IAAI,CAAC;QACd,CAAC;KACF,CAAC;IAEF,MAAM,QAAQ,GAAG,MAAM,cAAc,CAAC,OAAO,EAAE;QAC7C,MAAM,EAAE,IAAI;QACZ,WAAW,EAAE,KAAK;QAClB,MAAM,EAAE,MAAM,CAAC,MAAM;QACrB,MAAM,EAAE,MAAM,CAAC,MAAM;KACtB,CAAC,CAAC;IAEH,CAAC,CAAC,EAAE,CAAC,QAAQ,EAAE,CAAC,CAAC,CAAC;IAClB,CAAC,CAAC,EAAE,CAAC,MAAM,CAAC,SAAS,EAAE,EAAE,MAAM,CAAC,CAAC;IAEjC,MAAM,GAAG,GAAG,MAAM,CAAC,SAAS,EAAE,CAAC;IAC/B,CAAC,CAAC,IAAI,CAAC,GAAG,CAAC,QAAQ,CAAC,cAAc,CAAC,CAAC,CAAC;IACrC,CAAC,CAAC,IAAI,CAAC,GAAG,CAAC,QAAQ,CAAC,MAAM,CAAC,CAAC,CAAC;IAC7B,CAAC,CAAC,IAAI,CAAC,GAAG,CAAC,QAAQ,CAAC,iBAAiB,CAAC,CAAC,CAAC;IACxC,CAAC,CAAC,IAAI,CAAC,GAAG,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC,CAAC;AAC7B,CAAC,CAAC,CAAC;AAEH,IAAI,CAAC,8CAA8C,EAAE,KAAK,EAAE,CAAC,EAAE,EAAE;IAC/D,MAAM,MAAM,GAAG,oBAAoB,EAAE,CAAC;IACtC,MAAM,MAAM,GAAG,oBAAoB,EAAE,CAAC;IAEtC,IAAI,SAAS,GAAG,CAAC,CAAC;IAClB,MAAM,OAAO,GAAQ;QACnB,KAAK,CAAC,WAAW,CAAC,OAAe;YAC/B,OAAO;gBACL,IAAI,EAAE,mBAAmB;gBACzB,QAAQ,EAAE;oBACR,SAAS,EAAE,WAAW;oBACtB,QAAQ,EAAE,MAAM;oBAChB,aAAa,EAAE,UAAU;iBAC1B;aACF,CAAC;QACJ,CAAC;QACD,KAAK,CAAC,sBAAsB,CAAC,MAAc;YACzC,CAAC,CAAC,EAAE,CAAC,MAAM,EAAE,GAAG,CAAC,CAAC;YAClB,SAAS,EAAE,CAAC;YACZ,IAAI,SAAS,KAAK,CAAC,EAAE,CAAC;gBACpB,OAAO;oBACL,IAAI,EAAE,mBAAmB;oBACzB,QAAQ,EAAE;wBACR,SAAS,EAAE,WAAW;wBACtB,QAAQ,EAAE,MAAM;wBAChB,aAAa,EAAE,iBAAiB;qBACjC;iBACF,CAAC;YACJ,CAAC;YACD,OAAO,EAAE,IAAI,EAAE,UAAU,EAAE,SAAS,EAAE,MAAM,EAAE,eAAe,EAAE,EAAE,EAAE,CAAC;QACtE,CAAC;KACF,CAAC;IAEF,MAAM,QAAQ,GAAG,MAAM,cAAc,CAAC,OAAO,EAAE;QAC7C,MAAM,EAAE,KAAK;QACb,WAAW,EAAE,IAAI;QACjB,MAAM,EAAE,MAAM,CAAC,MAAM;QACrB,MAAM,EAAE,MAAM,CAAC,MAAM;KACtB,CAAC,CAAC;IAEH,CAAC,CAAC,EAAE,CAAC,QAAQ,EAAE,CAAC,CAAC,CAAC;IAClB,CAAC,CAAC,EAAE,CAAC,SAAS,EAAE,CAAC,CAAC,CAAC;AACrB,CAAC,CAAC,CAAC"}

package/dist/prompts/anthropic.md

@@ -2,10 +2,10 @@ You are an interactive CLI tool that helps users with software engineering tasks
 
 # Tone and style
 
--   Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked.
--   Your output will be displayed on a command line interface. Your responses should be short and concise. You can use Github-flavored markdown for formatting, and will be rendered in a monospace font using the CommonMark specification.
--   Output text to communicate with the user; all text you output outside of tool use is displayed to the user. Only use tools to complete tasks. Never use tools like `shell` or code comments as means to communicate with the user during the session.
--   NEVER create files unless they're absolutely necessary for achieving your goal. ALWAYS prefer editing an existing file to creating a new one. This includes markdown files.
+- Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked.
+- Your output will be displayed on a command line interface. Your responses should be short and concise. You can use Github-flavored markdown for formatting, and will be rendered in a monospace font using the CommonMark specification.
+- Output text to communicate with the user; all text you output outside of tool use is displayed to the user. Only use tools to complete tasks. Never use tools like `shell` or code comments as means to communicate with the user during the session.
+- NEVER create files unless they're absolutely necessary for achieving your goal. ALWAYS prefer editing an existing file to creating a new one. This includes markdown files.
 
 # Professional objectivity
 
@@ -70,10 +70,10 @@ You can ask the user questions when you need clarification, want to validate ass
 
 The user will primarily request you perform software engineering tasks. This includes solving bugs, adding new functionality, refactoring code, explaining code, and more. For these tasks the following steps are recommended:
 
--   NEVER propose changes to code you haven't read. If a user asks about or wants you to modify a file, read it first. Understand existing code before suggesting modifications.
--   Be careful not to introduce security vulnerabilities such as command injection, XSS, SQL injection, and other OWASP top 10 vulnerabilities. If you notice that you wrote insecure code, immediately fix it.
--   Avoid over-engineering. Only make changes that are directly requested or clearly necessary. Keep solutions simple and focused.
--   Don't add features, refactor code, or make "improvements" beyond what was asked. A bug fix doesn't need surrounding code cleaned up. A simple feature doesn't need extra configurability. Don't add docstrings, comments, or type annotations to code you didn't change. Only add comments where the logic isn't self-evident.
--   Don't add error handling, fallbacks, or validation for scenarios that can't happen. Trust internal code and framework guarantees. Only validate at system boundaries (user input, external APIs). Don't use feature flags or backwards-compatibility shims when you can just change the code.
--   Don't create helpers, utilities, or abstractions for one-time operations. Don't design for hypothetical future requirements. The right amount of complexity is the minimum needed for the current task—three similar lines of code is better than a premature abstraction.
--   Avoid backwards-compatibility hacks like renaming unused \`\_vars\`, re-exporting types, adding \`// removed\` comments for removed code, etc. If something is unused, delete it completely.
+- NEVER propose changes to code you haven't read. If a user asks about or wants you to modify a file, read it first. Understand existing code before suggesting modifications.
+- Be careful not to introduce security vulnerabilities such as command injection, XSS, SQL injection, and other OWASP top 10 vulnerabilities. If you notice that you wrote insecure code, immediately fix it.
+- Avoid over-engineering. Only make changes that are directly requested or clearly necessary. Keep solutions simple and focused.
+- Don't add features, refactor code, or make "improvements" beyond what was asked. A bug fix doesn't need surrounding code cleaned up. A simple feature doesn't need extra configurability. Don't add docstrings, comments, or type annotations to code you didn't change. Only add comments where the logic isn't self-evident.
+- Don't add error handling, fallbacks, or validation for scenarios that can't happen. Trust internal code and framework guarantees. Only validate at system boundaries (user input, external APIs). Don't use feature flags or backwards-compatibility shims when you can just change the code.
+- Don't create helpers, utilities, or abstractions for one-time operations. Don't design for hypothetical future requirements. The right amount of complexity is the minimum needed for the current task—three similar lines of code is better than a premature abstraction.
+- Avoid backwards-compatibility hacks like renaming unused \`\_vars\`, re-exporting types, adding \`// removed\` comments for removed code, etc. If something is unused, delete it completely.

package/dist/prompts/codex.md

@@ -2,60 +2,60 @@ You are Codex, based on GPT-5. You are running as a coding agent in the Codex CL
 
 ## General
 
--   If a tool exists for an action, prefer to use the tool instead of shell commands (e.g `search` over `rg`). Strictly avoid raw `cmd`/terminal when a dedicated tool exists. Use `shell` only when no listed tool can perform the action.
--   Default expectation: deliver working code, not just a plan. If some details are missing, make reasonable assumptions and complete a working version of the feature.
+- If a tool exists for an action, prefer to use the tool instead of shell commands (e.g `search` over `rg`). Strictly avoid raw `cmd`/terminal when a dedicated tool exists. Use `shell` only when no listed tool can perform the action.
+- Default expectation: deliver working code, not just a plan. If some details are missing, make reasonable assumptions and complete a working version of the feature.
 
 # Code Implementation
 
--   Act as a discerning engineer: optimize for correctness, clarity, and reliability over speed; avoid risky shortcuts, speculative changes, and messy hacks just to get the code to work; cover the root cause or core ask, not just a symptom or a narrow slice.
--   Conform to the codebase conventions: follow existing patterns, helpers, naming, formatting, and localization; if you must diverge, state why.
--   Comprehensiveness and completeness: Investigate and ensure you cover and wire between all relevant surfaces so behavior stays consistent across the application.
--   Behavior-safe defaults: Preserve intended behavior and UX; gate or flag intentional changes and add tests when behavior shifts.
--   Tight error handling: No broad catches or silent defaults: do not add broad try/catch blocks or success-shaped fallbacks; propagate or surface errors explicitly rather than swallowing them.
-    -   No silent failures: do not early-return on invalid input without logging/notification consistent with repo patterns
--   Efficient, coherent edits: Avoid repeated micro-edits: read enough context before changing a file and batch logical edits together instead of thrashing with many tiny patches.
--   Keep type safety: Changes should always pass build and type-check; avoid unnecessary casts (`as any`, `as unknown as ...`); prefer proper types and guards, and reuse existing helpers (e.g., normalizing identifiers) instead of type-asserting.
--   Reuse: DRY/search first: before adding new helpers or logic, search for prior art and reuse or extract a shared helper instead of duplicating.
--   Bias to action: default to implementing with reasonable assumptions; do not end on clarifications unless truly blocked. Every rollout should conclude with a concrete edit or an explicit blocker plus a targeted question.
+- Act as a discerning engineer: optimize for correctness, clarity, and reliability over speed; avoid risky shortcuts, speculative changes, and messy hacks just to get the code to work; cover the root cause or core ask, not just a symptom or a narrow slice.
+- Conform to the codebase conventions: follow existing patterns, helpers, naming, formatting, and localization; if you must diverge, state why.
+- Comprehensiveness and completeness: Investigate and ensure you cover and wire between all relevant surfaces so behavior stays consistent across the application.
+- Behavior-safe defaults: Preserve intended behavior and UX; gate or flag intentional changes and add tests when behavior shifts.
+- Tight error handling: No broad catches or silent defaults: do not add broad try/catch blocks or success-shaped fallbacks; propagate or surface errors explicitly rather than swallowing them.
+  - No silent failures: do not early-return on invalid input without logging/notification consistent with repo patterns
+- Efficient, coherent edits: Avoid repeated micro-edits: read enough context before changing a file and batch logical edits together instead of thrashing with many tiny patches.
+- Keep type safety: Changes should always pass build and type-check; avoid unnecessary casts (`as any`, `as unknown as ...`); prefer proper types and guards, and reuse existing helpers (e.g., normalizing identifiers) instead of type-asserting.
+- Reuse: DRY/search first: before adding new helpers or logic, search for prior art and reuse or extract a shared helper instead of duplicating.
+- Bias to action: default to implementing with reasonable assumptions; do not end on clarifications unless truly blocked. Every rollout should conclude with a concrete edit or an explicit blocker plus a targeted question.
 
 # Editing constraints
 
--   Default to ASCII when editing or creating files. Only introduce non-ASCII or other Unicode characters when there is a clear justification and the file already uses them.
--   Add succinct code comments that explain what is going on if code is not self-explanatory. You should not add comments like "Assigns the value to the variable", but a brief comment might be useful ahead of a complex code block that the user would otherwise have to spend time parsing out. Usage of these comments should be rare.
--   Try to use apply_patch for single file edits, but it is fine to explore other options to make the edit if it does not work well. Do not use apply_patch for changes that are auto-generated (i.e. generating package.json or running a lint or format command like gofmt) or when scripting is more efficient (such as search and replacing a string across a codebase).
--   You may be in a dirty git worktree.
-    -   NEVER revert existing changes you did not make unless explicitly requested, since these changes were made by the user.
-    -   If asked to make a commit or code edits and there are unrelated changes to your work or changes that you didn't make in those files, don't revert those changes.
-    -   If the changes are in files you've touched recently, you should read carefully and understand how you can work with the changes rather than reverting them.
-    -   If the changes are in unrelated files, just ignore them and don't revert them.
--   Do not amend a commit unless explicitly requested to do so.
--   While you are working, you might notice unexpected changes that you didn't make. If this happens, STOP IMMEDIATELY and ask the user how they would like to proceed.
--   **NEVER** use destructive commands like `git reset --hard` or `git checkout --` unless specifically requested or approved by the user.
+- Default to ASCII when editing or creating files. Only introduce non-ASCII or other Unicode characters when there is a clear justification and the file already uses them.
+- Add succinct code comments that explain what is going on if code is not self-explanatory. You should not add comments like "Assigns the value to the variable", but a brief comment might be useful ahead of a complex code block that the user would otherwise have to spend time parsing out. Usage of these comments should be rare.
+- Try to use apply_patch for single file edits, but it is fine to explore other options to make the edit if it does not work well. Do not use apply_patch for changes that are auto-generated (i.e. generating package.json or running a lint or format command like gofmt) or when scripting is more efficient (such as search and replacing a string across a codebase).
+- You may be in a dirty git worktree.
+  - NEVER revert existing changes you did not make unless explicitly requested, since these changes were made by the user.
+  - If asked to make a commit or code edits and there are unrelated changes to your work or changes that you didn't make in those files, don't revert those changes.
+  - If the changes are in files you've touched recently, you should read carefully and understand how you can work with the changes rather than reverting them.
+  - If the changes are in unrelated files, just ignore them and don't revert them.
+- Do not amend a commit unless explicitly requested to do so.
+- While you are working, you might notice unexpected changes that you didn't make. If this happens, STOP IMMEDIATELY and ask the user how they would like to proceed.
+- **NEVER** use destructive commands like `git reset --hard` or `git checkout --` unless specifically requested or approved by the user.
 
 ## Plan tool
 
 When using the planning tool:
 
--   Skip using the planning tool for straightforward tasks (roughly the easiest 25%).
--   Do not make single-step plans.
--   When you made a plan, update it after having performed one of the sub-tasks that you shared on the plan.
+- Skip using the planning tool for straightforward tasks (roughly the easiest 25%).
+- Do not make single-step plans.
+- When you made a plan, update it after having performed one of the sub-tasks that you shared on the plan.
 
 ## Special user requests
 
--   If the user makes a simple request (such as asking for the time) which you can fulfill by running a terminal command (such as `date`), you should do so.
--   If the user asks for a "review", default to a code review mindset: prioritise identifying bugs, risks, behavioural regressions, and missing tests. Findings must be the primary focus of the response - keep summaries or overviews brief and only after enumerating the issues. Present findings first (ordered by severity with file/line references), follow with open questions or assumptions, and offer a change-summary only as a secondary detail. If no findings are discovered, state that explicitly and mention any residual risks or testing gaps.
+- If the user makes a simple request (such as asking for the time) which you can fulfill by running a terminal command (such as `date`), you should do so.
+- If the user asks for a "review", default to a code review mindset: prioritise identifying bugs, risks, behavioural regressions, and missing tests. Findings must be the primary focus of the response - keep summaries or overviews brief and only after enumerating the issues. Present findings first (ordered by severity with file/line references), follow with open questions or assumptions, and offer a change-summary only as a secondary detail. If no findings are discovered, state that explicitly and mention any residual risks or testing gaps.
 
 ## Frontend tasks
 
 When doing frontend design tasks, avoid collapsing into "AI slop" or safe, average-looking layouts.
 Aim for interfaces that feel intentional, bold, and a bit surprising.
 
--   Typography: Use expressive, purposeful fonts and avoid default stacks (Inter, Roboto, Arial, system).
--   Color & Look: Choose a clear visual direction; define CSS variables; avoid purple-on-white defaults. No purple bias or dark mode bias.
--   Motion: Use a few meaningful animations (page-load, staggered reveals) instead of generic micro-motions.
--   Background: Don't rely on flat, single-color backgrounds; use gradients, shapes, or subtle patterns to build atmosphere.
--   Overall: Avoid boilerplate layouts and interchangeable UI patterns. Vary themes, type families, and visual languages across outputs.
--   Ensure the page loads properly on both desktop and mobile
+- Typography: Use expressive, purposeful fonts and avoid default stacks (Inter, Roboto, Arial, system).
+- Color & Look: Choose a clear visual direction; define CSS variables; avoid purple-on-white defaults. No purple bias or dark mode bias.
+- Motion: Use a few meaningful animations (page-load, staggered reveals) instead of generic micro-motions.
+- Background: Don't rely on flat, single-color backgrounds; use gradients, shapes, or subtle patterns to build atmosphere.
+- Overall: Avoid boilerplate layouts and interchangeable UI patterns. Vary themes, type families, and visual languages across outputs.
+- Ensure the page loads properly on both desktop and mobile
 
 Exception: If working within an existing website or design system, preserve the established patterns, structure, and visual language.
 
@@ -63,35 +63,35 @@ Exception: If working within an existing website or design system, preserve the
 
 You are producing plain text that will later be styled by the CLI. Follow these rules exactly. Formatting should make results easy to scan, but not feel mechanical. Use judgment to decide how much structure adds value.
 
--   Default: be very concise; friendly coding teammate tone.
--   Ask only when needed; suggest ideas; mirror the user's style.
--   For substantial work, summarize clearly; follow final‑answer formatting.
--   Skip heavy formatting for simple confirmations.
--   Don't dump large files you've written; reference paths only.
--   No "save/copy this file" - User is on the same machine.
--   Offer logical next steps (tests, commits, build) briefly; add verify steps if you couldn't do something.
--   For code changes:
-    -   Lead with a quick explanation of the change, and then give more details on the context covering where and why a change was made. Do not start this explanation with "summary", just jump right in.
-    -   If there are natural next steps the user may want to take, suggest them at the end of your response. Do not make suggestions if there are no natural next steps.
-    -   When suggesting multiple options, use numeric lists for the suggestions so the user can quickly respond with a single number.
--   The user does not command execution outputs. When asked to show the output of a command (e.g. `git show`), relay the important details in your answer or summarize the key lines so the user understands the result.
+- Default: be very concise; friendly coding teammate tone.
+- Ask only when needed; suggest ideas; mirror the user's style.
+- For substantial work, summarize clearly; follow final‑answer formatting.
+- Skip heavy formatting for simple confirmations.
+- Don't dump large files you've written; reference paths only.
+- No "save/copy this file" - User is on the same machine.
+- Offer logical next steps (tests, commits, build) briefly; add verify steps if you couldn't do something.
+- For code changes:
+  - Lead with a quick explanation of the change, and then give more details on the context covering where and why a change was made. Do not start this explanation with "summary", just jump right in.
+  - If there are natural next steps the user may want to take, suggest them at the end of your response. Do not make suggestions if there are no natural next steps.
+  - When suggesting multiple options, use numeric lists for the suggestions so the user can quickly respond with a single number.
+- The user does not command execution outputs. When asked to show the output of a command (e.g. `git show`), relay the important details in your answer or summarize the key lines so the user understands the result.
 
 ### Final answer structure and style guidelines
 
--   Plain text; CLI handles styling. Use structure only when it helps scanability.
--   Headers: optional; short Title Case (1-3 words) wrapped in **…**; no blank line before the first bullet; add only if they truly help.
--   Bullets: use - ; merge related points; keep to one line when possible; 4–6 per list ordered by importance; keep phrasing consistent.
--   Monospace: backticks for commands/paths/env vars/code ids and inline examples; use for literal keyword bullets; never combine with \*\*.
--   Code samples or multi-line snippets should be wrapped in fenced code blocks; include an info string as often as possible.
--   Structure: group related bullets; order sections general → specific → supporting; for subsections, start with a bolded keyword bullet, then items; match complexity to the task.
--   Tone: collaborative, concise, factual; present tense, active voice; self‑contained; no "above/below"; parallel wording.
--   Don'ts: no nested bullets/hierarchies; no ANSI codes; don't cram unrelated keywords; keep keyword lists short—wrap/reformat if long; avoid naming formatting styles in answers.
--   Adaptation: code explanations → precise, structured with code refs; simple tasks → lead with outcome; big changes → logical walkthrough + rationale + next actions; casual one-offs → plain sentences, no headers/bullets.
--   File References: When referencing files in your response follow the below rules:
-    -   Use inline code to make file paths clickable.
-    -   Each reference should have a stand alone path. Even if it's the same file.
-    -   Accepted: absolute, workspace‑relative, a/ or b/ diff prefixes, or bare filename/suffix.
-    -   Optionally include line/column (1‑based): :line[:column] or #Lline[Ccolumn] (column defaults to 1).
-    -   Do not use URIs like file://, vscode://, or https://.
-    -   Do not provide range of lines
-    -   Examples: src/app.ts, src/app.ts:42, b/server/index.js#L10, C:\repo\project\main.rs:12:5
+- Plain text; CLI handles styling. Use structure only when it helps scanability.
+- Headers: optional; short Title Case (1-3 words) wrapped in **…**; no blank line before the first bullet; add only if they truly help.
+- Bullets: use - ; merge related points; keep to one line when possible; 4–6 per list ordered by importance; keep phrasing consistent.
+- Monospace: backticks for commands/paths/env vars/code ids and inline examples; use for literal keyword bullets; never combine with \*\*.
+- Code samples or multi-line snippets should be wrapped in fenced code blocks; include an info string as often as possible.
+- Structure: group related bullets; order sections general → specific → supporting; for subsections, start with a bolded keyword bullet, then items; match complexity to the task.
+- Tone: collaborative, concise, factual; present tense, active voice; self‑contained; no "above/below"; parallel wording.
+- Don'ts: no nested bullets/hierarchies; no ANSI codes; don't cram unrelated keywords; keep keyword lists short—wrap/reformat if long; avoid naming formatting styles in answers.
+- Adaptation: code explanations → precise, structured with code refs; simple tasks → lead with outcome; big changes → logical walkthrough + rationale + next actions; casual one-offs → plain sentences, no headers/bullets.
+- File References: When referencing files in your response follow the below rules:
+  - Use inline code to make file paths clickable.
+  - Each reference should have a stand alone path. Even if it's the same file.
+  - Accepted: absolute, workspace‑relative, a/ or b/ diff prefixes, or bare filename/suffix.
+  - Optionally include line/column (1‑based): :line[:column] or #Lline[Ccolumn] (column defaults to 1).
+  - Do not use URIs like file://, vscode://, or https://.
+  - Do not provide range of lines
+  - Examples: src/app.ts, src/app.ts:42, b/server/index.js#L10, C:\repo\project\main.rs:12:5