@orxataguy/tyr 1.0.38 → 1.0.39

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@orxataguy/tyr",
-  "version": "1.0.38",
+  "version": "1.0.39",
   "type": "module",
   "bin": {
     "tyr": "./bin/tyr.js"

package/src/core/sys/chat.ts

@@ -1,7 +1,7 @@
 import path from 'path';
 import { readFile } from 'fs/promises';
 import { TyrContext } from '../Kernel';
-import type { AIContentBlock, AIMessage } from '../../lib/AIVendorManager';
+import type { AIContentBlock, AIMessage, TaskPriority } from '../../lib/AIVendorManager';
 import type { ChatMessageContext } from '../../lib/ChatManager';
 
 function parseFlag(args: string[], name: string): string | undefined {
@@ -19,9 +19,25 @@ export default function chat({ logger, chat: chatManager, aiVendor, fail }: TyrC
         const port = portArg ? parseInt(portArg, 10) : undefined;
         const splitRatio = splitArg ? parseFloat(splitArg) : undefined;
 
+        // Which routing priority (model tier + thinking effort) answers a chat message with —
+        // see AIVendorManager.TaskPriority. Chat defaults to 'media-prioridad' (the same default
+        // ai:code uses) rather than something cheaper, since a wrong answer in an interactive
+        // back-and-forth is more disruptive than in a one-shot batch command.
+        const priority = (parseFlag(args, '--priority') as TaskPriority | undefined) ?? 'media-prioridad';
+
+        // Complexity/cost ceiling ("techo de complejidad"): no resolved priority may ever exceed
+        // this, no matter what --priority above (or a future per-message override) asks for. Falls
+        // back to AI_CHAT_MAX_PRIORITY so a chat session can be capped independently from ai:code /
+        // ai:describe (which fall back to the general AI_MAX_PRIORITY instead — see
+        // AIVendorManager.getPriorityCeiling()). --max-priority overrides both for this one run.
+        const maxPriority = (parseFlag(args, '--max-priority') as TaskPriority | undefined)
+            ?? (process.env.AI_CHAT_MAX_PRIORITY as TaskPriority | undefined);
+        if (maxPriority) aiVendor.setPriorityCeiling(maxPriority);
+
         // Default responder: forwards the conversation (plus any attached images) to the
-        // configured AI vendor. Replace with your own chatManager.onMessage(...) in a custom
-        // command if you want different behaviour.
+        // configured AI vendor, routed through the same priority/ceiling system as ai:code and
+        // ai:describe. Replace with your own chatManager.onMessage(...) in a custom command if you
+        // want different behaviour.
         chatManager.onMessage(async ({ message, history, dir: chatDir }: ChatMessageContext) => {
             const priorTurns: AIMessage[] = history.slice(0, -1).map((m) => ({
                 role: m.role === 'user' ? 'user' : 'assistant',
@@ -49,7 +65,7 @@ export default function chat({ logger, chat: chatManager, aiVendor, fail }: TyrC
                 { role: 'user', content: contentBlocks.length > 0 ? contentBlocks : message.text },
             ];
 
-            const result = await aiVendor.complete(messages);
+            const result = await aiVendor.completeWithPriority(messages, priority);
             return result.content;
         });
 
@@ -65,6 +81,7 @@ export default function chat({ logger, chat: chatManager, aiVendor, fail }: TyrC
             const session = await chatManager.open(dir, { port, splitRatio });
             logger.success(`Chat ready at: ${session.url}`);
             logger.info(`Browsing: ${session.dir}`);
+            logger.info(`Priority: ${priority}${maxPriority ? ` (ceiling: ${maxPriority})` : ''}`);
             logger.info('Press Ctrl+C to stop.');
         } catch (e: any) {
             fail(`Could not start chat: ${e.message}`, 'Check that the directory exists and the port is free.');